Login Won't Work on Latest Deploy

Support
,
1

Website: https://rolltidedad-hymnal-history.netlify.app/

Problem:

My app will not let me login even though I can login by running “rpm run dev” through my VSCode. I realized before my last deploy that I’d made an error in the “NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN” field. It was listed as “-hero-eaff1.firebaseapp.com,” and I corrected it to “hymnal-hero-eaff.firebaseapp.com” and pushed up the change on my last deploy. The link is correct on my Netlify Environmental Variables, but I’m still unable to login.

Error message in dev tools:

1a3cf1a8-ea840158aee37e7f.js:1

GET https://www.googleapis.com/identitytoolkit/v3/relyingparty/getProjectConfig?key=NEXT_PUBLIC_FIREBASE_API_KEY%3D"AIzaSyCq5s5fuLYNNeBbWSEUK71RfJZvBWYipcY"&cb=1734537216433 400 (Bad Request)

2

@MJSuttles The fact the request shows key=NEXT_PUBLIC_FIREBASE_API_KEY indicates the key hasn’t been replaced during your build (if it was supposed to be).

This previous thread provides more detail for your situation with Env Vars and Firebase API Keys:

3

Thanks! I did see that I accidentally included a closing parenthesis at the end of the NEXT_PUBLIC_FIREBASE_API_KEY. I removed it, saved the new key, and then triggered a new deployment at 7:23 AM CDT. It’s now 12:39 CDT, and it’s still “in progress.” Is this normal?

Did I do something wrong or miss a step?

4

It sounds like the build was stuck, though it seems to have successfully built at this point. Let us know if you see issues moving forward!

5

It’s still giving the same error when I click on “Log in.” It just regenerates the login page.

6

@MJSuttles If it’s still the same URL, I’m still seeing the same thing:

image
image1248×189 70 KB

The environment variable isn’t being replaced by your build.

7

Found it and corrected it. Thanks!

After saving the new variable, do I now have to trigger a new deploy?

8

Yes, variable changes need new deploy.