Hello,
I am unable to configure Sign in with Apple on my developer account.
Whenever I try to:
Enable/disable the Sign in with Apple capability in my App ID, or
Configure a Service ID for web authentication,
the portal does not save my changes.
In the browser developer console, I consistently see this error:
Request URL: https://developer.apple.com/services-account/v1/bundleIds/XXXXXXXX
Request Method: PATCH
Status Code: 501 Not Implemented
This happens across all browsers (Safari, Chrome, Incognito) and even after clearing cache. It affects my entire account, not just one App ID.
I have already tried:
Creating a new Service ID → still fails.
Creating a new App ID → still fails.
Re-enabling the capability → save does not work.
Different browsers and devices → same result.
Has anyone else experienced this issue, and is there a known fix?
Or is this something that Apple Developer Support needs to resolve at the account level?
Sign in with Apple
RSS for tagDiscuss how to provide users the ability to sign in to your apps and websites using their Apple ID.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Is there any documentation about the server to server notification, specifically what sort of data Apple servers send to our server when there is an update to users who used Sign in with Apple?
Hey there, im getting Sign up not complete! even with the official template
https://developer.apple.com/documentation/authenticationservices/implementing-user-authentication-with-sign-in-with-apple
my developer account is recently renewed, which it has expired for a bit
i am using automatic managed signing
I have a feel something went wrong my apple developer account id,
and also this cause me getting invalid client when sign in with app on web app.
Hi Apple Developer Support,
We are implementing Sign in with Apple for our web application hosted on example.com.
In the Service ID settings, we have configured the following:
Service ID (client_id):
com.example.service.local
Web Domain:
example.com
Return URL:
https://2db2-121-160-153-88.ngrok-free.app/login/oauth2/code/apple
We also tested login via the following URL from our web application:
https://appleid.apple.com/auth/authorize?response_mode=form_post&response_type=code&client_id=com.example.service.local&scope=name%20email&state=2f9gMY1rTe12-O7Wbnb7KWe504HQ0KWBSHTKHbg9ZEY=&redirect_uri=https://2db2-121-160-153-88.ngrok-free.app/login/oauth2/code/apple
However, we’re receiving an invalid_client error after submission.
Our questions:
Is it valid to use an ngrok URL like https://2db2-121-160-153-88.ngrok-free.app/... as the Return URL for development and testing?
Does the Web Domain need to match the ngrok domain, or is it enough to register the production domain (e.g., example.com)?
Is there any propagation delay or approval process after updating the Return URL in the Service ID?
Is the client_id strictly required to match the Service ID exactly?
We would greatly appreciate any insights or best practices to help us resolve this issue.
Thank you in advance!
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags:
Sign in with Apple REST API
Sign in with Apple
Running the sample "Juice" app, which demos the Sign In With Apple flow, doesn't seem to work with Xcode 12 beta and iOS 14 beta on the simulator (worked fine on the non-beta versions and on a real device with iOS 14 beta).
Once the password for the device's Apple ID is entered, the wheel in the password field just keeps spinning. No error messages and nothing handed back over to the app from the ASAuthorizationController.
Anyone else seeing this problem ? Are there any workarounds ?
Topic:
Privacy & Security
SubTopic:
Sign in with Apple
Tags:
Sign in with Apple
Simulator
Authentication Services