Search results for

“Account Locked”

33,571 results found

Post

Replies

Boosts

Views

Activity

Problem testing SignificantAppUpdateTopic with AskCenter
Hi, I have a problem testing sending a significantAppUpdateTopic request with AskCenter. Sending a request of type CommunicationTopic works correctly: let question = PermissionQuestion( handle: .init(value: description, kind: .custom) ) try await AskCenter.shared.ask(question, in: viewController) Receiving the response from the guardian also works correctly for a question of type CommunicationTopic. However, after changing the request from CommunicationTopic to significantAppUpdateTopic, I get the following cryptic error: Error returned from daemon: Error Domain=com.apple.accounts Code=7 (null) (and nothing happens). This is the code I am using: let topic = SignificantAppUpdateTopic(description: description) let question = PermissionQuestion(significantAppUpdateTopic: topic) try await AskCenter.shared.ask(question, in: viewController) These are my settings: I created a child account within a family group the child's age in the family group is set to 15 I am the group organizer I am not located in Tex
1
0
130
3w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Co
4
0
254
3w
Apple School Manager API - invalid_client error with correct JWT
Hello Apple Developer Community, I'm experiencing an invalid_client error (HTTP 400) when attempting to authenticate with the Apple School Manager API using OAuth2 with JWT bearer assertion (RFC 7523). Despite verifying all configuration values and following Apple's documentation, I continue to receive this error. Error Details Error: invalid_client HTTP Status: 400 Bad Request Endpoint: https://appleid.apple.com/auth/oauth2/v2/token Response: {error: invalid_client} My Configuration All values have been verified to match Apple School Manager exactly: Organization ID: 55155430 Key ID: 8136a1f6-c995-4010-b964-bc8278c107ef Client ID (Service ID): SCHOOLAPI.7c0c10a0-4d8a-4ef8-a2be-eda040b65c59 Private Key: Loads correctly, signs JWT properly (ES256) JWT Configuration I'm generating a JWT with the following structure: Header: { alg: ES256, kid: 8136a1f6-c995-4010-b964-bc8278c107ef, typ: JWT } Payload: { iss: 55155430, sub: SCHOOLAPI.7c0c10a0-4d8a-4ef8-a2be-eda040b65c59, aud: https://appleid.apple.com, iat: [times
0
0
723
3w
Xcode 26.3 Claude Agent — 401 Invalid Bearer Token on Intel Mac (FB22141224)
I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with Failed to authenticate. API Error: 401 - Invalid bearer token on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported upstream as a 401 authenticat
4
0
274
3w
Reply to App stuck in "Waiting for Review" for 17+ days despite 5 Support Cases
Update (Day 5): Still no response from Apple Staff. This is now affecting 5 apps on my account, all stuck since early February. Developer Support cases (102842489731) provide no answers. This appears to be a system-level issue where binaries are ghosted in the review queue. Can someone from Apple please acknowledge this? We are considering resubmitting all apps, but this wastes significant engineering resources.
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
Thank you for your response. I understand the following point: To summarize this interpretation: Existence of a 410 status merely indicates that the token is no longer valid and should not be used anymore. However, in some cases it is difficult to associate a device token with a user account because the app does not provide a login feature or user accounts. In our case, the following scenario can occur: The user installs the app on a device (IDFV: A, DeviceToken: a) The user uninstalls the app The user reinstalls the app on the same device (IDFV: B, DeviceToken: b) Push notifications are sent using both DeviceToken: a and DeviceToken: b As a result, two push notifications are delivered to the same device If we cannot associate the device token with a user account, what would be the recommended way to prevent duplicate push notifications being delivered to the same device in this situation? I would appreciate your guidance.
3w
Reply to Sandbox subscription test is triggering multiple transaction events for a single purchase attempt
Thank you for your reply, and I apologize for not providing enough detail earlier. Our app is built with React Native, and we implemented in-app purchases using an OpenIAP-related library that supports StoreKit 2. We are currently testing with a Sandbox account. The feature itself is not completely broken, but we are seeing several abnormal behaviors during testing. For example, even when a purchase is attempted only once, we sometimes receive the purchase-completed message two or three times. We have also observed other inconsistent behaviors during Sandbox testing. Because of this, we were wondering whether this might be related to instability or known issues in the Sandbox environment, rather than being entirely caused by our implementation. Has anyone experienced similar issues when testing subscriptions with StoreKit 2 in a React Native environment? If there are any known Sandbox limitations or specific points we should check first, I would greatly appreciate your advice.
3w
App in "Waiting for Review" for 32 days — two escalations with no resolution
Hello everyone, I'm reaching out to see if anyone has experienced a similar situation or has any advice. My app Currot has been in Waiting for Review across multiple submissions since February 8, 2026. Despite following all recommended steps, the review team has not responded. Timeline: Feb 8: Initial submission Feb 11 (04:50 AM): Moved to In Review Feb 11 (05:17 AM): Rejected (Guidelines 2.3.6, 5.1.1, 1.2, 5.1.1v) Feb 11 (08:10 PM): All four issues resolved, resubmitted same day with detailed screenshots in Resolution Center Feb 14: Follow-up message sent via Resolution Center — no response Feb 23: After 12 days of no movement, canceled and resubmitted with review notes explaining all resolved issues Mar 4: Developer Support (Case 102831733019) confirmed they notified the review team Mar 9: Follow-up email and phone call requesting escalation Mar 10: Developer Support confirmed they escalated again Mar 12 (today): Still Waiting for Review — 32 days since initial submission, 17 days since latest submission Ac
5
0
206
3w
Reply to Unable to Locate Pending Terms & Conditions in App Store Connect
Same, not sure if it's something on AppFigures side or on the Apple side. But something I noticed was that if I go to /agreements, there's a redirect back to /business. But for a split second, I saw that something was wrong with my bank account setup for paid apps. Though on the /business site, everything looks fine. Tried to get more time with simulating throttling via Chrome, but didn't gather any more information.
3w
Reply to Apple Pay Sandbox: onpaymentauthorized not fired after successful authentication (started March 6)
Hi @shirakura, Thanks for reporting the unexpected behavior you've observed in the Sandbox environment. For Apple Pay merchants using the Sandbox payment gateway, the user and device must now be a sandbox tester account. Previously, both production and sandbox tester accounts were supported. Could you please confirm you've configured the device to test against the Apple Pay & Wallet Sandbox? To confirm this, your device should be logged in with a sandbox tester account: Sandbox Testing https://developer.apple.com/apple-pay/sandbox-testing/ If your device is using a sandbox test account for Apple Pay and Wallet, the Apple Pay Server engineering team would need to investigate this issue directly via Feedback Assistant. To submit a bug report, please follow the steps outlined in the post below: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 Once submitted, please reply here with your
3w
Reply to Questions on Promo/Offer Code Validation and Functionality for In-App Purchases
Hello, You can find most of the answers and details to your points by going through the Supporting offer codes in your app article, but let me give you a summary to your specific questions: You can test offer codes in the sandbox environment for all In-App Purchase product types: consumable, non-consumable, non-renewing subscription, and auto-renewable subscription. To redeem an offer code in the sandbox environment, follow these steps: On your device, sign in using a Sandbox Apple Account. On the Sandbox Account Settings page, tap Initiate Transaction. Select Offer Codes and redeem a sandbox offer code you created in App Store Connect. You can use the information contained in the transaction to identify products purchased with offer codes, you need to check the offer property of Transaction on StoreKit, or the offerIdentifier if you're using the App Store Server API or notifications. If you're not using it yet, we highly recommend using the App Store Server libraries to adopt the App Store
Topic: App & System Services SubTopic: StoreKit Tags:
3w
Reply to Is my account active?
Thanks for your post and congratulations on having that game almost completed. About your Apple Developer Account, have you login into the account and do you see the submit button for apps? The Developer Account team does not monitor the forums very often, if you have questions about your account, I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue. Albert Pascual
  Worldwide Developer Relations.
3w
Problem testing SignificantAppUpdateTopic with AskCenter
Hi, I have a problem testing sending a significantAppUpdateTopic request with AskCenter. Sending a request of type CommunicationTopic works correctly: let question = PermissionQuestion( handle: .init(value: description, kind: .custom) ) try await AskCenter.shared.ask(question, in: viewController) Receiving the response from the guardian also works correctly for a question of type CommunicationTopic. However, after changing the request from CommunicationTopic to significantAppUpdateTopic, I get the following cryptic error: Error returned from daemon: Error Domain=com.apple.accounts Code=7 (null) (and nothing happens). This is the code I am using: let topic = SignificantAppUpdateTopic(description: description) let question = PermissionQuestion(significantAppUpdateTopic: topic) try await AskCenter.shared.ask(question, in: viewController) These are my settings: I created a child account within a family group the child's age in the family group is set to 15 I am the group organizer I am not located in Tex
Replies
1
Boosts
0
Views
130
Activity
3w
Xcode Source Control pull/push hangs indefinitely, terminal Git works normally After Tahoe 26.3 (25D125) Update
Device Details: MBP M2 Pro AND MBP M3 Pro macOS 26.3 (25D125) Xcode Version 26.3, 26.2, 26.1 (I reinstalled all 3 of these after the macOS update) BUG: Xcode hangs indefinitely when performing Source Control operations (Pull or Push) on a Git repository that uses SSH authentication. The same repository works correctly when performing the equivalent Git operations from the Terminal using the Git CLI. The issue appears to be specific to Xcode’s internal Source Control integration. When the operation is triggered from Xcode, the UI shows a spinning progress indicator and never completes. Terminal Git commands (git fetch, git pull, git push) complete normally using the same SSH key and repository. A hang sample taken during the issue shows the Xcode main thread blocked in Source Control authentication and fingerprint handling code paths, including: IDESourceControlUIHandler IDESourceControlFingerprintManager handleAuthenticationFailure showFingerprintAlertOnWindow This suggests Xcode may be waiting on a Source Co
Replies
4
Boosts
0
Views
254
Activity
3w
Apple School Manager API - invalid_client error with correct JWT
Hello Apple Developer Community, I'm experiencing an invalid_client error (HTTP 400) when attempting to authenticate with the Apple School Manager API using OAuth2 with JWT bearer assertion (RFC 7523). Despite verifying all configuration values and following Apple's documentation, I continue to receive this error. Error Details Error: invalid_client HTTP Status: 400 Bad Request Endpoint: https://appleid.apple.com/auth/oauth2/v2/token Response: {error: invalid_client} My Configuration All values have been verified to match Apple School Manager exactly: Organization ID: 55155430 Key ID: 8136a1f6-c995-4010-b964-bc8278c107ef Client ID (Service ID): SCHOOLAPI.7c0c10a0-4d8a-4ef8-a2be-eda040b65c59 Private Key: Loads correctly, signs JWT properly (ES256) JWT Configuration I'm generating a JWT with the following structure: Header: { alg: ES256, kid: 8136a1f6-c995-4010-b964-bc8278c107ef, typ: JWT } Payload: { iss: 55155430, sub: SCHOOLAPI.7c0c10a0-4d8a-4ef8-a2be-eda040b65c59, aud: https://appleid.apple.com, iat: [times
Replies
0
Boosts
0
Views
723
Activity
3w
Xcode 26.3 Claude Agent — 401 Invalid Bearer Token on Intel Mac (FB22141224)
I've been investigating a persistent 401 Invalid Bearer Token error with Claude Agent in Xcode 26.3 on an Intel Core i9 Mac and wanted to share my findings here in case others are affected. ENVIRONMENT Hardware: Intel Core i9 (x86_64) Xcode: 26.3 (17C529) macOS: 26.3 (25D125) THE ISSUE Claude Agent fails with Failed to authenticate. API Error: 401 - Invalid bearer token on every prompt, despite the account showing as Signed In under Settings → Intelligence. The error persists after signing out and back in, and the token is confirmed valid and unexpired in Keychain. WHAT WORKS Claude Code in Terminal works perfectly on the same machine with the same credentials The basic Claude Sonnet 4.5 coding assistant in Xcode works fine Only Claude Agent is affected ROOT CAUSE HYPOTHESIS Xcode appears to be installing an ARM64 Claude binary on Intel Macs silently, with no warning or fallback. This binary likely fails to execute on x86_64 hardware and that failure is being misreported upstream as a 401 authenticat
Replies
4
Boosts
0
Views
274
Activity
3w
Reply to App stuck in "Waiting for Review" for 17+ days despite 5 Support Cases
Update (Day 5): Still no response from Apple Staff. This is now affecting 5 apps on my account, all stuck since early February. Developer Support cases (102842489731) provide no answers. This appears to be a system-level issue where binaries are ghosted in the review queue. Can someone from Apple please acknowledge this? We are considering resubmitting all apps, but this wastes significant engineering resources.
Replies
Boosts
Views
Activity
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
I'm not sure associating the push device token to a user account would even solve the problem, unless you only allow one token per user account. But that would prevent users from using multiple devices (such as their iPhone and iPad) with the same account. Our app requires the users to login and we do associate the push device tokens to the respective user account, but we allow multiple tokens per account. And we have noticed for a while that these tokens stack up, even if users only use one device. I don't think we had a case of the same push notification being sent multiple times to the same device yet though. (Haven't tested with iOS 26.4 Beta).
Replies
Boosts
Views
Activity
3w
Pending account help please
Hello, my account is pending .i try to contact apple several times with no respond the customer service is terrible.
Replies
0
Boosts
0
Views
28
Activity
3w
Reply to Device Token Not Invalidated After App Uninstall (iOS 26.4 Beta)
Thank you for your response. I understand the following point: To summarize this interpretation: Existence of a 410 status merely indicates that the token is no longer valid and should not be used anymore. However, in some cases it is difficult to associate a device token with a user account because the app does not provide a login feature or user accounts. In our case, the following scenario can occur: The user installs the app on a device (IDFV: A, DeviceToken: a) The user uninstalls the app The user reinstalls the app on the same device (IDFV: B, DeviceToken: b) Push notifications are sent using both DeviceToken: a and DeviceToken: b As a result, two push notifications are delivered to the same device If we cannot associate the device token with a user account, what would be the recommended way to prevent duplicate push notifications being delivered to the same device in this situation? I would appreciate your guidance.
Replies
Boosts
Views
Activity
3w
Reply to Sandbox subscription test is triggering multiple transaction events for a single purchase attempt
Thank you for your reply, and I apologize for not providing enough detail earlier. Our app is built with React Native, and we implemented in-app purchases using an OpenIAP-related library that supports StoreKit 2. We are currently testing with a Sandbox account. The feature itself is not completely broken, but we are seeing several abnormal behaviors during testing. For example, even when a purchase is attempted only once, we sometimes receive the purchase-completed message two or three times. We have also observed other inconsistent behaviors during Sandbox testing. Because of this, we were wondering whether this might be related to instability or known issues in the Sandbox environment, rather than being entirely caused by our implementation. Has anyone experienced similar issues when testing subscriptions with StoreKit 2 in a React Native environment? If there are any known Sandbox limitations or specific points we should check first, I would greatly appreciate your advice.
Replies
Boosts
Views
Activity
3w
App in "Waiting for Review" for 32 days — two escalations with no resolution
Hello everyone, I'm reaching out to see if anyone has experienced a similar situation or has any advice. My app Currot has been in Waiting for Review across multiple submissions since February 8, 2026. Despite following all recommended steps, the review team has not responded. Timeline: Feb 8: Initial submission Feb 11 (04:50 AM): Moved to In Review Feb 11 (05:17 AM): Rejected (Guidelines 2.3.6, 5.1.1, 1.2, 5.1.1v) Feb 11 (08:10 PM): All four issues resolved, resubmitted same day with detailed screenshots in Resolution Center Feb 14: Follow-up message sent via Resolution Center — no response Feb 23: After 12 days of no movement, canceled and resubmitted with review notes explaining all resolved issues Mar 4: Developer Support (Case 102831733019) confirmed they notified the review team Mar 9: Follow-up email and phone call requesting escalation Mar 10: Developer Support confirmed they escalated again Mar 12 (today): Still Waiting for Review — 32 days since initial submission, 17 days since latest submission Ac
Replies
5
Boosts
0
Views
206
Activity
3w
Reply to Unable to Locate Pending Terms & Conditions in App Store Connect
Same, not sure if it's something on AppFigures side or on the Apple side. But something I noticed was that if I go to /agreements, there's a redirect back to /business. But for a split second, I saw that something was wrong with my bank account setup for paid apps. Though on the /business site, everything looks fine. Tried to get more time with simulating throttling via Chrome, but didn't gather any more information.
Replies
Boosts
Views
Activity
3w
Reply to Apple Pay Sandbox: onpaymentauthorized not fired after successful authentication (started March 6)
Hi @shirakura, Thanks for reporting the unexpected behavior you've observed in the Sandbox environment. For Apple Pay merchants using the Sandbox payment gateway, the user and device must now be a sandbox tester account. Previously, both production and sandbox tester accounts were supported. Could you please confirm you've configured the device to test against the Apple Pay & Wallet Sandbox? To confirm this, your device should be logged in with a sandbox tester account: Sandbox Testing https://developer.apple.com/apple-pay/sandbox-testing/ If your device is using a sandbox test account for Apple Pay and Wallet, the Apple Pay Server engineering team would need to investigate this issue directly via Feedback Assistant. To submit a bug report, please follow the steps outlined in the post below: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 Once submitted, please reply here with your
Replies
Boosts
Views
Activity
3w
Reply to App distributed but IAP - is waiting for review.
@Dimbonder was your problem resolved? I am in the same situation - app approved, non-consumable IAP 'in review'. My app will lock up and show a paywall in 14 days, so it doesn't make much sense to announce my app without IAP approval.
Replies
Boosts
Views
Activity
3w
Reply to Questions on Promo/Offer Code Validation and Functionality for In-App Purchases
Hello, You can find most of the answers and details to your points by going through the Supporting offer codes in your app article, but let me give you a summary to your specific questions: You can test offer codes in the sandbox environment for all In-App Purchase product types: consumable, non-consumable, non-renewing subscription, and auto-renewable subscription. To redeem an offer code in the sandbox environment, follow these steps: On your device, sign in using a Sandbox Apple Account. On the Sandbox Account Settings page, tap Initiate Transaction. Select Offer Codes and redeem a sandbox offer code you created in App Store Connect. You can use the information contained in the transaction to identify products purchased with offer codes, you need to check the offer property of Transaction on StoreKit, or the offerIdentifier if you're using the App Store Server API or notifications. If you're not using it yet, we highly recommend using the App Store Server libraries to adopt the App Store
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
3w
Reply to Is my account active?
Thanks for your post and congratulations on having that game almost completed. About your Apple Developer Account, have you login into the account and do you see the submit button for apps? The Developer Account team does not monitor the forums very often, if you have questions about your account, I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue. Albert Pascual
  Worldwide Developer Relations.
Replies
Boosts
Views
Activity
3w