-
Notifications
You must be signed in to change notification settings - Fork 208
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
Fix payments server React-related warnings (LocalizationProvider lifecycle hooks, anchor links, dependency array) #4042
Comments
Hi @parshva-b, sure thing! Thanks for offering to take this up. Yes, you'll follow the front-page README to get setup. Once you've got the servers up and running and you've setup a Firefox account locally and verified it, you should be able to hit the payments server with this link (we're working on payments / Stripe docs, but this should hit a local fake product):
You should be able to open the console from there to see the warnings. If you run into issues, you can reach the team in FxA IRC. :) |
Hey @LZoog, I am not able to hit After a little probing, I found these console print statements I have asked this question on the IRC channel mentioned as well and am awaiting a response. |
Hey @LZoog, I can now access page but I pulled the new code from master and now I can't seem to hit the page again. (Attaching a gif for reference) Essentially, I am encountering CORS errors and WebSocket errors Should I roll back to previous version or am i missing steps here. Would love your help. |
Hey @parshva-b, I'm sorry for the late response here. I looked into this just now to try to help out and it actually looks like we can close this issue. This issue was just regarding the warnings, and we can ignore the Stripe warning since we're in development here. It looks like the only warning we have now is one coming from FWIW, you can read through https://mozilla.github.io/ecosystem-platform/docs/fxa-engineering/fxa-sub-platform to see how to go through a payments server flow locally (we've had some recent changes to setup here) but you'd need to create your own free Stripe account and setup your own product and reference that URL. Kind of hairy. 😅 Thank you for volunteering to do this though, it's appreciated! |
Ignore the red errors.
┆Issue is synchronized with this Jira Bug
┆Issue Number: FXA-1028
The text was updated successfully, but these errors were encountered: