Sign in with Apple

RSS for tag

Discuss how to provide users the ability to sign in to your apps and websites using their Apple ID.

Sign in with Apple Documentation

Posts under Sign in with Apple subtopic

Post

Replies

Boosts

Views

Activity

Gathering required information for troubleshooting Sign in with Apple authorization and token requests
Hi, Before I begin my investigation, I want to explain our code-level support process for issues related to Sign in with Apple—as the issue you’re reporting may be the result of any of the following: An error in your app or web service request. A configuration issue in your Developer Account. An internal issue in the operation system or Apple ID servers. To ensure the issue is not caused by an error within your app or web service request, please review TN3107: Resolving Sign in with Apple response errors to learn more about common error causes and potential solutions when performing requests. If the technote does not help identify the cause of the error, I need more information about your app or web services to get started. To prevent sending sensitive JSON Web Tokens (JWTs) in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. Gathering required information for troubleshooting Sign in with Apple authorization and token requests For issues occurring with your native app, perform the following steps: Install the Accounts/AuthKit profile on your iOS, macOS, tvOS, watchOS, or visionOS device. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS, macOS, tvOS, watchOS, or visionOS device. Create a report in Feedback Assistant, and ensure your feedback contains the following information: the primary App ID or Bundle ID the user’s Apple ID, email address, and/or identity token the sysdiagnose gathered after reproducing the issue the timestamp of when the issue was reproduced screenshots or videos of errors and unexpected behaviors (optional) For issues occurring with your web service, ensure your feedback contains the following information: the primary App ID and Services ID the user’s Apple ID, email address, and/or identity token the failing request, including all parameter values, and error responses (if applicable) the timestamp of when the issue was reproduced (optional) screenshots or videos of errors and unexpected behaviors (optional) Important: If providing a web service request, please ensure the client secret (JWT) has an extended expiration time (exp) of at least ten (10) business days, so I have enough time to diagnose the issue. Additionally, if your request requires access token or refresh tokens, please provide refresh tokens as they do not have a time-based expiration time; most access tokens have a maximum lifetime of one (1) hour, and will expire before I have a chance to look at the issue. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above (for your native app or web service) is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
0
0
2.4k
Sep ’25
Gathering required information for troubleshooting Sign in with Apple user migration
Hi, Please see TN3159: Migrating Sign in with Apple users for an app transfer for more information on the expected end-to-end app transfer and user migration flow. Additionally, if you'd like for the iCloud and App Store engineering teams to confirm if the errors are related to a revoked authorization to previous users accounts, please submit a report via Feedback Assistant and include the following information: Gathering required information for troubleshooting Sign in with Apple user migration To prevent sending sensitive JSON Web Tokens (JWTs) in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. For issues occurring with your user migration, ensure your feedback contains the following information: the primary App ID and Services ID the client secret for the transferring team (Team A) and the recipient team (Team B) the failing request(s), including all parameter values, and error responses (if applicable) the timestamp of when the issue was reproduced (optional) screenshots or videos of errors and unexpected behaviors (optional) Important: If providing a web service request, please ensure the client secret (JWT) has an extended expiration time (exp) of at least ten (10) business days, so I have enough time to diagnose the issue. Additionally, if your request requires access token or refresh tokens, please provide refresh tokens as they do not have a time-based expiration time; most access tokens have a maximum lifetime of one (1) hour, and will expire before I have a chance to look at the issue. Submitting your feedback Before you submit via Feedback Assistant, please confirm the requested information above (for your native app or web service) is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
0
0
2.8k
Aug ’24
Gathering required information for troubleshooting Private Email Relay with Sign in with Apple
Hi, Before I begin my investigation, I want to explain our code-level support process for issues related to Sign in with Apple—as the issue you’re reporting may be the result of any of the following: An error in your app or web service request. A configuration issue in your Developer Account. An internal issue in the operation system or Apple ID servers. To ensure the issue is not caused by an error within your Private Email Replay configuration, please review Configuring your environment for Sign in with Apple to learn more about registering your email sources and authenticated domains. To prevent sending sensitive message details in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. Gathering required information for troubleshooting Private Email Relay with Sign in with Apple For issues occurring with your email delivery, ensure your feedback contains the following information: the primary App ID and Services ID the user’s Apple ID and/or email address the email message headers the Private Email Relay Service or Hide My Email message delivery failure, and SMTP error codes Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
0
0
3.0k
Sep ’25
Handling account deletions and revoking tokens for Sign in with Apple
The revoke tokens endpoint (/auth/revoke) is the only way to programmatically invalidate user tokens associated to your developer account without user interaction. This endpoint requires either a valid refresh token or access token for invalidation, as Sign in with Apple expects all apps to securely transmit and store these tokens for validation and user identity verification while managing user sessions. If you don’t have the user’s refresh token, access token, or authorization code, you must still fulfill the user’s account deletion request and meet the account deletion requirement. You'll need to follow this workaround to manually revoke the user credentials: Delete the user’s account data from your systems. Direct the user to manually revoke access for your client. Respond to the credential revoked notification to revert the client to an unauthenticated state Important: If the manual token revocation isn’t completed, the next time the user authenticates with your client using Sign in with Apple, they won’t be presented with the initial authorization flow to enter their full name, email address, or both. This is because the user credential state managed by Sign in with Apple remains unchanged and returns the.authorizedcredential state, which may also result in the system auth UI displaying the “Continue with Apple” button. Respond to the credential revoked notification Once the user’s credentials are revoked by Apple, your client will receive a notification signaling the revocation event:  For apps using the Authentication Services framework to implement Sign in with Apple, register to observe the notification named credentialRevokedNotification. For web services, if an endpoint is registered for server-to-server notifications, Apple broadcasts a notification to the specified endpoint with the consent-revokedevent type. When receiving either notification, ensure you’ve already performed the following operations to meet the requirements of account deletion: Deleted all user-related account data, including: The token used for token revocation; Any user-related data stored in your app servers; and Any user-related data store in the Keychain or securely on disk in the native app or locally on web client. Reverted the client to an unauthenticated state. Securely store user tokens for account creations For all new user account creations, follow the expected authorization flow below: Securely transmit the identity token and authorization code to your app server. Verify the identity token and validate the authorization code using the /auth/token endpoint.  Once the authorization code is validated, securely store the token response — including the identity token, refresh token, and access token. Validate the refresh token up to once per day with Apple servers (to manage the lifetime of your user session and for future token revocation requests), and obtain access tokens (for future token revocation, app transfer, or user migration requests). For information about verifying an identity token and validating tokens, visit Verifying a user and Generate and validate tokens. If you have questions about implementing these flows, including client authorization, token validation, or token revocation, please submit a Technical Support Incident.
0
0
16k
Sep ’24
Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.
137
6
34k
3h
Immediate ASAuthorizationError 1000 for some iOS 27 users — FB25610914
We are investigating intermittent native Sign in with Apple failures in TrueScreen, reported on iOS 27.0–27.2.1. Some production attempts return com.apple.AuthenticationServices.AuthorizationError code 1000 (unknown) approximately 15–18 ms after request start, before a visible authorization sheet or any credential. No underlying NSError is supplied to the app. The affected attempts record an active application, foreground-active scene and visible presentation window. The request uses ASAuthorizationAppleIDProvider with fullName/email scopes and a SHA-256 nonce. Each attempt owns its controller, actual presentation window, nonce and continuation; there is no fallback UIWindow. The native failure precedes our Firebase credential exchange. Other users successfully complete Apple sign-in on iOS 27. We do not know whether the cause is account/device state, App ID configuration, our request, the OS or an Apple service. We are not claiming a confirmed iOS regression. Feedback Assistant report: FB25610914. It includes the implementation checks and evidence limits. Our current staging simulator runs on iOS 27.0/27.2 show the normal prompt to sign in to an Apple Account in Settings, rather than reproducing the immediate production failure. We do not yet have an affected physical-device Accounts/AuthKit-profile sysdiagnose or a reliable minimal reproducer. We reviewed TN3107 and the DTS guidance for Sign in with Apple diagnostics. Which additional checks would distinguish the possible causes of this immediate native 1000? Is this an expected error for some unavailable/restricted Apple Account states, and is there a way to obtain a more actionable native error? We will supplement the Feedback report with an affected-device capture when available.
0
0
38
3d
Sign in with Apple fails for new users only since Nov 14 ("connection problem"), returning users work
Since November 14, 2026 around 08:57 CET, new users can no longer create an account in our iOS app with Sign in with Apple. Users who have used Sign in with Apple with our app before still sign in normally. What happens New user taps Sign in with Apple → Apple's sheet shows "Verbindungsproblem" (connection problem). The app receives ASAuthorizationError 1000 (unknown); no identity token is returned. Our backend never receives a request. Seen on iOS 26.3 through 27.2, multiple devices and users, all day. What still works Returning users: sign-in works. An existing user who removed our app under Settings → Sign in with Apple and signed in again succeeded, but Apple reused their existing user identifier. So only creating a new identifier seems to fail. What we checked No changes to the App ID, Sign in with Apple capability, Services IDs, keys or entitlements. Same app build created 8 new Sign in with Apple accounts on Nov 13. Membership, agreements, tax and banking all Active. Is anyone else seeing new-user Sign in with Apple failures since Nov 14? Apple folks: is there a known issue with creating new user identifiers? Bundle ID: com.paulschmidt.complete anyone else having this issue
17
14
2k
3d
Sign in with Apple fails with "Cannot Connect" on first sign-up for one app only (other apps on the same team work)
Sign in with Apple fails for one of our iOS apps (bundle ID kr.certlab.app) on the very first sign-up, while other apps from the same developer team work on the same device. Steps Tap "Sign in with Apple" in the app (ASAuthorizationAppleIDProvider, scopes: fullName, email). The Apple sheet appears with name and "Share My Email / Hide My Email". Tap "Continue". Alert: "Cannot Connect — Make sure you are connected to Wi-Fi or cellular network." The request fails with ASAuthorizationError (unknown). The app never appears under Settings > Apple Account > Sign-In & Security > Sign in with Apple, so no link is created. Same iPhone, same Wi-Fi, same Apple Account: Works: four other apps from the same team (including a brand-new first-time sign-up). They use the same Flutter code (sign_in_with_apple) and the same entitlement. Fails: kr.certlab.app only. TestFlight builds 4, 5, 7 and 8 all fail. It has never worked since the first build. What we checked App ID kr.certlab.app has Sign in with Apple enabled as a primary App ID (same setting as the working apps). The App Store provisioning profile and the app's entitlements contain com.apple.developer.applesignin = Default. We removed and re-added the capability, created a new provisioning profile and uploaded a new build. Same result. No Services IDs exist on the team, so there is no web configuration that could conflict. Another app of ours showed the same alert once today and worked on the second try. kr.certlab.app fails every time. Has anyone seen Sign in with Apple fail like this for a single App ID? Is there anything on the App ID or App Store Connect side that can block the first consent? Apple Developer Support case: 30000016304083 / Feedback: FB25591915 Thank you.
0
1
99
4d
First-time Sign in with Apple fails with error 1000 for about 45% of users on iOS 26/27 since Nov 14, returning users unaffected
Since 2026-11-14 00:56 UTC, about 45% of people creating a new account with Sign in with Apple in our App Store app fail. The sheet appears, the user picks Share or Hide My Email and confirms with Face ID, then the delegate gets ASAuthorizationError 1000 with an empty userInfo. Customers report a system "could not connect" alert just before it. What we see: Only first-time authorizations fail. Returning users sign in normally. Only iOS 26.x and 27.x. No failures on iOS 18.x. Same rate in Japan and Thailand, on Wi-Fi and cellular, with either email choice. An affected device fails on almost every attempt, then eventually one attempt succeeds. Unaffected devices succeed first time. 1,340 failed attempts from 376 devices so far. The same build signed in 107 of 111 users in the two days before it started. No app release, App ID change or backend change at the time. System Status shows Sign in with Apple as available. We have not been able to reproduce it on our own devices, so we have no sysdiagnose from a failing device yet. Feedback ID: FB25582932 Is anyone else seeing this since November 14? And could someone from Apple check the server side for our client ID?
1
2
295
4d
First-time Sign in with Apple authorisations suddenly return 1000 after the sheet completes; existing users fine
Our iOS app has used Sign in with Apple (SwiftUI SignInWithAppleButton, scopes .fullName and .email, hashed nonce) for over a year without problems. Since about 04:00 UTC on 14 November 2026, most people authorising the app for the first time fail: they tap the button, the system sheet appears, they complete it (Face ID or passcode), and 6 to 20 seconds after the tap the completion handler receives ASAuthorizationError.unknown (1000). People who have authorised the app before sign in normally. No request reaches our server in the failing case. What we see Before the onset this failure was rare: about one person a week against 15 to 24 first-time sign-ups a day. In the first 12 hours after the onset, 10 people got a result from the sheet. 7 never signed in. 3 did, two of them only on the 3rd and 5th attempt. It affects the current App Store build and the previous one, iOS 26.5 to 26.7, several iPhone models, in Canada, the US, Saudi Arabia, Qatar and Morocco, on Wi-Fi and cellular. This is separate from the immediate 1000 a device with no Apple Account returns. Those arrive within 3 seconds and we excluded them. What we checked Sign In with Apple is enabled on the App ID as a primary App ID. The com.apple.developer.applesignin entitlement is unchanged. Distribution certificates are valid and the membership is active. Nothing in the authorisation request, the button or the completion handler changed between the two builds. We could not reproduce it on our own device after revoking our grant in Settings (Stop Using) and signing in again. One possibly related fact: an updated Apple Developer Program License Agreement was issued on 29 October 2026 and we only accepted it on 14 November, about 12 hours after the failures began. We do not yet know whether the failures stopped after acceptance. Questions Can an unaccepted Program License Agreement degrade Sign in with Apple for first-time users, for example after a grace period? Has anyone else seen first-time authorisations start failing around 14 November 2026 with no change on their side? What should we capture from an affected device to identify the cause, given that we cannot reproduce it ourselves? We have no sysdiagnose from a failing attempt yet. The code-level support form requires a sample project, and this cannot be reproduced in one, so I am asking here. I can share the team ID, bundle ID and UTC timestamps of individual failed attempts privately with an Apple engineer. Update: this looks like the same thing as https://developer.apple.com/forums/thread/857623 (new users only since 14 November, returning users fine, agreements all active there). Our first failure was at 04:07 UTC on 14 November.
0
2
374
5d
Sign in with Apple fails with ASAuthorizationError.canceled (1001) / "Sign Up Not Completed" — server-side, all config verified
Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.
13
0
4.7k
1w
Authentication code for mobile phone not received
I am trying to fix an expired TestFlight build, which requires an update. However, when I attempt to log in to my developer account, I get stuck at the mobile phone authentication step. Although I have entered the correct phone number, the verification code never arrives on my device—even after multiple attempts—and the phone-based authentication option itself is not working. What should I do?
0
0
28
1w
Apple Music off-device authorization for Android TV / WebOS — supported integration and client registration
Hello, I am developing an application that integrates with Apple Music to provide a personalized music video experience for Apple Music subscribers. We are working on support for many devices like Android TV / Google TV / WebOS / etc. and would like to implement an authorization experience suitable for a television, where entering account credentials with a remote control is cumbersome. Intended authorization flow We would like to implement the following experience: The application on the TV displays a QR code or short activation code. The user scans the QR code with their phone and opens an Apple-hosted authentication and authorization page. The user signs in to their Apple Account if necessary and approves Apple Music access for the application on the TV. The TV application receives or retrieves the resulting authorization and can use it for the supported Apple Music functionality. The objective is for the TV application itself to be authorized following approval on the phone, with no need to enter the Apple Account credentials on the television. Relevant implementation evidence found on Apple’s website While researching this integration, we examined JavaScript publicly served by link.apple.com. In the following OAuth view bundle, we observed these identifiers: PartnerAuthorizationRequest isOffDeviceOAuth2Flow DEVICE_CODE Source: Apple-hosted OAuth view bundle — oauth-views-OAuth-vue.4db9105e.js In the associated OAuth initializer bundle, we observed properties including: client_id scope response_type Source: Apple-hosted OAuth initializer bundle — oauth-views-OAuthInitializer-vue.23605d03.js These elements suggest that Apple’s authorization interface includes an off-device authorization path associated with partner clients. We understand that these implementation details are not public API documentation and do not establish whether this flow is available to third-party developers. We are looking for the officially supported integration and enrollment process, if one is available. Clarification requested 1. Availability for third-party TV applications Does Apple offer a supported Apple Music authorization flow of this kind for third-party applications running on non-Apple devices? If the observed flow is limited to certain integrations or partners, what are the eligibility requirements for obtaining access? 2. Client registration and account configuration What is the official process for registering or obtaining a client_id authorized to use this flow? We have reviewed the standard MusicKit configuration involving Media IDs, Media Services keys, App Services and Capability Requests, but have not identified the configuration or application process for off-device authorization. Could you clarify whether this requires: A standard MusicKit Media ID and Media Services key; An additional service configuration or managed capability request in the Apple Developer account; A separate OAuth client registration; Or approval through an Apple Music partner program? 3. Supported integration documentation If this integration is available, where can we obtain the documentation or SDK covering: The required client configuration, request parameters and permitted scopes; Creation of the authorization request and the QR code or activation link; The mechanism by which the TV checks for completion or receives the result; The resulting token type, its intended use, and its expiration or reauthorization requirements? In particular, we would appreciate clarification on whether the resulting authorization provides a Music User Token usable by the TV application, or another token that requires a documented exchange. 4. Apple Music access on the authorized TV Which Apple Music APIs or SDKs can consume the resulting authorization? We would like to confirm its supported use with Apple Music API and MusicKit for Android, including any separate requirements for playback on the TV. Our intended design is for authorization to be issued for the TV application, rather than transferring a Music User Token issued for the phone. If this access is handled outside the standard MusicKit developer workflow, could you please identify the applicable program and enrollment process, or who to route this request to the Apple Music team responsible for partner authorization and connected-device integrations? Thank you for helping us identify the supported path for this integration. Louis
1
0
687
1w
Account Membership Expired / Team ID DNQ8PB6F6V Unreachable Due to Deprecated Profile Conflict
Apple Developer Account — Access & Subscription Issue Hello Apple Developer Support, I am writing to resolve a critical access and subscription issue with my Apple Developer account. My Apple ID (lich666black@gmail.com, Person ID: 1669634243, Developer ID: L2B6257ZS2) is the Account Holder for my organization, Khasanshin Rinat Ildarovich, IP (Team ID: DNQ8PB6F6V, App Store Connect Legal Entity ID: 90331734). Current Blocking State In App Store Connect, the organization team DNQ8PB6F6V shows that the membership has expired and prompts me to accept the updated Apple Developer Program License Agreement on the Apple Developer website. However, when I log into developer.apple.com/account, the portal backend returns an empty teams array (teams: []) with isAgentOfAnyActiveTeam: false, and defaults my web session to an old duplicate profile ("Rinat khasanshin", marked as Deprecated in ASC). Because of this, the web portal hides my organization team and only displays the "Enroll today" button. When I try to use it, the system blocks me with the error: "Your Apple Account is already associated with the Account Holder of a membership." Additionally, I cannot use the native macOS Apple Developer app to resolve this, because the app requires a newer version of macOS than what is currently running on my Mac. Request Could you please assist in: Unlinking or merging the deprecated profile; Re-syncing my active organization team (DNQ8PB6F6V); Updating the membership status so I can properly access the portal and sign the updated agreement? Thank you for your help.
1
1
113
1w
Sign in with Apple shows old app name (“Pet Companion”) after renaming to PawAide — all identifiers updated
Our app’s Sign in with Apple sheet still says “Create an account for Pet Companion,” but the app was renamed to PawAide, and every setting we control has been updated: Primary App ID (app.replit.petcompanion): description is “PawAide,” set as the Primary App ID for Sign in with Apple, no other grouped App IDs Services ID (web flow): description is “PawAide,” linked to the primary App ID above App Store Connect: app name is “PawAide” (English U.S., our only localization), and the app is live on the App Store under that name These changes were made over 11 days ago. I have revoked the app under Settings → Sign in with Apple and retested on new TestFlight builds. The old name still appears in both the native iOS sheet and the web flow. Sign-in itself works fine; only the display name is wrong. Developer Support suggested checking these same identifiers, which are all already correct. Has anyone seen the Sign in with Apple display name stay stuck like this? Is there a way to get the cached name refreshed on Apple’s side? Support case: 103007748183 Thanks for any help!
0
0
40
2w
Adding a new domain and Return URL to an existing Services ID: impact on existing users and review requirements
Hello, We use Sign in with Apple on the web with an existing Services ID that is already in production. We plan to keep using the same Services ID and change its configuration as follows: Migration rehearsal: Add a new domain and Return URL, while keeping the current ones. Production cutover: Change the name shown to users, and remove the old domain and Return URL. We would appreciate guidance on the following two points: If we add a new domain and Return URL while keeping the existing ones, will sign-in through the existing Return URL continue to work without any impact on existing users? Do any of these changes (adding or removing domains and Return URLs, or changing the name shown to users) require a review or approval by Apple before they take effect? Thank you in advance.
0
0
43
2w
Company logo in Safari’s native Sign in with Apple sheet for a website-only Services ID
We operate a website-only service using Sign in with Apple. On iPhone Safari, the native authorization sheet displays a gray tile containing “N” beside our service name. We would like that tile to display our company logo. This concerns the service icon inside Apple’s native sheet, not the Sign in with Apple button on our website. Our Services ID is associated with an existing primary App ID enabled for Sign in with Apple. As of our latest account review on October 15, 2026, our team had no App Store Connect app record for this service. We have not found a separate logo upload field in the Services ID or primary App ID settings. Apple Developer Support directed us here for technical guidance. Could Apple clarify the currently supported approach? Can a website-only service configure this logo independently? If so, what exact setting or process, asset specifications, and eligibility requirements apply? If the icon must come from a native app, what is the earliest qualifying stage: an App Store Connect record, a processed build upload, TestFlight availability, App Review submission, approval, or public release? Does a build that is never publicly released qualify? What determines the gray letter tile when the company logo is unavailable? After a qualifying icon is added or changed, what propagation/cache time should we expect, and how can we verify or refresh it safely on a physical iPhone without revoking existing users’ authorizations? If there is currently no supported solution for a website-only service, could you confirm that limitation and any supported alternative? We need to retain the existing Services ID, primary App ID, and user associations. We reviewed the web configuration guide, WWDC22 session 10122, the historical Apple Staff replies in thread 123054, and Add an app icon. These describe the primary app icon, but do not clearly establish the supported website-only path or the precise eligibility stage for this native sheet. Thank you.
1
0
1k
2w
Sign In with Apple: Migrating Users to Another Team
⚠ It'd be great to get some Apple Dev eyes on this -- it's one of my last remaining issues before submission. Regarding migrating Sign In with Apple users from team PLR8R96VKA to team Y76F338229... I'm following the migration steps at the bottom of https://developer.apple.com/documentation/signinwithapple, in the Transfers Across Teams section. My call to the /auth/usermigrationinfo endpoint results in a 400 error: invalid_request, but my request params all look correct: transfer_sub is set to the the value I got from a successful /auth/usermigrationinfo response. client_id is set to Services ID of the new team's Sign In with Apple service. client_secret was built from the new team's Key ID, Team ID and Services ID. I know it's content and format is valid because it worked fine when calling the /auth/token endpoint. I know my auth token is fine (the one I got from /auth/token)--I'm sure I'd see an auth error if it wasn't. Is there any way I can get more information about what is invalid about the request?
1
0
513
2w
Transfer of an App with Sign in with Apple Functionality
Hello, I currently have an app that includes the "Sign in with Apple" feature, and I need to transfer this app to another app team. I have reviewed all official documentation but have not found the answer I need. My situation has some specificities, and I hope to receive assistance. The .p8 key created by the original developer team has been lost, and the app’s backend does not use a .p8 key for verification—instead, it verifies by obtaining Apple’s public key. However, according to the official documentation I reviewed, obtaining a transfer identifier during the app transfer process requires a client_secret generated from the original team’s .p8 key. This has left us facing a challenge, and we have two potential approaches to address this issue: Q1: During the transfer, is it possible to skip obtaining the transfer identifier and proceed directly with the app transfer, without performing any backend operations? Is this approach feasible? Q2: If the above approach is not feasible, should we create a new .p8 key in the original team’s account and use this new key for the transfer? If a new key is generated, do we need to re-release a new version of the app before initiating the transfer? If neither of the above approaches is feasible, are there better solutions to resolve our issue? I hope to receive a response. Thank you. TN3159: Migrating Sign in with Apple users for an app transfer | Apple Developer Documentation/ https://developer.apple.com/documentation/signinwithapple/transferring-your-apps-and-users-to-another-team
3
0
1.2k
3w
Sign in with Apple user migration blocked: no private key created before app transfer
Hello Apple Developer Support, We need assistance with migrating Sign in with Apple users after completing an app transfer between two Apple Developer Teams. Current situation The app transfer has been completed and accepted by the recipient team. The recipient team has not yet released a new version on the App Store. Our production server, database, API domain, Bundle ID, and existing application user accounts remain unchanged. Before the transfer, we had never created a Sign in with Apple private key under the transferor team. Therefore, we do not have a previously generated .p8 private key for this app. This is not a case of a lost or revoked key. After the transfer, the app’s identifier is no longer listed under the transferor team’s Certificates, Identifiers & Profiles. When attempting to create a Sign in with Apple key under that team, we cannot select the transferred App ID as the primary App ID. Migration blocker According to Apple’s migration documentation, the transferor team must use its own client_secret to obtain a migration access token and generate a transfer_sub for each existing user. We are unsure how to obtain valid transferor-team credentials now that the App ID has moved to the recipient team and no private key was created before the transfer. Questions What is the supported procedure for obtaining valid transferor-team migration credentials in this situation? Can the transferor team create or configure a new Sign in with Apple private key for the transferred App ID after the transfer has been completed? If this cannot be done through the developer portal, can Apple Developer Support assist, or is there another supported migration method? Is transferring the app back to the original team, preparing the migration credentials and user transfer identifiers, and then transferring it again necessary in this situation? We would like to confirm whether this is required before making any further changes to the app’s ownership. We understand that the user migration process has a 60-day transfer window. We would appreciate guidance on resolving this credential issue promptly so that existing users can continue signing in to their original application accounts. Thank you for your assistance.
0
0
59
3w
Sign in with Apple: email claim missing from ID Token for a small subset of users
Hi everyone! We recently integrated "Sign in with Apple" into our application using standard social login flows. For the vast majority of our users, the integration works perfectly—we receive the user's email during sign-in and sign-up. However, we are noticing an edge case where a small subset of users are returning an ID token that is completely missing the email. We can't seem to reproduce this error ourselves during testing. Every time we test a sign-up or sign-in, the email payload is included exactly as expected. My Questions: Is there a specific reason why Apple would omit the email claim from the ID token? Any insights or guidance would be greatly appreciated. Thank you!
1
0
913
3w
Sign in with Apple Migration
We are in the process of transferring our existing Apple account to a new account. We read the documentation and we realized that "Sign in with Apple" users needs to be migrated via API. This API seems to require "sub" which we are not currently storing in our systems. So we are planning to "collect subs" over a period before we can start transfer. I want to make sure we are collecting correct data so I am looking for confirmation from Apple engineers on this. Should we get "sub" from "user" property in ASAuthorizationAppleIDCredential or by decoding identityToken and get "sub" from the token? I think both are same but wanted to double check. Thank you!
1
0
172
3w
Is it safe to pass a bearer token through ASWebAuthenticationSession without PKCE?
We’re trying to determine whether an iOS authentication flow is safe for production when ASWebAuthenticationSession ultimately returns a reusable backend bearer token because the authentication provider does not support a native authorization-code/PKCE exchange. We have an iOS app built with React + Capacitor that uses @capgo/capacitor-inappbrowser for Apple/Google social login. The iOS flow uses ASWebAuthenticationSession. Our backend/auth provider is Base44. Base44 supports web OAuth, but they have confirmed they do not provide a supported native authorization-code / PKCE session exchange for externally wrapped Capacitor apps. Current flow: The app starts Base44 OAuth in ASWebAuthenticationSession. Base44 completes Apple or Google authentication. Base44 redirects to an HTTPS bridge page hosted on our Base44 app domain. The bridge receives the Base44 access token. The bridge redirects to our app callback URL scheme and includes that Base44 bearer token in the callback. The active ASWebAuthenticationSession receives the callback. The app validates the callback URL, verifies a one-time random state, sets the Base44 token and immediately calls auth.me() to confirm the authenticated account. We have already hardened the flow by: using a 256-bit random one-time state expiring pending login attempts after 10 minutes binding the state to the provider and locally stored return path validating callback scheme/host/path removing unsolicited/global deep-link authentication listeners using prefersEphemeralWebBrowserSession = true scrubbing token artifacts from the hosted bridge URL/local storage not trusting callback-supplied return paths verifying the Base44 account before marking native login complete We understand that the preferred native OAuth model is authorization code + PKCE, but the backend provider does not expose that capability for this integration. My question is: Given that ASWebAuthenticationSession delivers the authentication callback to the initiating session, is passing a reusable backend bearer token through that callback still considered unsuitable for a production iOS app? If it is unsuitable, is there any secure pattern available when the authentication provider does not support a native one-time code / PKCE exchange? We also need to preserve existing Apple/Google-linked Base44 accounts, user data and subscription entitlements, so replacing the authentication backend is not a simple migration. I would particularly appreciate guidance on whether: ASWebAuthenticationSession materially mitigates custom-scheme interception in this scenario changing to a Universal Link callback would materially improve the design if the bearer token still has to be transferred this architecture would be considered acceptable for an App Store production release
0
0
66
3w
Gathering required information for troubleshooting Sign in with Apple authorization and token requests
Hi, Before I begin my investigation, I want to explain our code-level support process for issues related to Sign in with Apple—as the issue you’re reporting may be the result of any of the following: An error in your app or web service request. A configuration issue in your Developer Account. An internal issue in the operation system or Apple ID servers. To ensure the issue is not caused by an error within your app or web service request, please review TN3107: Resolving Sign in with Apple response errors to learn more about common error causes and potential solutions when performing requests. If the technote does not help identify the cause of the error, I need more information about your app or web services to get started. To prevent sending sensitive JSON Web Tokens (JWTs) in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. Gathering required information for troubleshooting Sign in with Apple authorization and token requests For issues occurring with your native app, perform the following steps: Install the Accounts/AuthKit profile on your iOS, macOS, tvOS, watchOS, or visionOS device. Reproduce the issue and make a note of the timestamp when the issue occurred, while optionally capturing screenshots or video. Gather a sysdiagnose on the same iOS, macOS, tvOS, watchOS, or visionOS device. Create a report in Feedback Assistant, and ensure your feedback contains the following information: the primary App ID or Bundle ID the user’s Apple ID, email address, and/or identity token the sysdiagnose gathered after reproducing the issue the timestamp of when the issue was reproduced screenshots or videos of errors and unexpected behaviors (optional) For issues occurring with your web service, ensure your feedback contains the following information: the primary App ID and Services ID the user’s Apple ID, email address, and/or identity token the failing request, including all parameter values, and error responses (if applicable) the timestamp of when the issue was reproduced (optional) screenshots or videos of errors and unexpected behaviors (optional) Important: If providing a web service request, please ensure the client secret (JWT) has an extended expiration time (exp) of at least ten (10) business days, so I have enough time to diagnose the issue. Additionally, if your request requires access token or refresh tokens, please provide refresh tokens as they do not have a time-based expiration time; most access tokens have a maximum lifetime of one (1) hour, and will expire before I have a chance to look at the issue. Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above (for your native app or web service) is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Replies
0
Boosts
0
Views
2.4k
Activity
Sep ’25
Gathering required information for troubleshooting Sign in with Apple user migration
Hi, Please see TN3159: Migrating Sign in with Apple users for an app transfer for more information on the expected end-to-end app transfer and user migration flow. Additionally, if you'd like for the iCloud and App Store engineering teams to confirm if the errors are related to a revoked authorization to previous users accounts, please submit a report via Feedback Assistant and include the following information: Gathering required information for troubleshooting Sign in with Apple user migration To prevent sending sensitive JSON Web Tokens (JWTs) in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. For issues occurring with your user migration, ensure your feedback contains the following information: the primary App ID and Services ID the client secret for the transferring team (Team A) and the recipient team (Team B) the failing request(s), including all parameter values, and error responses (if applicable) the timestamp of when the issue was reproduced (optional) screenshots or videos of errors and unexpected behaviors (optional) Important: If providing a web service request, please ensure the client secret (JWT) has an extended expiration time (exp) of at least ten (10) business days, so I have enough time to diagnose the issue. Additionally, if your request requires access token or refresh tokens, please provide refresh tokens as they do not have a time-based expiration time; most access tokens have a maximum lifetime of one (1) hour, and will expire before I have a chance to look at the issue. Submitting your feedback Before you submit via Feedback Assistant, please confirm the requested information above (for your native app or web service) is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Replies
0
Boosts
0
Views
2.8k
Activity
Aug ’24
Gathering required information for troubleshooting Private Email Relay with Sign in with Apple
Hi, Before I begin my investigation, I want to explain our code-level support process for issues related to Sign in with Apple—as the issue you’re reporting may be the result of any of the following: An error in your app or web service request. A configuration issue in your Developer Account. An internal issue in the operation system or Apple ID servers. To ensure the issue is not caused by an error within your Private Email Replay configuration, please review Configuring your environment for Sign in with Apple to learn more about registering your email sources and authenticated domains. To prevent sending sensitive message details in plain text, you should create a report in Feedback Assistant to share the details requested below. Additionally, if I determine the error is caused by an internal issue in the operating system or Apple ID servers, the appropriate engineering teams have access to the same information and can communicate with you directly for more information, if needed. Please follow the instructions below to submit your feedback. Gathering required information for troubleshooting Private Email Relay with Sign in with Apple For issues occurring with your email delivery, ensure your feedback contains the following information: the primary App ID and Services ID the user’s Apple ID and/or email address the email message headers the Private Email Relay Service or Hide My Email message delivery failure, and SMTP error codes Submitting your feedback Before you submit to Feedback Assistant, please confirm the requested information above is included in your feedback. Failure to provide the requested information will only delay my investigation into the reported issue within your Sign in with Apple client. After your submission to Feedback Assistant is complete, please respond in your existing Developer Forums post with the Feedback ID. Once received, I can begin my investigation and determine if this issue is caused by an error within your client, a configuration issue within your developer account, or an underlying system bug. Cheers, Paris X Pinkney |  WWDR | DTS Engineer
Replies
0
Boosts
0
Views
3.0k
Activity
Sep ’25
Handling account deletions and revoking tokens for Sign in with Apple
The revoke tokens endpoint (/auth/revoke) is the only way to programmatically invalidate user tokens associated to your developer account without user interaction. This endpoint requires either a valid refresh token or access token for invalidation, as Sign in with Apple expects all apps to securely transmit and store these tokens for validation and user identity verification while managing user sessions. If you don’t have the user’s refresh token, access token, or authorization code, you must still fulfill the user’s account deletion request and meet the account deletion requirement. You'll need to follow this workaround to manually revoke the user credentials: Delete the user’s account data from your systems. Direct the user to manually revoke access for your client. Respond to the credential revoked notification to revert the client to an unauthenticated state Important: If the manual token revocation isn’t completed, the next time the user authenticates with your client using Sign in with Apple, they won’t be presented with the initial authorization flow to enter their full name, email address, or both. This is because the user credential state managed by Sign in with Apple remains unchanged and returns the.authorizedcredential state, which may also result in the system auth UI displaying the “Continue with Apple” button. Respond to the credential revoked notification Once the user’s credentials are revoked by Apple, your client will receive a notification signaling the revocation event:  For apps using the Authentication Services framework to implement Sign in with Apple, register to observe the notification named credentialRevokedNotification. For web services, if an endpoint is registered for server-to-server notifications, Apple broadcasts a notification to the specified endpoint with the consent-revokedevent type. When receiving either notification, ensure you’ve already performed the following operations to meet the requirements of account deletion: Deleted all user-related account data, including: The token used for token revocation; Any user-related data stored in your app servers; and Any user-related data store in the Keychain or securely on disk in the native app or locally on web client. Reverted the client to an unauthenticated state. Securely store user tokens for account creations For all new user account creations, follow the expected authorization flow below: Securely transmit the identity token and authorization code to your app server. Verify the identity token and validate the authorization code using the /auth/token endpoint.  Once the authorization code is validated, securely store the token response — including the identity token, refresh token, and access token. Validate the refresh token up to once per day with Apple servers (to manage the lifetime of your user session and for future token revocation requests), and obtain access tokens (for future token revocation, app transfer, or user migration requests). For information about verifying an identity token and validating tokens, visit Verifying a user and Generate and validate tokens. If you have questions about implementing these flows, including client authorization, token validation, or token revocation, please submit a Technical Support Incident.
Replies
0
Boosts
0
Views
16k
Activity
Sep ’24
Sign in with Apple: "Sign Up Not Completed" for every App ID in our team — framework returns canceled (1001) with empty userInfo
Sign in with Apple fails for every App ID in our team (K9UFUZF2XW), on every device and every Apple ID we have tried. The system sheet appears, the user authenticates successfully, the sheet then shows "Sign Up Not Completed", and no credential is returned. The failure happens after authentication — this is not a client-side rejection. I have spent several days isolating this and have ruled out everything on my side. Posting the full evidence in case an Apple engineer can look at the server-side state for our team, and in case it helps others hitting the same wall. WHAT THE FRAMEWORK ACTUALLY RETURNS The client library we use (expo-apple-authentication) discards the original NSError, so I patched its native layer to surface the raw error verbatim. This is what ASAuthorizationController hands back to didCompleteWithError, immediately after the user authenticated and the sheet displayed "Sign Up Not Completed": ASAuthorizationError .canceled (rawValue = 1001) domain = com.apple.AuthenticationServices.AuthorizationError code = 1001 desc = The operation couldn't be completed. (com.apple.AuthenticationServices.AuthorizationError, error 1001) userInfo: NSUnderlyingError: So the framework reports a user cancellation that never happened, with a completely empty userInfo and no underlying error. There is no diagnostic information on the client at all — I cannot debug this any further from my side, because the information does not exist there. Note: the same failure surfaces as a different error code depending on the client library version — .unknown (1000) with the older version, .canceled (1001) with the current one. The user-visible behaviour ("Sign Up Not Completed") is identical in both. So the error code is not a reliable signal here. WHAT I RULED OUT Not the App ID. I created a brand-new App ID (kz.auraai.ios) with Sign in with Apple enabled as a primary App ID, built a fresh binary, tested on the same device with the same Apple ID — identical failure. Two independent App IDs in the same team fail the same way. Not the entitlement. Verified inside the signed binary, not just in the portal: application-identifier = K9UFUZF2XW.kz.auraai.ios com.apple.developer.applesignin = ["Default"] I also tried the workaround suggested elsewhere on these forums (removing the entitlement while keeping the capability in the portal). That made it strictly worse: iOS then rejects the request instantly, without showing the sheet at all. Which confirms iOS reads the entitlement correctly, the sheet works, and the user authenticates — the failure is downstream of all of that. No stray or wildcard App IDs. A commonly cited cause is other App IDs in the team lacking the entitlement. I enumerated the whole team via the App Store Connect API: it contains exactly two App IDs, both with APPLE_ID_AUTH = PRIMARY_APP_CONSENT. No wildcard identifiers exist. Not the Apple ID, the device, or the iOS version. The same Apple ID, on the same device, with the same iOS, signs in successfully through another app belonging to a different team (Expo Go, host.exp.Exponent) — a valid identity token is returned. A second, unrelated Apple ID on another device fails in my app in exactly the same way. So this is not scoped to one account: it affects every user of the app. Agreements and membership are in good standing. Program License Agreement accepted 30 June 2026; Developer Agreement accepted 26 June 2026; membership active. Both distribution types fail. TestFlight and ad-hoc. WHAT IS LEFT After all of the above, the only variable that differs between the working case (a different team's app, same device, same Apple ID) and the failing case (my app) is the Apple Developer team itself. This exact signature — sheet renders fully, final server submit fails, "Sign Up Not Completed", delegate reports canceled with no userInfo, not reproducible in other apps on the same device — is documented in thread 122458 ("Error: Sign-Up Not Completed"). In that case it affected multiple developers, including Apple's own sample app, and was ultimately resolved by Apple on the server side, with a recurrence reported in June 2025. THE ASK Could someone from Apple check the server-side Sign in with Apple registration for team K9UFUZF2XW (App IDs kz.auraai.app and kz.auraai.ios)? I am not looking for configuration advice — I have exhausted the client side and there is nothing left to configure. This looks like the same server-side state that was fixed in the referenced cases. Feedback Assistant: FB23716661 (includes sysdiagnose with the Accounts/AuthKit profile, timestamp, and video of the failure). This is currently blocking us: because Sign in with Apple works for none of our users, guideline 4.8 prevents us from offering Google Sign-In, so we are shipping with email-only login. Happy to provide the binary, entitlements dump, or a fresh sysdiagnose on request.
Replies
137
Boosts
6
Views
34k
Activity
3h
Immediate ASAuthorizationError 1000 for some iOS 27 users — FB25610914
We are investigating intermittent native Sign in with Apple failures in TrueScreen, reported on iOS 27.0–27.2.1. Some production attempts return com.apple.AuthenticationServices.AuthorizationError code 1000 (unknown) approximately 15–18 ms after request start, before a visible authorization sheet or any credential. No underlying NSError is supplied to the app. The affected attempts record an active application, foreground-active scene and visible presentation window. The request uses ASAuthorizationAppleIDProvider with fullName/email scopes and a SHA-256 nonce. Each attempt owns its controller, actual presentation window, nonce and continuation; there is no fallback UIWindow. The native failure precedes our Firebase credential exchange. Other users successfully complete Apple sign-in on iOS 27. We do not know whether the cause is account/device state, App ID configuration, our request, the OS or an Apple service. We are not claiming a confirmed iOS regression. Feedback Assistant report: FB25610914. It includes the implementation checks and evidence limits. Our current staging simulator runs on iOS 27.0/27.2 show the normal prompt to sign in to an Apple Account in Settings, rather than reproducing the immediate production failure. We do not yet have an affected physical-device Accounts/AuthKit-profile sysdiagnose or a reliable minimal reproducer. We reviewed TN3107 and the DTS guidance for Sign in with Apple diagnostics. Which additional checks would distinguish the possible causes of this immediate native 1000? Is this an expected error for some unavailable/restricted Apple Account states, and is there a way to obtain a more actionable native error? We will supplement the Feedback report with an affected-device capture when available.
Replies
0
Boosts
0
Views
38
Activity
3d
Sign in with Apple fails for new users only since Nov 14 ("connection problem"), returning users work
Since November 14, 2026 around 08:57 CET, new users can no longer create an account in our iOS app with Sign in with Apple. Users who have used Sign in with Apple with our app before still sign in normally. What happens New user taps Sign in with Apple → Apple's sheet shows "Verbindungsproblem" (connection problem). The app receives ASAuthorizationError 1000 (unknown); no identity token is returned. Our backend never receives a request. Seen on iOS 26.3 through 27.2, multiple devices and users, all day. What still works Returning users: sign-in works. An existing user who removed our app under Settings → Sign in with Apple and signed in again succeeded, but Apple reused their existing user identifier. So only creating a new identifier seems to fail. What we checked No changes to the App ID, Sign in with Apple capability, Services IDs, keys or entitlements. Same app build created 8 new Sign in with Apple accounts on Nov 13. Membership, agreements, tax and banking all Active. Is anyone else seeing new-user Sign in with Apple failures since Nov 14? Apple folks: is there a known issue with creating new user identifiers? Bundle ID: com.paulschmidt.complete anyone else having this issue
Replies
17
Boosts
14
Views
2k
Activity
3d
Sign in with Apple fails with "Cannot Connect" on first sign-up for one app only (other apps on the same team work)
Sign in with Apple fails for one of our iOS apps (bundle ID kr.certlab.app) on the very first sign-up, while other apps from the same developer team work on the same device. Steps Tap "Sign in with Apple" in the app (ASAuthorizationAppleIDProvider, scopes: fullName, email). The Apple sheet appears with name and "Share My Email / Hide My Email". Tap "Continue". Alert: "Cannot Connect — Make sure you are connected to Wi-Fi or cellular network." The request fails with ASAuthorizationError (unknown). The app never appears under Settings > Apple Account > Sign-In & Security > Sign in with Apple, so no link is created. Same iPhone, same Wi-Fi, same Apple Account: Works: four other apps from the same team (including a brand-new first-time sign-up). They use the same Flutter code (sign_in_with_apple) and the same entitlement. Fails: kr.certlab.app only. TestFlight builds 4, 5, 7 and 8 all fail. It has never worked since the first build. What we checked App ID kr.certlab.app has Sign in with Apple enabled as a primary App ID (same setting as the working apps). The App Store provisioning profile and the app's entitlements contain com.apple.developer.applesignin = Default. We removed and re-added the capability, created a new provisioning profile and uploaded a new build. Same result. No Services IDs exist on the team, so there is no web configuration that could conflict. Another app of ours showed the same alert once today and worked on the second try. kr.certlab.app fails every time. Has anyone seen Sign in with Apple fail like this for a single App ID? Is there anything on the App ID or App Store Connect side that can block the first consent? Apple Developer Support case: 30000016304083 / Feedback: FB25591915 Thank you.
Replies
0
Boosts
1
Views
99
Activity
4d
First-time Sign in with Apple fails with error 1000 for about 45% of users on iOS 26/27 since Nov 14, returning users unaffected
Since 2026-11-14 00:56 UTC, about 45% of people creating a new account with Sign in with Apple in our App Store app fail. The sheet appears, the user picks Share or Hide My Email and confirms with Face ID, then the delegate gets ASAuthorizationError 1000 with an empty userInfo. Customers report a system "could not connect" alert just before it. What we see: Only first-time authorizations fail. Returning users sign in normally. Only iOS 26.x and 27.x. No failures on iOS 18.x. Same rate in Japan and Thailand, on Wi-Fi and cellular, with either email choice. An affected device fails on almost every attempt, then eventually one attempt succeeds. Unaffected devices succeed first time. 1,340 failed attempts from 376 devices so far. The same build signed in 107 of 111 users in the two days before it started. No app release, App ID change or backend change at the time. System Status shows Sign in with Apple as available. We have not been able to reproduce it on our own devices, so we have no sysdiagnose from a failing device yet. Feedback ID: FB25582932 Is anyone else seeing this since November 14? And could someone from Apple check the server side for our client ID?
Replies
1
Boosts
2
Views
295
Activity
4d
First-time Sign in with Apple authorisations suddenly return 1000 after the sheet completes; existing users fine
Our iOS app has used Sign in with Apple (SwiftUI SignInWithAppleButton, scopes .fullName and .email, hashed nonce) for over a year without problems. Since about 04:00 UTC on 14 November 2026, most people authorising the app for the first time fail: they tap the button, the system sheet appears, they complete it (Face ID or passcode), and 6 to 20 seconds after the tap the completion handler receives ASAuthorizationError.unknown (1000). People who have authorised the app before sign in normally. No request reaches our server in the failing case. What we see Before the onset this failure was rare: about one person a week against 15 to 24 first-time sign-ups a day. In the first 12 hours after the onset, 10 people got a result from the sheet. 7 never signed in. 3 did, two of them only on the 3rd and 5th attempt. It affects the current App Store build and the previous one, iOS 26.5 to 26.7, several iPhone models, in Canada, the US, Saudi Arabia, Qatar and Morocco, on Wi-Fi and cellular. This is separate from the immediate 1000 a device with no Apple Account returns. Those arrive within 3 seconds and we excluded them. What we checked Sign In with Apple is enabled on the App ID as a primary App ID. The com.apple.developer.applesignin entitlement is unchanged. Distribution certificates are valid and the membership is active. Nothing in the authorisation request, the button or the completion handler changed between the two builds. We could not reproduce it on our own device after revoking our grant in Settings (Stop Using) and signing in again. One possibly related fact: an updated Apple Developer Program License Agreement was issued on 29 October 2026 and we only accepted it on 14 November, about 12 hours after the failures began. We do not yet know whether the failures stopped after acceptance. Questions Can an unaccepted Program License Agreement degrade Sign in with Apple for first-time users, for example after a grace period? Has anyone else seen first-time authorisations start failing around 14 November 2026 with no change on their side? What should we capture from an affected device to identify the cause, given that we cannot reproduce it ourselves? We have no sysdiagnose from a failing attempt yet. The code-level support form requires a sample project, and this cannot be reproduced in one, so I am asking here. I can share the team ID, bundle ID and UTC timestamps of individual failed attempts privately with an Apple engineer. Update: this looks like the same thing as https://developer.apple.com/forums/thread/857623 (new users only since 14 November, returning users fine, agreements all active there). Our first failure was at 04:07 UTC on 14 November.
Replies
0
Boosts
2
Views
374
Activity
5d
Sign in with Apple fails with ASAuthorizationError.canceled (1001) / "Sign Up Not Completed" — server-side, all config verified
Our app's Sign in with Apple never completes. Apple's create-account sheet renders fully (name + share/hide-my-email step), then the final server submit fails and shows the "Sign Up Not Completed" sheet. The authorization callback returns ASAuthorizationError.canceled (1001) with no userInfo — even though the user did not cancel. Reproduced on multiple physical devices and multiple Apple IDs (all with 2FA), on iOS 26.5.1, since our first build. Team ID: 24XS837728 App ID: C54N9Q226H (bundle com.sucsessmaperrs.careerAssessmentApp) Verified on our side: com.apple.developer.applesignin = [Default] present in the distribution build (codesign -d --entitlements); embedded profile is the explicit App Store profile for the App ID (not wildcard). App ID has Sign in with Apple enabled as a primary App ID; capability deleted + recreated via the App Store Connect API today, no change. Firebase consumes the identity token; the failure is in Apple's UI before our code runs. App Store Connect agreements are clean. Key isolating fact: the same Apple ID on the same device completes a first-time Sign in with Apple sign-up in other third-party apps — only ours fails. So the cause appears scoped to our App ID / team on Apple's side, not the device, the Apple ID, 2FA, or our client code. This matches the widespread server-side "Sign Up Not Completed" failure in thread 675756 — same signature: multiple devices/Apple IDs, no console error, the failure delegate surfacing only as "cancel", newly created apps affected, even Apple's own sample app failing — which Apple ultimately resolved server-side (with a recurrence reported June 2025). Note this is the native ASAuthorizationController flow, not the REST/web flow, so the query-parameter percent-encoding fix from thread 122458 does not apply here. Could an Apple engineer check the server-side Sign in with Apple / account-association state for App ID C54N9Q226H (Team 24XS837728)? Happy to provide a screen recording or sysdiagnose.
Replies
13
Boosts
0
Views
4.7k
Activity
1w
Authentication code for mobile phone not received
I am trying to fix an expired TestFlight build, which requires an update. However, when I attempt to log in to my developer account, I get stuck at the mobile phone authentication step. Although I have entered the correct phone number, the verification code never arrives on my device—even after multiple attempts—and the phone-based authentication option itself is not working. What should I do?
Replies
0
Boosts
0
Views
28
Activity
1w
Apple Music off-device authorization for Android TV / WebOS — supported integration and client registration
Hello, I am developing an application that integrates with Apple Music to provide a personalized music video experience for Apple Music subscribers. We are working on support for many devices like Android TV / Google TV / WebOS / etc. and would like to implement an authorization experience suitable for a television, where entering account credentials with a remote control is cumbersome. Intended authorization flow We would like to implement the following experience: The application on the TV displays a QR code or short activation code. The user scans the QR code with their phone and opens an Apple-hosted authentication and authorization page. The user signs in to their Apple Account if necessary and approves Apple Music access for the application on the TV. The TV application receives or retrieves the resulting authorization and can use it for the supported Apple Music functionality. The objective is for the TV application itself to be authorized following approval on the phone, with no need to enter the Apple Account credentials on the television. Relevant implementation evidence found on Apple’s website While researching this integration, we examined JavaScript publicly served by link.apple.com. In the following OAuth view bundle, we observed these identifiers: PartnerAuthorizationRequest isOffDeviceOAuth2Flow DEVICE_CODE Source: Apple-hosted OAuth view bundle — oauth-views-OAuth-vue.4db9105e.js In the associated OAuth initializer bundle, we observed properties including: client_id scope response_type Source: Apple-hosted OAuth initializer bundle — oauth-views-OAuthInitializer-vue.23605d03.js These elements suggest that Apple’s authorization interface includes an off-device authorization path associated with partner clients. We understand that these implementation details are not public API documentation and do not establish whether this flow is available to third-party developers. We are looking for the officially supported integration and enrollment process, if one is available. Clarification requested 1. Availability for third-party TV applications Does Apple offer a supported Apple Music authorization flow of this kind for third-party applications running on non-Apple devices? If the observed flow is limited to certain integrations or partners, what are the eligibility requirements for obtaining access? 2. Client registration and account configuration What is the official process for registering or obtaining a client_id authorized to use this flow? We have reviewed the standard MusicKit configuration involving Media IDs, Media Services keys, App Services and Capability Requests, but have not identified the configuration or application process for off-device authorization. Could you clarify whether this requires: A standard MusicKit Media ID and Media Services key; An additional service configuration or managed capability request in the Apple Developer account; A separate OAuth client registration; Or approval through an Apple Music partner program? 3. Supported integration documentation If this integration is available, where can we obtain the documentation or SDK covering: The required client configuration, request parameters and permitted scopes; Creation of the authorization request and the QR code or activation link; The mechanism by which the TV checks for completion or receives the result; The resulting token type, its intended use, and its expiration or reauthorization requirements? In particular, we would appreciate clarification on whether the resulting authorization provides a Music User Token usable by the TV application, or another token that requires a documented exchange. 4. Apple Music access on the authorized TV Which Apple Music APIs or SDKs can consume the resulting authorization? We would like to confirm its supported use with Apple Music API and MusicKit for Android, including any separate requirements for playback on the TV. Our intended design is for authorization to be issued for the TV application, rather than transferring a Music User Token issued for the phone. If this access is handled outside the standard MusicKit developer workflow, could you please identify the applicable program and enrollment process, or who to route this request to the Apple Music team responsible for partner authorization and connected-device integrations? Thank you for helping us identify the supported path for this integration. Louis
Replies
1
Boosts
0
Views
687
Activity
1w
Account Membership Expired / Team ID DNQ8PB6F6V Unreachable Due to Deprecated Profile Conflict
Apple Developer Account — Access & Subscription Issue Hello Apple Developer Support, I am writing to resolve a critical access and subscription issue with my Apple Developer account. My Apple ID (lich666black@gmail.com, Person ID: 1669634243, Developer ID: L2B6257ZS2) is the Account Holder for my organization, Khasanshin Rinat Ildarovich, IP (Team ID: DNQ8PB6F6V, App Store Connect Legal Entity ID: 90331734). Current Blocking State In App Store Connect, the organization team DNQ8PB6F6V shows that the membership has expired and prompts me to accept the updated Apple Developer Program License Agreement on the Apple Developer website. However, when I log into developer.apple.com/account, the portal backend returns an empty teams array (teams: []) with isAgentOfAnyActiveTeam: false, and defaults my web session to an old duplicate profile ("Rinat khasanshin", marked as Deprecated in ASC). Because of this, the web portal hides my organization team and only displays the "Enroll today" button. When I try to use it, the system blocks me with the error: "Your Apple Account is already associated with the Account Holder of a membership." Additionally, I cannot use the native macOS Apple Developer app to resolve this, because the app requires a newer version of macOS than what is currently running on my Mac. Request Could you please assist in: Unlinking or merging the deprecated profile; Re-syncing my active organization team (DNQ8PB6F6V); Updating the membership status so I can properly access the portal and sign the updated agreement? Thank you for your help.
Replies
1
Boosts
1
Views
113
Activity
1w
Sign in with Apple shows old app name (“Pet Companion”) after renaming to PawAide — all identifiers updated
Our app’s Sign in with Apple sheet still says “Create an account for Pet Companion,” but the app was renamed to PawAide, and every setting we control has been updated: Primary App ID (app.replit.petcompanion): description is “PawAide,” set as the Primary App ID for Sign in with Apple, no other grouped App IDs Services ID (web flow): description is “PawAide,” linked to the primary App ID above App Store Connect: app name is “PawAide” (English U.S., our only localization), and the app is live on the App Store under that name These changes were made over 11 days ago. I have revoked the app under Settings → Sign in with Apple and retested on new TestFlight builds. The old name still appears in both the native iOS sheet and the web flow. Sign-in itself works fine; only the display name is wrong. Developer Support suggested checking these same identifiers, which are all already correct. Has anyone seen the Sign in with Apple display name stay stuck like this? Is there a way to get the cached name refreshed on Apple’s side? Support case: 103007748183 Thanks for any help!
Replies
0
Boosts
0
Views
40
Activity
2w
Adding a new domain and Return URL to an existing Services ID: impact on existing users and review requirements
Hello, We use Sign in with Apple on the web with an existing Services ID that is already in production. We plan to keep using the same Services ID and change its configuration as follows: Migration rehearsal: Add a new domain and Return URL, while keeping the current ones. Production cutover: Change the name shown to users, and remove the old domain and Return URL. We would appreciate guidance on the following two points: If we add a new domain and Return URL while keeping the existing ones, will sign-in through the existing Return URL continue to work without any impact on existing users? Do any of these changes (adding or removing domains and Return URLs, or changing the name shown to users) require a review or approval by Apple before they take effect? Thank you in advance.
Replies
0
Boosts
0
Views
43
Activity
2w
Company logo in Safari’s native Sign in with Apple sheet for a website-only Services ID
We operate a website-only service using Sign in with Apple. On iPhone Safari, the native authorization sheet displays a gray tile containing “N” beside our service name. We would like that tile to display our company logo. This concerns the service icon inside Apple’s native sheet, not the Sign in with Apple button on our website. Our Services ID is associated with an existing primary App ID enabled for Sign in with Apple. As of our latest account review on October 15, 2026, our team had no App Store Connect app record for this service. We have not found a separate logo upload field in the Services ID or primary App ID settings. Apple Developer Support directed us here for technical guidance. Could Apple clarify the currently supported approach? Can a website-only service configure this logo independently? If so, what exact setting or process, asset specifications, and eligibility requirements apply? If the icon must come from a native app, what is the earliest qualifying stage: an App Store Connect record, a processed build upload, TestFlight availability, App Review submission, approval, or public release? Does a build that is never publicly released qualify? What determines the gray letter tile when the company logo is unavailable? After a qualifying icon is added or changed, what propagation/cache time should we expect, and how can we verify or refresh it safely on a physical iPhone without revoking existing users’ authorizations? If there is currently no supported solution for a website-only service, could you confirm that limitation and any supported alternative? We need to retain the existing Services ID, primary App ID, and user associations. We reviewed the web configuration guide, WWDC22 session 10122, the historical Apple Staff replies in thread 123054, and Add an app icon. These describe the primary app icon, but do not clearly establish the supported website-only path or the precise eligibility stage for this native sheet. Thank you.
Replies
1
Boosts
0
Views
1k
Activity
2w
Sign In with Apple: Migrating Users to Another Team
⚠ It'd be great to get some Apple Dev eyes on this -- it's one of my last remaining issues before submission. Regarding migrating Sign In with Apple users from team PLR8R96VKA to team Y76F338229... I'm following the migration steps at the bottom of https://developer.apple.com/documentation/signinwithapple, in the Transfers Across Teams section. My call to the /auth/usermigrationinfo endpoint results in a 400 error: invalid_request, but my request params all look correct: transfer_sub is set to the the value I got from a successful /auth/usermigrationinfo response. client_id is set to Services ID of the new team's Sign In with Apple service. client_secret was built from the new team's Key ID, Team ID and Services ID. I know it's content and format is valid because it worked fine when calling the /auth/token endpoint. I know my auth token is fine (the one I got from /auth/token)--I'm sure I'd see an auth error if it wasn't. Is there any way I can get more information about what is invalid about the request?
Replies
1
Boosts
0
Views
513
Activity
2w
Transfer of an App with Sign in with Apple Functionality
Hello, I currently have an app that includes the "Sign in with Apple" feature, and I need to transfer this app to another app team. I have reviewed all official documentation but have not found the answer I need. My situation has some specificities, and I hope to receive assistance. The .p8 key created by the original developer team has been lost, and the app’s backend does not use a .p8 key for verification—instead, it verifies by obtaining Apple’s public key. However, according to the official documentation I reviewed, obtaining a transfer identifier during the app transfer process requires a client_secret generated from the original team’s .p8 key. This has left us facing a challenge, and we have two potential approaches to address this issue: Q1: During the transfer, is it possible to skip obtaining the transfer identifier and proceed directly with the app transfer, without performing any backend operations? Is this approach feasible? Q2: If the above approach is not feasible, should we create a new .p8 key in the original team’s account and use this new key for the transfer? If a new key is generated, do we need to re-release a new version of the app before initiating the transfer? If neither of the above approaches is feasible, are there better solutions to resolve our issue? I hope to receive a response. Thank you. TN3159: Migrating Sign in with Apple users for an app transfer | Apple Developer Documentation/ https://developer.apple.com/documentation/signinwithapple/transferring-your-apps-and-users-to-another-team
Replies
3
Boosts
0
Views
1.2k
Activity
3w
Sign in with Apple user migration blocked: no private key created before app transfer
Hello Apple Developer Support, We need assistance with migrating Sign in with Apple users after completing an app transfer between two Apple Developer Teams. Current situation The app transfer has been completed and accepted by the recipient team. The recipient team has not yet released a new version on the App Store. Our production server, database, API domain, Bundle ID, and existing application user accounts remain unchanged. Before the transfer, we had never created a Sign in with Apple private key under the transferor team. Therefore, we do not have a previously generated .p8 private key for this app. This is not a case of a lost or revoked key. After the transfer, the app’s identifier is no longer listed under the transferor team’s Certificates, Identifiers & Profiles. When attempting to create a Sign in with Apple key under that team, we cannot select the transferred App ID as the primary App ID. Migration blocker According to Apple’s migration documentation, the transferor team must use its own client_secret to obtain a migration access token and generate a transfer_sub for each existing user. We are unsure how to obtain valid transferor-team credentials now that the App ID has moved to the recipient team and no private key was created before the transfer. Questions What is the supported procedure for obtaining valid transferor-team migration credentials in this situation? Can the transferor team create or configure a new Sign in with Apple private key for the transferred App ID after the transfer has been completed? If this cannot be done through the developer portal, can Apple Developer Support assist, or is there another supported migration method? Is transferring the app back to the original team, preparing the migration credentials and user transfer identifiers, and then transferring it again necessary in this situation? We would like to confirm whether this is required before making any further changes to the app’s ownership. We understand that the user migration process has a 60-day transfer window. We would appreciate guidance on resolving this credential issue promptly so that existing users can continue signing in to their original application accounts. Thank you for your assistance.
Replies
0
Boosts
0
Views
59
Activity
3w
Sign in with Apple: email claim missing from ID Token for a small subset of users
Hi everyone! We recently integrated "Sign in with Apple" into our application using standard social login flows. For the vast majority of our users, the integration works perfectly—we receive the user's email during sign-in and sign-up. However, we are noticing an edge case where a small subset of users are returning an ID token that is completely missing the email. We can't seem to reproduce this error ourselves during testing. Every time we test a sign-up or sign-in, the email payload is included exactly as expected. My Questions: Is there a specific reason why Apple would omit the email claim from the ID token? Any insights or guidance would be greatly appreciated. Thank you!
Replies
1
Boosts
0
Views
913
Activity
3w
Sign in with Apple Migration
We are in the process of transferring our existing Apple account to a new account. We read the documentation and we realized that "Sign in with Apple" users needs to be migrated via API. This API seems to require "sub" which we are not currently storing in our systems. So we are planning to "collect subs" over a period before we can start transfer. I want to make sure we are collecting correct data so I am looking for confirmation from Apple engineers on this. Should we get "sub" from "user" property in ASAuthorizationAppleIDCredential or by decoding identityToken and get "sub" from the token? I think both are same but wanted to double check. Thank you!
Replies
1
Boosts
0
Views
172
Activity
3w
Is it safe to pass a bearer token through ASWebAuthenticationSession without PKCE?
We’re trying to determine whether an iOS authentication flow is safe for production when ASWebAuthenticationSession ultimately returns a reusable backend bearer token because the authentication provider does not support a native authorization-code/PKCE exchange. We have an iOS app built with React + Capacitor that uses @capgo/capacitor-inappbrowser for Apple/Google social login. The iOS flow uses ASWebAuthenticationSession. Our backend/auth provider is Base44. Base44 supports web OAuth, but they have confirmed they do not provide a supported native authorization-code / PKCE session exchange for externally wrapped Capacitor apps. Current flow: The app starts Base44 OAuth in ASWebAuthenticationSession. Base44 completes Apple or Google authentication. Base44 redirects to an HTTPS bridge page hosted on our Base44 app domain. The bridge receives the Base44 access token. The bridge redirects to our app callback URL scheme and includes that Base44 bearer token in the callback. The active ASWebAuthenticationSession receives the callback. The app validates the callback URL, verifies a one-time random state, sets the Base44 token and immediately calls auth.me() to confirm the authenticated account. We have already hardened the flow by: using a 256-bit random one-time state expiring pending login attempts after 10 minutes binding the state to the provider and locally stored return path validating callback scheme/host/path removing unsolicited/global deep-link authentication listeners using prefersEphemeralWebBrowserSession = true scrubbing token artifacts from the hosted bridge URL/local storage not trusting callback-supplied return paths verifying the Base44 account before marking native login complete We understand that the preferred native OAuth model is authorization code + PKCE, but the backend provider does not expose that capability for this integration. My question is: Given that ASWebAuthenticationSession delivers the authentication callback to the initiating session, is passing a reusable backend bearer token through that callback still considered unsuitable for a production iOS app? If it is unsuitable, is there any secure pattern available when the authentication provider does not support a native one-time code / PKCE exchange? We also need to preserve existing Apple/Google-linked Base44 accounts, user data and subscription entitlements, so replacing the authentication backend is not a simple migration. I would particularly appreciate guidance on whether: ASWebAuthenticationSession materially mitigates custom-scheme interception in this scenario changing to a Universal Link callback would materially improve the design if the bearer token still has to be transferred this architecture would be considered acceptable for an App Store production release
Replies
0
Boosts
0
Views
66
Activity
3w