“Account Locked”

Hello, In my iOS app, I have a customer center where the user can see some details about its current subscription. I display things like the billing period, the price, the introductory offer state, the renewal date if it's not cancelled or the expiration date if it's cancelled, etc. From this screen, the user can open the subscription management sheet. I want to detect if the user cancels the subscription from this sheet or from the App Store (when the app is running) so I can refresh the information displayed on my customer center. I checked the asynchronous sequences provided by StoreKit 2 like Transaction.updates or Product.SubscriptionInfo.Status.updates and tested with a Sandbox account on my physical device with the app debugged using Xcode. But I noticed these sequences don't emit when I cancel the subscription in Sandbox. Is this the expected behavior? Is there a way to observe in real time if a user cancels the subscription? I can still manually check when the sheet is dismissed but it's not

I’m attempting to use a Locked Camera Capture Extension (created from Xcode’s template / following Apple’s “Creating a camera experience for the Lock Screen” guidance). The extension builds, embeds, and installs on a physical device, but I cannot get it provisioned with the required entitlement com.apple.developer.locked-camera-capture. Environment Xcode: 26.0.1 (17A400) iOS: 26.2.1 (device) Apple Developer Program: paid Individual (Team ID: FT55UW9363) Key issue: provisioning profile for the ExtensionKit appex lacks the locked-camera entitlement The locked camera capture target is embedded as an ExtensionKit extension: .../DirectionalCamera.app/Extensions/LockedCapture.appex I decoded the embedded provisioning profile inside that .appex and printed its Entitlements dictionary: security cms -D -i .../DirectionalCamera.app/Extensions/LockedCapture.appex/embedded.mobileprovision > /tmp/locked_profile.plist /usr/libexec/PlistBuddy -c Print:Entitlements /tmp/locked_profile.p

Hi, Can someone advice me why my account has not been activated when payment was processed in my bank account for the $99 annual membership subscription, this is not the first apple has done this to me and getting annoyed of the non-service now.

I have an app that records video (and also provides a custom remote interface) so it needs to remain awake and in the foreground. It sets; UIApplication.shared.isIdleTimerDisabled = true I've also tried catching willEnterForegroundNotification to ensure it resets it if the app is backgrounded and resumes; .onReceive( NotificationCenter.default.publisher( for: UIApplication.willEnterForegroundNotification) ) { _ in UIApplication.shared.isIdleTimerDisabled = true } However, it seems that on some devices it will still go to sleep. This seems to be the case when Adaptive Power Mode is on (or rather, I've not managed to reproduce it when Adaptive Power Mode is off) even when battery percentage is well over 20% (I sort of expected Low Power Mode to trigger this) Am I missing something obvious? there must be a way to make sure media capture apps stay awake (I'm surprised AVFoundation doesn't do it anyway!) If it is related to Adaptive Power Mode, is there any way to detect that programatically to at least provide a

I enrolled in the Apple Developer Program more than 48 hours ago around 4 days ago. The payment was successfully charged to my card, and I received a subscription confirmation email. However, my developer account is still not activated, and I’m unable to access the full developer features. Has anyone experienced a similar delay? Is there anything specific I should do, or does activation take longer than expected , i tried to contact support twice throw mail but i got no response ! Any guidance would be appreciated. Thanks!

We are developing an iOS application that requires NFC-based communication using ISO 7816 / ISO 14443 standards for secure element interaction as part of a card provisioning workflow. We would like clarification on the following points: Is it possible to provision a payment card or securely add a card to an NFC-enabled device using direct ISO 7816 APDU communication via NFCTagReaderSession? If not, is Apple Pay In-App Provisioning (PassKit framework) the only supported approach for enabling contactless payment functionality on iPhone? What specific entitlements are required if the use case involves secure element communication for token provisioning (not bypassing Apple Pay)? We have already requested the relevant NFC entitlements through our Apple Developer account and are awaiting a response. Any guidance on the correct architecture and approval requirements would be greatly appreciated. Thank you in advance for your support.

App Store review has twice now rejected our app, but everything they claim is not true. We noticed your app shares a similar binary, metadata, and/or concept as apps submitted to the App Store by other developers, with only minor differences. Not true. There's one other app with similar functionality (which I learned about after opening our TestFlight), but the apps are different enough, and there's room in the world for two apps to tackle a similar user need. Submitting similar or repackaged apps is a form of spam that creates clutter and makes it difficult for users to discover new apps. Repackaged is certainly not true. Some factors that contribute to a spam rejection may include: Submitting an app with the same source code or assets as other apps already submitted to the App Store Creating and submitting multiple similar apps using a repackaged app template Purchasing an app template with problematic code from a third party Submitting several similar apps across multiple accounts None of these bu

Hi everyone, I’m hoping to sanity-check App Store review queue times and see if there’s anything I might be missing. I currently have two iOS apps sitting in “Waiting for Review” with no movement: App 1: Apple ID 6758135741 — submitted Feb 6, 2026 at 5:42 PM (11 days in “Waiting for Review”) App 2: Apple ID 6758885884 — submitted Feb 8, 2026 at 4:33 PM (9 days in “Waiting for Review”) In App Store Connect I don’t see any warnings, messages, or visible account issues. Builds uploaded successfully and metadata looks complete. A couple questions for anyone who’s seen this recently: Are 9–11 day “Waiting for Review” times currently normal due to queue volume? Are there common “silent blockers” that can keep an app in this state even without an obvious warning (e.g., Agreements/Tax/Banking, export compliance/encryption, missing compliance answers, etc.)? If this seems unusual, what’s the best next step—Support ticket, Resolution Center, or an expedite request? Thanks in advance for any insight. If helpful