Sign in with Apple

Sign in with Apple enables users to sign into apps and websites using their Apple ID.

Sign in with Apple Documentation

Pinned TestFlight Posts

Posts under Sign in with Apple tag

7 Posts
Sort by:
Post not yet marked as solved
0 Replies
14k Views
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.
Posted
by ForumsContributor
Post not yet marked as solved
0 Replies
830 Views
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
Posted
by ForumsContributor
Post not yet marked as solved
0 Replies
146 Views
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
Posted
by ForumsContributor
Post not yet marked as solved
0 Replies
1.1k Views
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
Posted
by ForumsContributor
Post not yet marked as solved
0 Replies
0 Views
We’re launching on TestFlight to gather feedback and improve the swapping experience. This is an isolated beta build with isolated items to look through. You can upload random items and try it out. You may encounter bugs or glitches. Your feedback is essential to help us refine and grow Zèya. Any suggestions ? Send us an email.
Posted
by
Post not yet marked as solved
0 Replies
0 Views
Hey everyone! I’m looking for a few testers to try out Wanderly, an iOS app that surfaces nearby landmarks and hidden spots in your city. It uses a Mapbox map so you can see your location and keep track of the places you’ve visited. You earn XP for each place you check off, level up, and unlock badges as you explore. Would love any feedback around the UI + UX + app itself, currently not many cities are supported, I'm in the process of adding more before a proper launch.
Posted
by
Post not yet marked as solved
0 Replies
64 Views
Discover Luro, the app that's set to become your favorite tool for personal growth and productivity. We invite you to download Luro and explore how it can support your journey toward success. Be among the first to experience its intuitive design and user-friendly interface, try it today! TestFlight Link Below.
Posted
by
Post not yet marked as solved
0 Replies
357 Views
Hi everyone! 👋 I'm thrilled to share WallHub - HD & 4K Wallpapers with you! With an incredible collection of over 1 million wallpapers, WallHub is your ultimate destination for personalizing your device with breathtaking backgrounds. 🎨 What does WallHub offer? Massive Library: Access to over 1 million curated HD and 4K wallpapers that will transform your device's look Smart Categories: Easily browse through expertly organized collections to find your perfect wallpaper Daily Updates: 1000+ new wallpapers added daily to keep your collection fresh and exciting Personalized Experience: Create your account to save favorites, curate your own collections, and get personalized recommendations Custom Collections: Create and organize your own themed collections - from minimal aesthetics to vibrant landscapes Advanced Search: Find exactly what you're looking for with powerful search and filtering options Why I'm here I'm looking for beta testers to help make WallHub even better! I'm seeking enthusiastic users who: Love discovering and using high-quality wallpapers Want to be part of shaping the future of WallHub Can report bugs or issues through TestFlight Are excited to share feature suggestions and feedback How to join the beta ➡️ TestFlight link: https://testflight.apple.com/join/yvTsK9UU If TestFlight spots are full, don't worry! Stay tuned for more spots to open up. Your feedback and suggestions will help shape WallHub into the ultimate wallpaper app. Thanks for your interest in WallHub! 🙏 Let's make your device look extraordinary together. ✨
Posted
by
Post not yet marked as solved
0 Replies
341 Views
Hello Developer Forums, My friend and I are in the process of developing an app called Grafeedi. It is designed for locations that don’t have physical addresses. Think street vendors, buskers, mobile businesses, lemonade stands, yard sales and many more events or activities that would like to gain exposure without paying for expensive ads. A lot of Southeast Asia is hard to trek as a westerner due to this constraint. Some of the best locations go undiscovered due to this. We would like to gather feedback and input so that we can improve our product, and provide a wonderful user experience! Our objective from the beginning of this product was simple. To Create a collaborative map that changes from day to day along with the times! Our humble request is that you give us a try & help us improve. 🙏 Grafeedi - Features Public Markers only! Navigation deeplinking url linking Follow Friends Have Followers Attach Media to Marker Capture Media during Marker Creation “If we succeed, we will have created a digital 3rd eye” This is a bit far-fetched. But, I am not going to let doubt deteriorate my dreams. A decentralized collective 3rd eye? 😂 with a world of remote viewers. ❤️ kindest and utmost regards, Team member.
Posted
by
Post not yet marked as solved
0 Replies
423 Views
Hey! I’m excited to announce the alpha launch of Umka after a year of development + experimentation. The app lets you create a virtual pet that holds you accountable to your goals. Here's a short video to get an idea of it. We’re looking for people who want to get motivated, stay accountable, or just enjoy playing tamagotchi-like games to test the app https://testflight.apple.com/join/mswJWPFu and join our community https://discord.gg/3QpXHPdp (just made the server a second ago!) In a nutshell, this is what Umka does: Create a character: Create your own cat or dog with its own name, personality, and style. Level up in real life & the app: Your character will grow as you do. Complete your goals or study together to gain xp and acorns in the app, which you can use to progress. Stay accountable & work together: Your character will help you set goals, let you know when you’re falling behind, track your streaks, and even study along with you.
Posted
by
Post not yet marked as solved
1 Replies
566 Views
HiddenLayer is a new platform, with many unique features that provide utility, transparency, and enable infinite possible experiences. Layers are individualized spaces that can become communities, ideas, concepts, news, opinions, galleries, and more.
Posted
by