1671385 - Clicking link to tweet leads to "This is not available to you" page, but refresh shows content.

Status: RESOLVED WORKSFORME

(Core :: DOM: Service Workers, defect)

Description

[Matthew Gaudet (he/him) [:mgaudet]]

Attachment: Screen Shot 2020-10-15 at 6.30.25 AM.png

I am not logged into twitter.

If I click a link to a tweet, it seems the last couple of weeks, I frequently get a page that says "This is not available to you". However, if I hit refresh, the tweet actually shows up.

(For example: https://twitter.com/patrickc/status/1316475471203360769 was what triggered this time.)

Unfortunately: I goofed this time, and forgot to check the browser console to see if there was any hint. I'm opening this bug to see if others get it, but I will return with more info if I see it reproduce.

Comment 1

[Pascal Chevrel:pascalc (PTO until April 26)]

Matthew, what version of Firefox do you have?

Comment 2

[Matthew Gaudet (he/him) [:mgaudet]]

/me facepalm

Nightly 83.0a1 (2020-10-13) was what triggered that one.

Comment 3

[Matthew Gaudet (he/him) [:mgaudet]]

Reproducing I get the following console log entries:

08:57:24.693 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 2
08:57:24.773 Loading failed for the <script> with source “https://abs.twimg.com/responsive-web/client-web/polyfills.06981235.js”. 1316475471203360769:152:1
08:57:24.773 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 9
08:57:24.969 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inject.js:221:46
08:57:25.065 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 8
08:57:25.255 Google Analytics is being shimmed by Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1493602 for details. sandbox eval code:1:9
08:57:30.106 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 6

If I refresh, I get

08:58:57.373 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:58:57.417 Some cookies are misusing the “SameSite“ attribute, so it won’t work as expected 5
08:58:57.482 Loading failed for the <script> with source “https://abs.twimg.com/responsive-web/client-web/polyfills.06981235.js”. 1316475471203360769:155:1
08:58:57.539 Loading failed for the <script> with source “https://abs.twimg.com/responsive-web/client-web/vendors~main.aee47a35.js”. 1316475471203360769:156:1
08:58:57.848 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inject.js:221:46
08:58:57.933 Source map error: Error: request failed with status 401
Resource URL: https://twitter.com/patrickc/status/1316475471203360769
Source Map URL: https://ton.twitter.com/responsive-web-internal/sourcemaps/client-web/runtime.a5c23c65.js.map
08:58:57.944 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:58:58.080 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:58:58.143 Google Analytics is being shimmed by Firefox. See https://bugzilla.mozilla.org/show_bug.cgi?id=1493602 for details. sandbox eval code:1:9
08:58:58.369 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:58:58.559 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:59:01.070 Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
08:59:03.312 Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://api2.branch.io/v1/open. (Reason: CORS request did not succeed).
08:59:03.312 The resource at “https://api2.branch.io/v1/open” was blocked because content blocking is enabled. 1316475471203360769

Not sure if there's anything helpful. Next time I'll check the browser toolbox.

Comment 4

[Matthew Gaudet (he/him) [:mgaudet]]

This time I got something slight different: a "Something went wrong" message, with in-page refresh button.

Hitting it, I see the following message on the console each time I click the button. Shift-refresh worked tho.

13:26:08.225 XHRGEThttps://twitter.com/i/api/2/timeline/conversation/1316731525547716611.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&include_can_media_tag=1&skip_status=1&cards_platform=Web-12&include_cards=1&include_ext_alt_text=true&include_quote_count=true&include_reply_count=1&tweet_mode=extended&include_entities=true&include_user_entities=true&include_ext_media_color=true&include_ext_media_availability=true&send_error_codes=true&simple_quoted_tweet=true&referrer=tweet&count=20&include_ext_has_birdwatch_notes=false&ext=mediaStats%2ChighlightedLabel
[HTTP/2 401 Unauthorized 61ms]

Comment 5

[Marcela (Please NI request to Brindusa Tot)]

I was unable to reproduce it on latest Nightly version 84.0a1 (2020-10-20) on Windows 10.
Could be related to this issue Bug 1589764?
I'll set the component, please feel free to change it if is not the correct one.

Comment 6

[Marcela (Please NI request to Brindusa Tot)]

The severity suggestion is S3 since I was not able to reproduce it and I am not aware of the impact or meaning of this error.

Comment 7

[Matthew Gaudet (he/him) [:mgaudet]]

Maybe this is ETP? I'm still seeing it regularly, but notably, I recently spotted it on Firefox iOS...

Comment 8

[Matthew Gaudet (he/him) [:mgaudet]]

Random data point: Just encountered this again, but needed to shift-reload to clear issue.

I am not sure this is the common case; unfortunately hands learned Shift-reload a little too well during the previous twitter service workers issue. Will try to pay more attention.

Comment 9

[Mathew Hodson]

This happens to me as well. Sometimes with the message "Something went wrong" and sometimes with "This is not available to you".

The symptoms are similar to older bug 1589764.

Comment 10

[Shivam Singhal [ :championshuttler ]]

I am on MacOS with Firefox 82.0.1 and its happening with me everytime. For me most of the time its "Something went wrong", refreshing page fixes the issues

Comment 11

[Matthew Gaudet (he/him) [:mgaudet]]

Note: Regular refresh seems to work most of the time.

Comment 12

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jstutte, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 13

[Dennis Schubert [:denschub]]

There hasn't been any report about this for >2 years. I'll close this as WORKSFORME, but please reopen this if you still run into this.