Pulse of Chennai

Hello, Thank you for the report, and for identifying the device and OS — it let us pinpoint the cause quickly. You were right: Sign in with Apple was broken in build 22, and the error you saw was genuine. Cause In the previous update we moved Sign in with Apple from a web-based authorization flow to the native flow using ASAuthorizationAppleIDProvider. The Sign in with Apple capability was not added to the app target alongside that change, so the binary shipped without the com.apple.developer.applesignin entitlement. Without it, the very first authorization request fails immediately with ASAuthorizationError code 1000, and the app surfaces that as the error message you encountered. This affects every device, which is why it reproduced consistently on iPad. Resolution — included in build 1.0.6 (23) 1. Added the Sign in with Apple capability to the app target. We verified the entitlement is present in the code-signed binary, not only in the project settings. 2. Registered the app's bundle identifier (com.pulseofchennai.app) with our authentication backend, so the identity token returned by the native Sign in with Apple flow is accepted. Previously only the web Services ID was registered, which would have caused a second failure once the entitlement issue was resolved. We have confirmed on iPad running iPadOS 27 that tapping Sign in with Apple now presents the system Sign in with Apple sheet and completes successfully, returning the user to the signed-in app. Demo account The credentials in App Review Information remain active. Enter the demo email on the login screen and then the App Review PIN — no email inbox, OTP or password is required, and no verification email is sent. Alternative sign-in methods Sign in with Google and email sign-in are both fully functional and available on the same screen if you would like to verify the rest of the app independently. Thank you for your patience across these reviews.