Other developers are also facing the same problem, here is the post: https://developer.apple.com/forums/thread/789011 I think we are facing the same issue, and this issue can only Apple can solve.

We are facing the same problem, if you using the Sign in with Apple JS, you probably get "invalid_client" error. see this post: https://developer.apple.com/forums/thread/789011

We are facing the same problem, see this: https://developer.apple.com/forums/thread/789011

We are facing the same problem, I think we need to wait apple to solve this problem. see this: https://developer.apple.com/forums/thread/789011

You are not alone, this happened since June 20: https://developer.apple.com/forums/thread/789011 (This thread is the most helpful. It confirms that we did nothing wrong and that we need to wait for Apple to fix it.)

same here.

Same here! https://developer.apple.com/forums/thread/789088 https://developer.apple.com/forums/thread/789011

Same here, from June 20: https://developer.apple.com/forums/thread/789011

I just submitted a Code-Level Support request to Apple, hopefully it will get their attention.

same error here.

In addition, I followed a YouTube tutorial (watch?v=8v01TaX1EJA) to set up Appwrite as my authentication service, but I encountered the same error: invalid_client. There was no helpful information in the Browser DevConsole.

I have the same problem. I've double-checked multiple times: The App Identifier The App Identifier has the Sign In with Apple capability enabled The Service Identifier The Service Identifier is linked to the correct Primary App ID and Website URLs The "Configure Sign In with Apple for Email Communication" setting has also passed SPF verification It took me almost two days to debug, but I got nothing. I referenced all of Apple’s API documentation and still couldn’t find the issue. I even tried the official Sign in with Apple JS with a minimal viable example — but that failed too. I believe Apple only verifies the client_id and redirect_uri, since the other parameters are the same as in working examples. For example, Dropbox uses this URL: https://appleid.apple.com/auth/authorize?client_id=com.dropbox.Backend&redirect_uri=https%3A%2F%2Fwww.dropbox.com%2Fapple%2Fauthcallback&response_mode=form_post&response_type=code&scope=email%20name&state=abc client_id=com.dropbox.Backend redirect_uri=https%3A%2F%2Fwww.dropbox.com%2Fapple%2Fauthcallback response_mode=form_post response_type=code scope=email%20name state=abc

same problem here