“Account Locked”

What is the correct way to verify a developer account? Thank you all.

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).

same as me... I haven't been gotten any information or update on the payment or the account for 18 days now...

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

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

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

Everything remains the same: my account is still not activated and I have received no response.