My login tab on the frontpage went missing after deployment on fly.io
:sadboi:
I followed the step on the documentation and all, I put all the necessary secret keys like google client id, sendgrid API, REACT_APP_VARIABLE_KEYS.
I went directly to /login, the front-end of google auth login is there, but it is not working.
What else am I missing?
12 Replies
Wohooo @uglybeanhead, you just became a Waspeteer level 3!
Which errors do you see in your Fly's dashboard? Do you see any errors in the browser's console?
Which Wasp version are you using?
there are no errors indicated in Fly's dashboard, browser console shows no error, i use wasp v. 0.12.2
Could you share the login page declaration in the Wasp file and the file itself?
What does it mean it is not working, how is that manifesting exactly?
Is this a new app -> is this first time you deployed it on Fly? Or it is an older app and you had it already deployed previously and maybe even migrated it from Wasp 0.11 to Wasp 0.12?
How did you start the app -> is it coming from open-saas starter template?
1. launched site, log in tab on nav bar disappeared VS 2. site from localhost 3,4,5. when go to /login manually, I hit log in, the site is not proceeding to google auth log in, it keeps spinning 6. code from LandingPage.tsx. I did not change the original template for log in that comes after DarkModeSwitcher.
edit: pic for #3
This is a new app and it's the first time deploying on Fly. I built it starting with Wasp 0.12. It came from open-saas starter template
edit: pic for #6
Update: I redeployed it and now Log in tab is showing up.
So
login won't show if isUserLoading is truthy. Which means, on Fly, isUserLoading is truthy for you at that moment.
Then, you also said, if you go to login manually, and hit google button, it keeps spinning.
Sounds to me like it is trying to reach out to the server, but server is not responding.
Can you, in browser, open dev tools and check what is happening in the "Network" tab? I think you will see that requests toward server are taking a long time, and I also expect after some time (minutes) they will fail.
Then, go on Fly, to your server, and take a look at it. What are its logs, what is being printed there? Is it getting requests from the client? Is it reporting any errors?Hi Thank you so much for your time, as updated, i just redeployed the app and it is working properly now.