Signup/Login missing in deployed Wasp app
I'm using the OpenSaaS template to translate my research Python scripts into a SaaS webapp. I am using Wasp v0.15.0 and am developing on macOS with Apple Silicon.
Everything works locally, including email signup, login/logout and access control to certain areas of the webapp based on subscriptions status or plan. However, when I deploy to fly.io following the Wasp Deployment guide, one part of the webapp does not work: in my local version, there is a login button in the top right corner of my landing page that, once logged in, turns into a dropdown menu that displays the user email address as seen in the first picture. This part is completely missing in my deployed app as seen in the second picture.
During deployment, the terminal output did not hint at any big issues except for this (for the server application), even though I do not think that this causes the described behavior:
I checked the browser console after cold-starting the client webapp and it said that it failed to load the auth part with error 502. However, when I reloaded the client webapp, this error went away. I figure that this only happened since the server side of my webapp was probably cold-started the first time it failed to load the auth component, and when I reloaded the client webapp, the auth part could actually be fetched (the errors went away) but the actual auth logic and the dropdown menu is still missing.
Do you have any idea why this whole part of the webapp is missing on fly.io? Thanks in advance!
Everything works locally, including email signup, login/logout and access control to certain areas of the webapp based on subscriptions status or plan. However, when I deploy to fly.io following the Wasp Deployment guide, one part of the webapp does not work: in my local version, there is a login button in the top right corner of my landing page that, once logged in, turns into a dropdown menu that displays the user email address as seen in the first picture. This part is completely missing in my deployed app as seen in the second picture.
During deployment, the terminal output did not hint at any big issues except for this (for the server application), even though I do not think that this causes the described behavior:
I checked the browser console after cold-starting the client webapp and it said that it failed to load the auth part with error 502. However, when I reloaded the client webapp, this error went away. I figure that this only happened since the server side of my webapp was probably cold-started the first time it failed to load the auth component, and when I reloaded the client webapp, the auth part could actually be fetched (the errors went away) but the actual auth logic and the dropdown menu is still missing.
Do you have any idea why this whole part of the webapp is missing on fly.io? Thanks in advance!
