New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'MacOS install' page issue #2460
Comments
cc @kf6gpe for visibility. |
I’d be curious to know how widespread this problem is, if others could comment. Also, how likely is it that firewalls are just confused by .dev in general? A long term fix would be to modify our publishing so we publish to both sites and take away the forwarding. If this turns out to be a long term problem for folks, I’m certainly open to that, although it kind of defeats the notion of launching the .dev domain overall. @mit-mit and @timsneath and I should discuss more next week, with input of course from @Sfshaza. Thanks for reporting it!! |
I suspect our script needs to be more resilient to failure; perhaps some kind of timeout, or the script should be server-side? And of course, we always have the direct links to the SDK archive -- perhaps they should be described not merely as being 'for other release channels, and older builds'... In the short term, I'd love to understand where it's failing -- @neiljaywarner is there any way to identify where it's blocked? Unfortunately, I don't think we can take responsibility for firewalls that block legitimate parts of the internet by mirroring content elsewhere. That seems like a never-ending slippery slope. |
@timsneath I'm not sure how to find out where it is failing (a look at the html source and chrome devtools did not yield anything useful from my perspective.. didn't try charles or anything) but... I am pretty sure This issue will be resolved by the scripts being server side, which would be appreciated - especially if the same script would then affect the code block so that the file to unzip was described with the exact name from the download link instead of x.x.y - just a small bonus for people. Plus more to the point it looks broken with the "Loading..." - and, unfortunately, the SDK archives page also does not work! (similarly gives loading...) |
@timsneath Perhaps you can please try to have one of the web devs identify in base.js or similar what server is being utilized and i can ask IT to whitelist it? (I think my boss will approve it promptly) |
OK, we think we've fixed this. flutter.io is now serving out of the same firebase project as flutter.dev. There are several other bugs filed against this issue, but with less info. I'm closing those out. Please let us know if you continue to experience this problem! |
@sfshaza2 thanks so much for working onthis. although... firefox and safari both work as expected... even though chrome previously worked properly, for flutter 1.0 and flutter.io ... Is that weird? |
Thanks for checking, @neiljaywarner! |
@neiljaywarner thanks for continuing to look at this with us! Can you try this and grab a snapshot of your JavaScript console? That should be (on Chrome, anyway) the options->More Tools->Developer Tools->Console? We're wondering if there's a JavaScript error that will give us a clue. Thanks!! cc @filiph too, who's working on this with me. |
JS console log would be super helpful. FWIW, I think the solution will be somewhere around https://github.com/flutter/website/blob/master/src/_assets/js/archive.js#L7. There's nothing wrong with the function, afaik, but it looks like:
This points to something that only affects JS http requests, and only to .dev domains (or, more generally, to new TLDs). Weird, but possible. CORS, maybe? |
@filiph @kf6gpe thanks |
@neiljaywarner I made this short gif: It's showing:
|
@filiph that is very kind of you to be so thorough. The part you show in your gif is exactly the part I did see, but when i refresh the site there is no output to the console - similar to how your shows nothing in the red circle area in the console at the end of the gif. |
if it helps for diagnostic purposes, i go to a semi-random dev site https://developer.android.com/guide/topics/permissions/overview and use your procedure in the gif and the console says the below. of course, i'm not suggesting you troubleshoot that site, i'm just giving more info. thank you. Access to fetch at 'https://www.gstatic.com/images/icons/material/product/2x/youtube_48dp.png' from origin 'https://developer.android.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. |
Hmm, that's already helpful information! There's no JS error. What happens in the Network tab (two tabs right from Console)? |
Weird. Does other JavaScript on the site work? For example, can you open and close carets in the left navigation bar? Can you make another screenshot of the Network tab, but this time, just before the screenshot, hit Cmd-Shift-R (force reload)? This should make sure that every network request is tried again. |
@filiph the carets also do not open and close; sorry i forgot to point that out. |
hey! look at the comment here: #2595 |
Page URL: https://flutter.dev/docs/get-started/install/macos.html
Page source: https://github.com/flutter/website/tree/master/src/docs/get-started/install/macos.md
Since the move to using flutter.dev (I think) it now does not work on our firewall. can both sites remain intact as mirrors rather than redirecting, or somehow otherwise have this be fixed on flutter's side?
Or can i get something more specific that doesnt cause our IT dept to go "huh?: if i try to report it... Preferably a fix on Flutter's end. (see the blue Loading...) button
Description of issue:
The text was updated successfully, but these errors were encountered: