Closed Bug 1371750 Opened 7 years ago Closed 7 years ago

Twitter website does fails to load properly in Firefox for iOS

Tracking

(platform-rel ?)

Status:

RESOLVED FIXED

Tracking Flags:

Tracking

Status

platform-rel

---

People

(Reporter: jhugman, Assigned: farhan)

References

(
URL
)

Details

(Whiteboard: [MobileCore][webcompat][sitewait][platform-rel-Twitter])

Attachments

(3 files)

Screen Shot 2017-06-09 at 6.26.45 PM.png 7 years ago James Hugman [:jhugman] [@jhugman] 70.88 KB, image/png		Details
Screen Shot 2017-06-09 at 6.26.39 PM.png 7 years ago James Hugman [:jhugman] [@jhugman] 66.69 KB, image/png		Details
IMG_3287.jpg 7 years ago Guillaume Démésy [:magsout] 172.24 KB, image/jpeg		Details

James Hugman [:jhugman] [@jhugman]

Reporter

Description

•

7 years ago

Attached image Screen Shot 2017-06-09 at 6.26.45 PM.png — Details

STR: 

1. Open Firefox for iOS
2. Goto https://twitter.com
3. Login

Or: 
1. Navigate to https://mobile.twitter.com/home while logged in.

Observed: 
The web app chrome loads, but the timeline does not load. The error message displayed is: "Sorry, Twitter is taking too long to load"

Expected: 
Twitter to load the time line correctly. 

Other info: 
This also occurs with the notifications tab of the twitter webapp, but not the searches or DMs.

Using "Request Desktop Site" will load the site.

The webapp performs as expect in Mobile Safari.

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 1

•

7 years ago

Attached image Screen Shot 2017-06-09 at 6.26.39 PM.png — Details

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 2

•

7 years ago

Also reported on twitter: https://twitter.com/hlieberman/status/873200324445712384

tracking-fxios: --- → ?

James Hugman [:jhugman] [@jhugman]

Reporter

Updated

•

7 years ago

Flags: webcompat?

Jenn Chaulk (:jchaulk)

Updated

•

7 years ago

platform-rel: --- → ?

Farhan Patel [:farhan]

Assignee

Updated

•

7 years ago

tracking-fxios: ? → 8.0+

Priority: -- → P2

Jenn Chaulk (:jchaulk)

Updated

•

7 years ago

Whiteboard: [MobileCore]

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 3

•

7 years ago

Testing Chrome, with our UA string, I cannot duplicate this behaviour. This would suggest it is not related to the UA string.

James Hugman [:jhugman] [@jhugman]

Reporter

Updated

•

7 years ago

Flags: webcompat?

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 4

•

7 years ago

Removing all UserScripts did not change any behavior.

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 5

•

7 years ago

Testing in the simulator, and the Safari Web Inspector, I am seeing home.json return with a status 500.: 

https://api.twitter.com/2/timeline/home.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&skip_status=1&cards_platform=Web-12&include_cards=1&include_ext_alt_text=true&include_reply_count=1&tweet_mode=extended&include_entities=true&include_user_entities=true&include_ext_media_color=true&send_error_codes=true&earned=1&count=20 

Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500)

{
    "errors": [
        {
            "message": "Internal error",
            "code": 131
        }
    ]
}

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 6

•

7 years ago

Fuller log from loading https://mobile.twitter.com/home

[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (runtime.6d41ecead1d838e9.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (vendor.69f9ac19fa493004.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (en.303af729525e96e5.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (main.fa740956da527fc7.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (loader.notificationsData.e53b99a2d9342222.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (bundle.App.fb95f962a03a6345.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (bundle.HomeTimeline.8121edf13e6d07d6.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (shared.1ab64633d91dc98c.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (loader.TweetCurationActionSheet.439bd375d8402097.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500) (home.json, line 0)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)
[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (loader.EntryTombstone.de7a6fe6d8288f42.js.map, line 0)
[Error] Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500) (about_me.json, line 0)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)
[Error] Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500) (home.json, line 0)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)
[Error] Failed to load resource: the server responded with a status of 500 (HTTP/2.0 500) (about_me.json, line 0)
[Error] Unhandled promise rejection – Error: Internal error — main.fa740956da527fc7.js:1:47505
Error: Internal error — main.fa740956da527fc7.js:1:47505
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366506)
	P (vendor.69f9ac19fa493004.js:1:365900)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:366377)
	exports (vendor.69f9ac19fa493004.js:1:284998)
	(anonymous function) (vendor.69f9ac19fa493004.js:1:355807)
	y (vendor.69f9ac19fa493004.js:1:355665)
	g (vendor.69f9ac19fa493004.js:1:355690)

Farhan Patel [:farhan]

Assignee

Updated

•

7 years ago

Iteration: --- → 1.24

Priority: P2 → P1

Farhan Patel [:farhan]

Assignee

Updated

•

7 years ago

Assignee: nobody → fpatel

Farhan Patel [:farhan]

Assignee

Comment 7

•

7 years ago

James I was able to replicate this bug by using our user-agent string in both chrome/safari desktop 
I used 
Mozilla/5.0 (iPhone; CPU iPhone OS 11_0 like Mac OS X) AppleWebKit/604.1.21 (KHTML, like Gecko) fxiOS/8.0b1 Mobile/15A5278f Safari/604.1.21

Dennis Schubert [:denschub]

Comment 8

•

7 years ago

Moving this into TE since it is apparently related to server-side UA sniffing. Karl, this feels important, do you mind pinging Twitter on the mailing list?

tracking-fxios: 8.0+ → ---

Component: Browser → Mobile

Flags: needinfo?(kdubost)

Product: Firefox for iOS → Tech Evangelism

Whiteboard: [MobileCore] → [MobileCore][webcompat][contactready]

Farhan Patel [:farhan]

Assignee

Comment 9

•

7 years ago

Testing different user-agent strings. Simply changing fxiOS to anything fixes this issue. 

Mozilla/5.0 (iPhone; CPU iPhone OS 11_0 like Mac OS X) AppleWebKit/604.1.21 (KHTML, like Gecko) fx.iOS/8.0b1 Mobile/15A5278f Safari/604.1.21

works!

Aaron Train [:aaronmt]

Comment 10

•

7 years ago

Worth checking the Focus UA too

Adam Stevenson [:adamopenweb]

Updated

•

7 years ago

See Also: → https://webcompat.com/issues/7434

Karl Dubost💡 :karlcow

Comment 11

•

7 years ago

The message is coming from 
https://ma-0.twimg.com/twitter-assets/responsive-web/web/ltr/bundle.Search.37370bc9b4e367e9.js:formatted

The URL which is failing with a 500.

https://api.twitter.com/1.1/timeline/user.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&skip_status=1&cards_platform=Web-12&include_cards=1&include_ext_alt_text=true&include_reply_count=1&tweet_mode=extended&include_ext_media_color=true&earned=1&pc=1&exclude_pinned_tweets=false&include_tweet_replies=true&id=2244587504&count=20

The request for this URI.

GET /1.1/timeline/user.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&skip_status=1&cards_platform=Web-12&include_cards=1&include_ext_alt_text=true&include_reply_count=1&tweet_mode=extended&include_ext_media_color=true&earned=1&pc=1&exclude_pinned_tweets=false&include_tweet_replies=true&id=2244587504&count=20 HTTP/1.1
Host: api.twitter.com
User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 11_0 like Mac OS X) AppleWebKit/604.1.21 (KHTML, like Gecko) fxiOS/8.0b1 Mobile/15A5278f Safari/604.1.21
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://mobile.twitter.com/webcompat
authorization: Bearer AAAAAAAAAAAAAAAAAAAAANRILgAAAAAAnNwIzUejRCOuH5E6I8xnZz4puTs%3D1Zv7ttfk8LF81IUq16cHjhLTvJu4FA33AGWWjCpTnA
x-guest-token: 877653053519806468
x-twitter-client-language: en
x-twitter-active-user: yes
Origin: https://mobile.twitter.com
Cookie: guest_id=v1%3A149698316215246341; personalization_id="v1_AZeVg/39xHJyoR3ZFbvnyA=="; _twitter_sess=BAh7CSIKZmxhc2hJQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNo%250ASGFzaHsABjoKQHVzZWR7ADoPY3JlYXRlZF9hdGwrCDuAmZpcAToMY3NyZl9p%250AZCIlM2NjOGRhY2RiMWNiZDk5OWYyYTQ1MGY0ZGY0YjE5NjI6B2lkIiVhZjAw%250AOThjNDg1Y2NjZDIzOWU0NDZiM2NiZjY4ZTg2Yg%253D%253D--31a049c3ed1864f306adab91ddfc1f87576a5769; _ga=GA1.2.845324185.1497242373; syndication_guest_id=v1%3A149742604273872807; __utma=43838368.845324185.1497242373.1497507102.1497507102.1; __utmc=43838368; __utmz=43838368.1497507102.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); external_referer=padhuUp37zjgzgv1mFWxJ1GGR6w5wXXNb61MrkCjQoc%3D|0|8e8t2xd8A2w%3D; _gid=GA1.2.861248835.1497936602; gt=877653053519806468; privacy_policy=1
Connection: keep-alive

Flags: needinfo?(kdubost)

Karl Dubost💡 :karlcow

Comment 12

•

7 years ago

They have been contacted today on the partner mailing-list.
Thanks everyone.

URL: https://twitter.com/webcompat

Whiteboard: [MobileCore][webcompat][contactready] → [MobileCore][webcompat][sitewait]

Desigan Chinniah [:cyberdees] [:dees] [London - GMT]

Updated

•

7 years ago

Whiteboard: [MobileCore][webcompat][sitewait] → [MobileCore][webcompat][sitewait][platform-rel-Twitter]

James Hugman [:jhugman] [@jhugman]

Reporter

Comment 13

•

7 years ago

Signing in on Firefox for iOS results in an email saying I'd signed in with Safari on iOS.

Jenn Chaulk (:jchaulk)

Updated

•

7 years ago

Iteration: 1.24 → 1.25

Guillaume Démésy [:magsout]

Comment 14

•

7 years ago

I just tested and it works on firefox iOS. Fixed

Guillaume Démésy [:magsout]

Comment 15

•

7 years ago

Attached image IMG_3287.jpg — Details

fixed on iOS

Farhan Patel [:farhan]

Assignee

Comment 16

•

7 years ago

Thanks everyone for all your help tracking down the bug. 

special thanks to the folks at twitter <3 for reaching out @mikecvet @paraga

Status: NEW → RESOLVED

Closed: 7 years ago

Resolution: --- → FIXED

Nobody; OK to take it and work on it

Updated

•

5 years ago

Product: Tech Evangelism → Web Compatibility

Nobody; OK to take it and work on it

Updated

•

2 months ago

Component: Mobile → Site Reports

You need to log in before you can comment on or make changes to this bug.