#3

We are seeing the same thing from about 7.5 hours ago (about 21:30UTC on the 27th), along with other strangeness in the entities.

Random example I just picked gives media entities via the rest API for ‘560291409522335746’ but when it came through on the streaming API the media key was missing altogether :

"entities":{
  "hashtags":[],
  "trends":[],
  "urls":[],
  "user_mentions":[{"screen_name":"MelissaGeise","name":"Melissa Geise","id":56539140,"id_str":"56539140","indices":[15,28]}],
  "symbols":[]
}

Also note that user @libbydink is missing from the above entities, but does appear in the REST API output, and there appears to be new, undocumented entities here ‘trends’, and ‘symbols’.

JB.

#4

same issue here. no media even it has photos posted.

#5

Maybe it’s because new video support. On other post I see they got extended_entities field.

#6

maybe. but I can not see extended_entities in the jsonString. It’s just frustrating.

#7

Yea, especially with tweets with media entity.

#8

Problem still there :frowning:

#9

Thanks for all the reports. We will investigate. Per the announcement forum, extended entities for GIFs and Video should be populated in early Feb, but this shouldn’t affect existing image / media support.

2 Likes
#10

Thanks, right now my services is calling REST API everytime Stream API trigger. :slight_smile:

#11

The team is looking into this issue as a priority. Thanks for your patience.

3 Likes
#12

Just let you know we are having the same problem here. Media entities come empty even if the tweet has images attached.

#13

We’re experiencing the same issue. The ‘media’ property on the ‘entities’ object is completely missing.

#14

Thx Andy.

Any ETA ?

#16

We are also experiencing this issue on the streaming API.

#17

We believe the issue that caused this has been resolved - are media entities no visible to others?

1 Like
#18

I just did a test post, and received the correct data. I will keep testing but initial report would be that this looks fixed.

#19

Fixed for me too!

#20

Seems to work for me! Thanks

#21

Thanks. :slight_smile:

#22

Thanks !

#23

Great news, and apologies once again for the inconvenience and problems caused.

1 Like