You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[$250] iOS - Login - Unable to sign in using Apple sign in #64622
Version Number: v9.1.69-2 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail:#51257 Email or phone of affected tester (no customers):applausetester+dt109@applause.expensifail.com Issue reported by: Applause Internal Team Device used: iPhone 8 App Component: Other
Action Performed:
Navigate to staging App on iOS
Try signing in with the Apple sign in
Expected Result:
Able to sign in with the apple sign in
Actual Result:
Error is shown on the login field and Unable to sign in
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Hi Here are some possible Causes for Apple Sign-In Failure
Missing Capabilities
– Sign In with Apple not enabled in Xcode project settings.
Wrong Bundle ID or Service ID
– Mismatch between app’s bundle ID and what’s set up on Apple Developer portal.
Unsupported Devices
– Apple Sign-In not supported on simulators or iOS versions below 13.
Incorrect Library Setup
– Misconfigured or incomplete integration of react-native-apple-authentication.
Missing or Incorrect Info.plist Keys
– Required keys like NSAppleIDUsageDescription not present.
Backend Token Verification Errors
– Identity token returned by Apple not properly verified by backend.
Apple Developer Console Misconfiguration
– Feature not properly enabled under App ID or missing provisioning profile update.
User Cancelled or Silent Errors
– No visible error, but sign-in was cancelled or failed without feedback.
Solutions for Fixing Apple Sign-In
Enable Sign-In with Apple in Xcode
Ensure the capability is added for all targets.
Verify Bundle ID & Service ID
Confirm that the app’s bundle ID matches exactly with the one registered on the Apple Developer portal.
Test on a Supported Real Device (iOS 13+)
Use physical devices running iOS 13 or above for reliable testing.
Recheck Integration of Apple Sign-In Library
Ensure correct installation, pod setup, and usage of the React Native Apple auth library.
Update Info.plist
Add NSAppleIDUsageDescription and any required URL schemes.
Check Developer Account Settings
Confirm "Sign In with Apple" is enabled in the App Identifier and re-download provisioning profiles if updated.
Backend Verification Review (if applicable)
Ensure backend properly validates Apple identity tokens, including signature and expiration.
Add Better Error Logging
Implement clear error messages or fallbacks to detect silent or user-cancelled flows.
📣 @AvtMob! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
github-actions commentedon Jun 20, 2025
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Jun 20, 2025
Triggered auto assignment to @puneetlath (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 20, 2025
Triggered auto assignment to @abekkala (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jun 20, 2025
💬 A slack conversation has been started in #expensify-open-source
6 remaining items
AvtMob commentedon Jun 20, 2025
Hi
Here are some possible Causes for Apple Sign-In Failure
Missing Capabilities
– Sign In with Apple not enabled in Xcode project settings.
Wrong Bundle ID or Service ID
– Mismatch between app’s bundle ID and what’s set up on Apple Developer portal.
Unsupported Devices
– Apple Sign-In not supported on simulators or iOS versions below 13.
Incorrect Library Setup
– Misconfigured or incomplete integration of react-native-apple-authentication.
Missing or Incorrect Info.plist Keys
– Required keys like NSAppleIDUsageDescription not present.
Backend Token Verification Errors
– Identity token returned by Apple not properly verified by backend.
Apple Developer Console Misconfiguration
– Feature not properly enabled under App ID or missing provisioning profile update.
User Cancelled or Silent Errors
– No visible error, but sign-in was cancelled or failed without feedback.
Solutions for Fixing Apple Sign-In
Enable Sign-In with Apple in Xcode
Ensure the capability is added for all targets.
Verify Bundle ID & Service ID
Confirm that the app’s bundle ID matches exactly with the one registered on the Apple Developer portal.
Test on a Supported Real Device (iOS 13+)
Use physical devices running iOS 13 or above for reliable testing.
Recheck Integration of Apple Sign-In Library
Ensure correct installation, pod setup, and usage of the React Native Apple auth library.
Update Info.plist
Add NSAppleIDUsageDescription and any required URL schemes.
Check Developer Account Settings
Confirm "Sign In with Apple" is enabled in the App Identifier and re-download provisioning profiles if updated.
Backend Verification Review (if applicable)
Ensure backend properly validates Apple identity tokens, including signature and expiration.
Add Better Error Logging
Implement clear error messages or fallbacks to detect silent or user-cancelled flows.
melvin-bot commentedon Jun 20, 2025
📣 @AvtMob! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
AvtMob commentedon Jun 20, 2025
Contributor details
Your Expensify account email: Avtar.hb13@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/avtar
melvin-bot commentedon Jun 20, 2025
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
mountiny commentedon Jun 20, 2025
Logs from the attempt https://www.expensify.com/_devportal/tools/logSearch/#query=request_id:(%229529f5aecd37f98e-LAX%22)+AND+timestamp:[2025-06-20T07:40:09.041Z+TO+2025-06-20T09:40:09.041Z]&index=logs_expensify-034265
401 Invalid ClientID
mountiny commentedon Jun 20, 2025
This will require Auth fix
mountiny commentedon Jun 20, 2025
clientID: com.expensify.expensifylite as we do not allow this clientID currently https://github.com/Expensify/Auth/blob/6c50f03ed1e47dc1d91c8cee5eed031751f2d0ea/auth/command/AuthenticateApple.cpp#L342-L347
mountiny commentedon Jun 20, 2025
PR raised
mountiny commentedon Jun 20, 2025
Fixed after the deploy!
puneetlath commentedon Jun 20, 2025
Thanks for handling!