Issues with Apple sign-in and Firebase auth on web

Hi,

I'm working on a website that uses Firebase auth. In development, it works fine with Google, Apple, and email link sign-in options.

In production, the Google and email link options work, but Apple sign-in doesn't. I'm using separate Firebase projects for dev and production too, though I'm not sure yet if that makes a difference.

From our Apple developer account, I got the Services ID, team ID, and private key info needed for Apple sign-in in Firebase. I also made sure to add the domains (without https://) and the redirect URLs (with https://) to the Services ID settings.

But with our Production site, we always get the error "invalid_request: invalid redirect url." ("we" being me and a coworker who tried with their own Apple ID).

My first questions are:

  • As long as both domains and redirect URLs for development and production provided during Services ID setup, does it matter if I'm using the same Services ID for both?
  • Does it matter if both are using the same private key and key ID?

Thanks!

Answered by no_one_important in 738216022

I think I accidentally commented on the beginning of my thread instead of adding a reply...

Anyway, issue resolved. Configuration was correct by this point. It just wasn't when the issue was first discovered, so it's possible the bad response got stuck for a while or the configuration hadn't finished propagating through Apple's system by the time I posted this.

The issue seems to be resolved.

Some more context: when we initially tried this on our live site, configuration was incomplete. I think since configuration was incomplete at first, the response got cached in Apple's system for a little while (we tried for a couple of internal users, with and without Incognito Mode in Chrome).

All is well again.

Accepted Answer

I think I accidentally commented on the beginning of my thread instead of adding a reply...

Anyway, issue resolved. Configuration was correct by this point. It just wasn't when the issue was first discovered, so it's possible the bad response got stuck for a while or the configuration hadn't finished propagating through Apple's system by the time I posted this.

Issues with Apple sign-in and Firebase auth on web
 
 
Q