Skip to content
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

Revisit browser support #330

Closed
devbugging opened this issue Sep 16, 2022 · 1 comment · Fixed by #806
Closed

Revisit browser support #330

devbugging opened this issue Sep 16, 2022 · 1 comment · Fixed by #806
Assignees

Comments

@devbugging
Copy link
Contributor

Currently, if you want to use the playground on safari you get the warning:

You're currently using an unsupported browser to access the Flow Playground. We hope to support your browser in the future, but for now some features may not function as intended. In order to have the best experience, we recommend you use either Chrome or Firefox to access the Flow Playground.

We should revisit why is that so and how to remove this warning.

@devbugging devbugging added the V2 label Sep 16, 2022
@bthaile bthaile assigned bthaile and unassigned alse Nov 8, 2022
@bthaile
Copy link
Contributor

bthaile commented Mar 22, 2023

Error GraphQL error: user error: not authorized
Getting this error in safari console.

After research below, Still doesn't resolve the safari issue.

We got a full fix. With advice from Apollo support, we switched out whatwg-fetch for isomorphic-fetch. This allowed us to return to full functionality on Safari/iOS and maintain functionality on Chrome and Firefox.
https://community.apollographql.com/t/apollo-client-3-6-9-with-graphql-15-8-0-broken-on-webkit-safari-serverparseerror/4550/5

It looks like playground is using isomorphic-fetch which has a dep on whatwg-fetch. isomorphic-fetch is no longer actively maintained, we'd want to use a different lib.

Could use built in fetch and remove out of date fetch libs.

@devbugging devbugging moved this to 🤓 Product Research in 🌊 Flow 4D Mar 30, 2023
@bthaile bthaile added Improvement and removed V2 labels Apr 27, 2023
@nialexsan nialexsan mentioned this issue Sep 18, 2024
6 tasks
@nialexsan nialexsan mentioned this issue Sep 18, 2024
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants