Search results for

“Account Locked”

33,550 results found

Post

Replies

Boosts

Views

Activity

Reply to System-wide deadlock in removexattr from revisiond / APFS
All of the APFS locks tend to be held for very short periods of time, so it's not unusual for work to pile up very quickly. More to the point, all of those other threads are (mostly) irrelevant to the issue. I'd actually be looking for any other reference to compression/decompression or xattrs. If they are held for a very short amount of time, shouldn't we rarely see other threads waiting for it ? It's what I would expect, at least. And here we can see that all other threads are waiting for it for the whole spindump duration (Num samples: 940 (1-940) / IORWLockWrite & IORWLockRead → 940). I mean, I know this count the number of times the sampler see these symbols each time it samples the processes (i.e. it doesn't mean this code was running between each sample), but I would be surprised that these exact same stacks is re-happening exactly at the same time as the samples are done by chances: they are likely running for the whole time. Yes, you do. It's defined in IOLocks.h, which maps it to lck_rw
Topic: App & System Services SubTopic: Core OS Tags:
1w
Inquiry regarding Local Push Connectivity Entitlement
Dear Sir/Madam, Thank you for your support. I have reviewed the documentation for Local Push Connectivity (see URL below) and, following the instruction in the Important section to Request this entitlement from the Entitlement Request Page, I completed the application process for this Entitlement on March 11, 2026. [Local push connectivity] https://developer.apple.com/documentation/networkextension/local-push-connectivity?language=objc#Supporting-APNs-and-local-push-connectivity-in-one-app Subsequently, on March 13, 2026, I received the following reply from Apple: Sub : Re: Requesting Network Extension App Push Entitlement From: Local Push Review Sent: Friday, March 13, 2026 4:09 AM Hi, Thank you for your interest in the Local Push Connectivity entitlement. Your entitlement request has been approved for: Team ID: NWKYYYYYYY Technical documentation on this API is available here: -(Omission) - Best Regards, Apple Developer Relations My understanding is that upon approval of this application, an Entitlements fie
5
0
124
1w
App Store Connect API returning 403 from perfPowerMetrics using Admin / Dev role keys
I'm unexpectedly getting 403 status codes when calling the perfPowerMetrics APIs for any arbitrary app on my account. This worked last week, it is not working now. I have since revoked keys and recreated admin and developer keys--no luck, still getting 403. I've been working with the analytics APIs lately so I don't know exactly when the power and performance API stopped working. I've narrowed it down to something related to the token scope. When I have a scope on this endpoint of GET /v1/apps/1234567890/perfPowerMetrics it is rejected -- but the docs say I can create a token and reduce its scope like this. When I remove the scope and let the token be unbounded, the API call returns a valid response. FB22313063 - App Store Connect API: Fetching xcode metrics with an admin key generated token results in a 403 unexpectedly
1
0
78
1w
Product ID conflict for IAP across staging/production apps
I’m working on a Flutter application that implements subscriptions using in-app purchases (IAP). I currently have two apps under the same developer account: One for staging One for production In App A (staging), I successfully created a monthly subscription with the product ID: rc_1299_monthly However, when I try to create a subscription with the same product ID (rc_1299_monthly) in App B (production), I encounter the following error: The Product ID you entered is already being used by another subscription. My understanding was that product IDs are scoped per app, but this error suggests there may be account-level constraints. Has anyone encountered this before? Is it required to use unique product IDs across all apps under the same account, or is there a recommended approach for handling staging vs production setups? Any clarification or best practices would be appreciated.
1
0
90
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
I opened one last week. Case-ID: 18860388 I don't think that’s a valid bug number. Details on the bug filing process are here, and the numbers are prefixed FB. Again, please upload the full spintrace to that bug and then post the bug number back here. It definitely revised (well, APFS), that's holding the lock. Sure, but the question is why, not who. Causes this kind of hang are the interactions between multiple locks and multiple processes. It's hard to pick up unless you're looking at the full log and know what you're looking for, but the basic form is that there are two locks: The outer lock, which the blocking thread (in this case, thread 0xc0616d) is inside and holding. The inner lock, which the blocking thread (thread 0xc0616d) is stuck waiting on. You can actually see this dynamic in the traces you sent. This lock is an APFS-owned lock: *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Universal Links and Cloud-testing platforms
Thank you for the quick response and for the clarification on how iOS enforces AASA validation, that context is very helpful. To answer your question: our cloud-based device testing environment is a third-party device farm that runs automated UI tests against real iOS devices hosted in their infrastructure, BrowserStack. In order to install our app on their devices, their platform re-signs the app using their own provisioning profile, which is where the Associated Domains entitlement is lost. We fully understand that this is a security boundary by design, we are not looking to bypass AASA validation in production. Our concern is specifically scoped to pre-production testing: we need a way to validate our authentication flow end-to-end (including the Universal Link redirect back into the app) in an automated, cloud-hosted environment before shipping to production. Given your confirmation that there is no native provisioning flag to accommodate this, we have a follow-up question: Short of the Enterprise Develop
Topic: Code Signing SubTopic: Entitlements Tags:
1w
Reply to The iOS CallKit end my call without user action.
Thanks for your reply. But if the user taps any hardware to trigger an action, the app will receive it. How are you receiving these events from hardware or from the call screen UI? For example, if you're on the lock screen in a call and the user taps end call, how is your app receiving that event from the system? I ask, because the way I'd expect this to behave and the way our sample app behaves is that the system “directly” calls performEndCallAction: on your CXProviderDelegate, exactly what you seem to be describing. Then the app will create a CXAction to the CallKit, here the app will print the calling of this method: CXCallController.request(CXTransaction) is how your app asks CallKit to perform action on your app’s behavior. For example, Speakerbox uses it to implement its own interface for starting, ending, and muting calls. However, this is only used for implementing the in-app UI. The same actions in the call screen UI will be delivered directly through the provider delegate. __ Kevin Elliott
Topic: App & System Services SubTopic: General Tags:
1w
Reply to macOS 26.4 Dev Beta 2 Install Fails
I had the same issue on a M1-Max Studio (with installations of 26.4 beta 3, beta 4, and the RC). I finally solved it and reported the following as a appendix to FB22153797: SUCCESS!! First, what didn’t work — I booted in Safe Mode and tried to install Tahoe 26.4. This failed just as reported above. Then, I DEINSTALLED the F-Secure security suite (which came with my Spectrum Business ISP account). Then attempted the installation (in NORMAL mode, not Safe Mode). The installation worked. So it is clear that the install problem was related to something that F-Secure did to my system that was undone by de-installation.
Topic: Community SubTopic: Apple Developers Tags:
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
The IORWLockWrite stack seems to point machine_switch_context, i.e. when the lock is owned by another thread, and so the current thread is suspended / yielded to another one, waiting the lock to be reclaimable again. But then it's a bit incoherent with all the other threads pointing that blocked by krwlock for writing owned by revisiond [426] thread 0xc0616d (it can't be at the same time the owner, and not the owner…). Is it possible that machine_switch_context is called if you were able to get the ownership of the lock ? In which kind of scenario ? The stack doesn't seem to tell it. And we don't have the source code of IORWLockWrite. It's like something suspended the revisiond thread in the kernel when it executed IORWLockWrite, but then this something is unable to resume it because it is blocked itself (on this same lock ?). But then it doesn't align with this machine_switch_context symbol in the stack.
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Securing XPC Daemon Communication from Authorization Plugin
Thanks for the detailed information. I’ll take a look and follow up. _It’s hard to say what’s going on there without seeing the specific requirement you’re using_ Here are the specific requirement i'm using from the Authorization Plugin(xpc client) com.apple.SecurityAgentHelper.arm64, com.apple.loginwindow, com.apple.authorizationhost, com.apple.SecurityAgent, bash-3.2$ codesign --display -r - /System/Library/CoreServices/loginwindow.app Executable=/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow designated => identifier com.apple.loginwindow and anchor apple I attempted to apply a loose constraint (accepting any Apple-signed code), but it still fails. Please let me know if I’m approaching the loose constraint correctly. I was able to block other applications(created a custom app) trying to connect to my daemon. However, during the login and lock screen flows, it fails with error -67050 (errSecCSReqFailed). Is there a way to identify whether the client originates from Author
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
All of the APFS locks tend to be held for very short periods of time, so it's not unusual for work to pile up very quickly. More to the point, all of those other threads are (mostly) irrelevant to the issue. I'd actually be looking for any other reference to compression/decompression or xattrs. If they are held for a very short amount of time, shouldn't we rarely see other threads waiting for it ? It's what I would expect, at least. And here we can see that all other threads are waiting for it for the whole spindump duration (Num samples: 940 (1-940) / IORWLockWrite & IORWLockRead → 940). I mean, I know this count the number of times the sampler see these symbols each time it samples the processes (i.e. it doesn't mean this code was running between each sample), but I would be surprised that these exact same stacks is re-happening exactly at the same time as the samples are done by chances: they are likely running for the whole time. Yes, you do. It's defined in IOLocks.h, which maps it to lck_rw
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Inquiry regarding Local Push Connectivity Entitlement
Dear Sir/Madam, Thank you for your support. I have reviewed the documentation for Local Push Connectivity (see URL below) and, following the instruction in the Important section to Request this entitlement from the Entitlement Request Page, I completed the application process for this Entitlement on March 11, 2026. [Local push connectivity] https://developer.apple.com/documentation/networkextension/local-push-connectivity?language=objc#Supporting-APNs-and-local-push-connectivity-in-one-app Subsequently, on March 13, 2026, I received the following reply from Apple: Sub : Re: Requesting Network Extension App Push Entitlement From: Local Push Review Sent: Friday, March 13, 2026 4:09 AM Hi, Thank you for your interest in the Local Push Connectivity entitlement. Your entitlement request has been approved for: Team ID: NWKYYYYYYY Technical documentation on this API is available here: -(Omission) - Best Regards, Apple Developer Relations My understanding is that upon approval of this application, an Entitlements fie
Replies
5
Boosts
0
Views
124
Activity
1w
App Store Connect API returning 403 from perfPowerMetrics using Admin / Dev role keys
I'm unexpectedly getting 403 status codes when calling the perfPowerMetrics APIs for any arbitrary app on my account. This worked last week, it is not working now. I have since revoked keys and recreated admin and developer keys--no luck, still getting 403. I've been working with the analytics APIs lately so I don't know exactly when the power and performance API stopped working. I've narrowed it down to something related to the token scope. When I have a scope on this endpoint of GET /v1/apps/1234567890/perfPowerMetrics it is rejected -- but the docs say I can create a token and reduce its scope like this. When I remove the scope and let the token be unbounded, the API call returns a valid response. FB22313063 - App Store Connect API: Fetching xcode metrics with an admin key generated token results in a 403 unexpectedly
Replies
1
Boosts
0
Views
78
Activity
1w
Q How to verify a developer account
Welcome to the Developer Forums. I hope everyone is well. I have some questions and need support, so I hope the moderators, if they find that the place where I created this post is not appropriate, will direct me to the correct place. How to
Replies
1
Boosts
0
Views
62
Activity
1w
Reply to Q How to verify a developer account
What is the correct way to verify a developer account? Thank you all.
Replies
Boosts
Views
Activity
1w
Product ID conflict for IAP across staging/production apps
I’m working on a Flutter application that implements subscriptions using in-app purchases (IAP). I currently have two apps under the same developer account: One for staging One for production In App A (staging), I successfully created a monthly subscription with the product ID: rc_1299_monthly However, when I try to create a subscription with the same product ID (rc_1299_monthly) in App B (production), I encounter the following error: The Product ID you entered is already being used by another subscription. My understanding was that product IDs are scoped per app, but this error suggests there may be account-level constraints. Has anyone encountered this before? Is it required to use unique product IDs across all apps under the same account, or is there a recommended approach for handling staging vs production setups? Any clarification or best practices would be appreciated.
Replies
1
Boosts
0
Views
90
Activity
1w
Reply to Product ID conflict for IAP across staging/production apps
Hello, the Product ID should be unique at the developer account level. For your use case, use a different Product ID when creating products for the “App B (production)” app if you have already used them in App A (staging).
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
1w
Reply to Payment processed 18 days ago, but Developer Program still not activated
same as me... I haven't been gotten any information or update on the payment or the account for 18 days now...
Replies
Boosts
Views
Activity
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
I opened one last week. Case-ID: 18860388 I don't think that’s a valid bug number. Details on the bug filing process are here, and the numbers are prefixed FB. Again, please upload the full spintrace to that bug and then post the bug number back here. It definitely revised (well, APFS), that's holding the lock. Sure, but the question is why, not who. Causes this kind of hang are the interactions between multiple locks and multiple processes. It's hard to pick up unless you're looking at the full log and know what you're looking for, but the basic form is that there are two locks: The outer lock, which the blocking thread (in this case, thread 0xc0616d) is inside and holding. The inner lock, which the blocking thread (thread 0xc0616d) is stuck waiting on. You can actually see this dynamic in the traces you sent. This lock is an APFS-owned lock: *940 apfs_vnop_getattr + 312 (apfs + 604336) [0xfffffe000beacff0] *940 IORWLockRead + 144 (kernel.release
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Universal Links and Cloud-testing platforms
Thank you for the quick response and for the clarification on how iOS enforces AASA validation, that context is very helpful. To answer your question: our cloud-based device testing environment is a third-party device farm that runs automated UI tests against real iOS devices hosted in their infrastructure, BrowserStack. In order to install our app on their devices, their platform re-signs the app using their own provisioning profile, which is where the Associated Domains entitlement is lost. We fully understand that this is a security boundary by design, we are not looking to bypass AASA validation in production. Our concern is specifically scoped to pre-production testing: we need a way to validate our authentication flow end-to-end (including the Universal Link redirect back into the app) in an automated, cloud-hosted environment before shipping to production. Given your confirmation that there is no native provisioning flag to accommodate this, we have a follow-up question: Short of the Enterprise Develop
Topic: Code Signing SubTopic: Entitlements Tags:
Replies
Boosts
Views
Activity
1w
Reply to The iOS CallKit end my call without user action.
Thanks for your reply. But if the user taps any hardware to trigger an action, the app will receive it. How are you receiving these events from hardware or from the call screen UI? For example, if you're on the lock screen in a call and the user taps end call, how is your app receiving that event from the system? I ask, because the way I'd expect this to behave and the way our sample app behaves is that the system “directly” calls performEndCallAction: on your CXProviderDelegate, exactly what you seem to be describing. Then the app will create a CXAction to the CallKit, here the app will print the calling of this method: CXCallController.request(CXTransaction) is how your app asks CallKit to perform action on your app’s behavior. For example, Speakerbox uses it to implement its own interface for starting, ending, and muting calls. However, this is only used for implementing the in-app UI. The same actions in the call screen UI will be delivered directly through the provider delegate. __ Kevin Elliott
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1w
Reply to Payment processed 18 days ago, but Developer Program still not activated
Everything remains the same: my account is still not activated and I have received no response.
Replies
Boosts
Views
Activity
1w
Reply to macOS 26.4 Dev Beta 2 Install Fails
I had the same issue on a M1-Max Studio (with installations of 26.4 beta 3, beta 4, and the RC). I finally solved it and reported the following as a appendix to FB22153797: SUCCESS!! First, what didn’t work — I booted in Safe Mode and tried to install Tahoe 26.4. This failed just as reported above. Then, I DEINSTALLED the F-Secure security suite (which came with my Spectrum Business ISP account). Then attempted the installation (in NORMAL mode, not Safe Mode). The installation worked. So it is clear that the install problem was related to something that F-Secure did to my system that was undone by de-installation.
Topic: Community SubTopic: Apple Developers Tags:
Replies
Boosts
Views
Activity
1w
Reply to System-wide deadlock in removexattr from revisiond / APFS
The IORWLockWrite stack seems to point machine_switch_context, i.e. when the lock is owned by another thread, and so the current thread is suspended / yielded to another one, waiting the lock to be reclaimable again. But then it's a bit incoherent with all the other threads pointing that blocked by krwlock for writing owned by revisiond [426] thread 0xc0616d (it can't be at the same time the owner, and not the owner…). Is it possible that machine_switch_context is called if you were able to get the ownership of the lock ? In which kind of scenario ? The stack doesn't seem to tell it. And we don't have the source code of IORWLockWrite. It's like something suspended the revisiond thread in the kernel when it executed IORWLockWrite, but then this something is unable to resume it because it is blocked itself (on this same lock ?). But then it doesn't align with this machine_switch_context symbol in the stack.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Securing XPC Daemon Communication from Authorization Plugin
Thanks for the detailed information. I’ll take a look and follow up. _It’s hard to say what’s going on there without seeing the specific requirement you’re using_ Here are the specific requirement i'm using from the Authorization Plugin(xpc client) com.apple.SecurityAgentHelper.arm64, com.apple.loginwindow, com.apple.authorizationhost, com.apple.SecurityAgent, bash-3.2$ codesign --display -r - /System/Library/CoreServices/loginwindow.app Executable=/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow designated => identifier com.apple.loginwindow and anchor apple I attempted to apply a loose constraint (accepting any Apple-signed code), but it still fails. Please let me know if I’m approaching the loose constraint correctly. I was able to block other applications(created a custom app) trying to connect to my daemon. However, during the login and lock screen flows, it fails with error -67050 (errSecCSReqFailed). Is there a way to identify whether the client originates from Author
Replies
Boosts
Views
Activity
1w