Overview

Hi all, I've been attempting to implement the Texas age range restrictions for an app I work on. I've banged my head against it for the last week and have a flow that is 99% working. I have all of the cases working exceptt when a significant change is approved. The issue I'm running into, is that let responsesSequence = AskCenter.shared.responses(for: SignificantAppUpdateTopic.self) is not receiving a response the first time it's called. It's only after the second time it's called that a response is registered and then I allow a user to access my app. When I set significant app change declined, then responses(for: ) returns on the first call to it. I can't for the life of my figure out why one works and the other doesn't. Has anyone else encountered this or have suggestions for me? I'm happy to post more code here in order to come to a resolution on this issue.

I installed xcode 16 and both Predictive Code Completion Model and iOS 18.0 Simulator Failed Download. I can live without the code completion, but I can not get any Simulator to install. I clicked of the info button and it shows the following: Download failed. Domain: DVTDownloadableErrorDomain Code: 41 User Info: { DVTErrorCreationDateKey = "2024-09-30 15:57:24 +0000"; } Download failed. Domain: DVTDownloadableErrorDomain Code: 41 Failed fetching catalog for assetType (com.apple.MobileAsset.iOSSimulatorRuntime), serverParameters ({ RequestedBuild = 22A3351; }) Domain: DVTDownloadsUtilitiesErrorDomain Code: -1 Download failed as the server said authentication failed. (Catalog download for com.apple.MobileAsset.iOSSimulatorRuntime) Domain: com.apple.MobileAssetError.Download Code: 41 User Info: { checkServer = 1; } System Information macOS Version 15.0 (Build 24A335) Xcode 16.0 (23051) (Build 16A242d) Timestamp: 2024-09-30T10:57:24-05:00

No eligible devices connected to 'My Mac

I've been wating for 5 business days now and one weekend to get my Apple Developer ID approved. This does delay the publishing of applications. Could a possible solution be delegating the work to other groups? Could the employees in physical stores be included in this work, if the staff allocated to this in head office are not sufficient?

Hello 👋 I ran into a SwiftUI lifecycle gotcha while debugging a List with .refreshable I share the code used to reproduce the issue @Observable final class CounterModel: Identifiable { let id: String var title: String var value: Int init(id: String, title: String, value: Int = 0) { self.id = id self.title = title self.value = value } deinit { print("deinit", title) } } @Observable final class ObservableCountersStore { var counters: [CounterModel] = [ .init(id: "1", title: "A"), .init(id: "2", title: "B"), .init(id: "3", title: "C") ] func refresh() async { try? await Task.sleep(nanoseconds: 300_000_000) counters = [.init(id: "4", title: "D")] } } struct ObservableCountersListView: View { @State private var store = ObservableCountersStore() var body: some View { List { ForEach(store.counters) { counter in ObservableCounterRow(counter: counter) } } .refreshable { await store.refresh() } } } struct ObservableCounterRow: View { let counter: CounterModel var body: some View { Text(counter.title) } } Observation: After calling refresh(), only some of the previous CounterModel only one CounterModel is deallocated immediately. Others are retained This doesn’t look like a leak, but it made me realize that passing observable reference types directly into List rows leads to non-deterministic object lifetimes, especially with .refreshable. Posting this as a gotcha — curious if this matches intended behavior or if others have run into the same thing.

Updated version of this post My HomePod mini is now on version 16.4, so the the temperature and humidity sensors are enabled. The data properly shows up in the Home app on my various devices. In my HomeKit iPad app running on Mac Catalyst, however, the data does not show up. I would expect the HomePod mini to show up in HMHome.accessories with a service of type HMServiceTypeTempatureSensor. I see all of my other HomeKit accessories, just not the HomePod mini. I have tried with the latest Xcode (14.3) and highest available iOS Target and Minimum Deployment (16.4), macOS version 13.3. I have not, as of this writing, upgraded my HomeKit architecture, however. Note that I haven't tried the app on an actual iPad (and the iOS simulator doesn't expose my HomeKit environment.)

Is this even possible? Instead of any pairing dialog appearing, my central code get the "Authentication is insufficient" error when reading the characteristic. My peripheral (in the macOS app) code uses the .notifyEncryptionRequired property and uses .readEncryptionRequired and .writeEncryptionRequired permissions. No descriptors are set, but I think they get added automatically since this characteristic notifies. 2900 and 2902 descriptors are set by the peripheral/CoreBluetooth. If the Mac and iPhone are using the same Apple ID does that affect pairing?

Hello everyone, We are the developer of PhotoMagic – AI Photo Editor, and we would appreciate guidance from the community regarding a pending enforcement case currently under review by the App Review Board. Case Information Case Number: 102812414888 App ID: 6746860005 Notice Date: January 25, 2026 Current Status: Pending review by the App Review Board Reason cited: Section 3.2(f) of the Apple Developer Program License Agreement The notice stated that our app submissions were considered to have “repeatedly violated the App Review Guidelines in an attempt to evade the review process.” Background & Acknowledgement Upon receiving the notice, we immediately conducted a comprehensive internal audit. During this process, we identified that certain user-uploaded template content (for example, templates involving concepts such as “kiss” or “hug”) posed potential policy risks. We would like to clearly state that we did not intentionally hide or disguise content to evade App Review. However, we fully acknowledge that our previous content moderation mechanisms were insufficient, and we take full responsibility for this oversight. Corrective Actions Taken Following the audit, we implemented the following remediation measures. Some items are already live, while others will take effect in the next app update once submission restrictions are lifted. Already Implemented 1.Expanded and strengthened our prohibited keyword library to prevent searching or generating sensitive content (e.g. “kiss”, “hug”, “nude”, etc.).(We can provide the keyword list if requested.) 2.Added detection and filtering mechanisms for public figures (including political figures and well-known individuals) to prevent potential deepfake misuse. 3.Raised AI model safety thresholds to prioritize risk prevention, even if this blocks borderline or otherwise normal content. 4.Fully restructured our content moderation team to ensure independence, accountability, and redundancy. 5.Implemented an in-app reporting mechanism allowing users to report any content, which is immediately reviewed and removed if found non-compliant. 6.Discontinued use of Grok and any other AI services deemed potentially risky; all AI generation capabilities have been migrated to Gemini. Pending Next App Update 7. Updated Terms of Use to restrict access to adults only and explicitly prohibit generating any prohibited content. Repeated violation attempts result in warnings and eventual denial of service. 8. Removed all user-uploaded custom templates. Only internally designed, fixed templates are provided, with no user-editable prompts. 9. Added both visible and invisible watermarks to all generated content to ensure clear AI attribution and traceability. Questions for the Community We would appreciate any guidance or shared experience regarding the following: Are there any additional steps that are appropriate or recommended to bring remediation details to the App Review Board’s attention while a case is under review? Is there any specific type of supporting documentation (e.g. technical architecture explanations, data cleanup confirmations, policy mappings) that has been helpful in similar situations? In general, once a case is under review by the App Review Board, is it best to wait for further instructions, or are proactive clarifications sometimes appropriate? We respect Apple’s review process and are fully committed to long-term compliance with the App Store Review Guidelines and the Apple Developer Program License Agreement. Any insight would be greatly appreciated. Thank you for your time and support.

My app has been waiting to be reviewed since Nov 21st 2025 and its now Feb 5th 2026! I have contacted developer support twice and they said that there is nothing to worry about??? What is going on at Apple???

Hello, My app (App ID: 1616628950) was recently reviewed, and I received an email stating that the submission review was completed and that the build is eligible for distribution. In App Store Connect, In App review - IOS submission, the build shows Approved. However, when returning to the main Distribution page, the app version is still displayed as In Review, and I do not yet see a “Ready for Distribution” or release option. In previous submissions, once review was completed, the status usually transitioned to “Ready for Distribution” or “Pending Developer Release” fairly quickly, so this behavior seems unusual. I have tried refreshing the page and logging out/in, but the status has not changed so far. I just wanted to ask if this is a known synchronization delay between App Review and Distribution, or if there is anything else I should check on my side. Thank you very much for your time and assistance.

Dear Support Team, ​I am writing to seek technical assistance regarding a persistent issue with Dolby Vision exporting in DaVinci Resolve 20 on my iPad Pro 12.9-inch (2021, M1 chip) running iPadOS 26.0.1. ​The Issue: Despite correctly configuring the project for a Dolby Vision workflow and successfully completing the dynamic metadata analysis, the "Dolby Vision Profile" dropdown menu (and related embedding options) is completely missing from the Advanced Settings in the Deliver page. ​My Current Configuration & Steps Taken: ​Software Version: DaVinci Resolve Studio 20 (Studio features like Dolby Vision analysis are active and functional). ​Project Settings: Color Science: DaVinci YRGB Color Managed. ​Dolby Vision: Enabled (Version 4.0) with Mastering Display set to 1000 nits. ​Output Color Space: Rec.2100 ST2084. ​Color Page: Dynamic metadata analysis has been performed, and "Trim" controls are functional. ​Export Settings: ​Format: QuickTime / MP4. ​Codec: H.265 (HEVC). ​Encoding Profile: Main 10. ​The Problem: Under "Advanced Settings," there is no option to select a Dolby Vision Profile (e.g., Profile 8.4) or to "Embed Dolby Vision Metadata." ​Potential Variables: ​System Version: I am currently running iPadOS 26. ​Apple ID: My iPad is currently not logged into an Apple ID. I suspect this might be preventing the app from accessing certain system-level AVFoundation frameworks or Dolby DRM/licensing certificates required for metadata embedding. ​Could you please clarify if the "Dolby Vision Profile" option is dependent on a signed-in Apple ID for hardware-level encoding authorization, or if this is a known compatibility issue with the current iPadOS 26 build? ​I look forward to your guidance on how to resolve this. ​Best regards, INSOFT_Fred

We recently migrated our entire product to Apple Unified Logging due to the various benefits it provides. However we immediately started hitting the "log quarantine" problem ("QUARANTINED DUE TO HIGH LOGGING VOLUME"). This is partly because we are indeed over logging in a few cases (which we have to work on fixing), but also partly because it's a complicated product with potentially hundreds of libraries, and some of the code can legitimately be very busy. For example we have a system extension that's implemented both as a NetworkExtension client and an EndpointSecurity client, if we were to log decent information about each network or file system event so we can troubleshoot something, they are bound to be high volume logs. Now when our app is running in a normal user environment, this is not a problem. We can disable certain heavy log levels, or at least disable persisting for certain logs (one of the benefits of Apple Unified Logging we really like is that it allows very flexible controls, log config command, OSLogPreferences, configuration profile, we can employ whatever that suits a specific case). But ultimately, the question is what if we end up with a troubleshooting case we don't know exactly where a problem is so we just need the full logs at debug level? And not only just enabled, but because we might not know when the issue can happen either we also need to persist the full set of logs for as long as possible? We will start hitting log quarantine again. Granted this is a very extreme case, but if worst comes to worst, how can we even do that with Apple Unified Logging? Is there an option that allows us to override the quarantine, if but temporarily? I've searched a few relevant forum posts, some of which described log quarantine but no one had mentioned any solution for it (besides having to stop logging so much from the app but as I explained we do have legitimate cases where log volume can still be huge). I've also read The Eskimo's "Your Friend the System Log" and browsed some of the troubleshooting config profiles provided by Apple hoping to discover some hidden payloads but found none so far. There is an OSLogRateLimit environment variable that I noticed if I run a launchctl print system/<a-launch-daemon-lable> and it's usually 64. Is this something relevant? And knowing Apple it's probably something that can't be tampered with?

I had published an App, and my app has App Clip supported. The issue I faced is that I had received complaints where the user keep seeing the pop up "Apple Media Services Terms and Conditions Have Changed" when user clicked on the "Open" Button in the App Clip. What we had tried so far: Let user switch the Apple Id's region to our supported region. Let user try to log out and log in to Apple Id within the supported region.

This is probably a silly question, but I just want to make sure. The screenshot submission states: "Upload three screenshots of your app playground that best represent the user experience as .png or .jpg files. Do not upload handwritten notes, sketches, or outlines." For an Apple Pencil based app, can I sketch in the canvas to show the abilities of the app in the screenshots? I assume yes and that this only refers to submitting mock-ups of apps, but I wanted to be super sure I won't be going against the rules.

Hello, I am facing a recurring issue with Xcode iOS simulator (preview). I want to preview a SwiftUI for iOS in Xcode, but the Simulator app fails to boot up. I receive the following error in Xcode: Cannot Preview in this file. Simulator was shutdown during an update. I have tried the following: Completely uninstalling XCode and deleting all developer data, then reinstalling everthing again. Shutdown and restart Deleting all developer data, deleting XCode cache Reinstalling iOS Simulator runtimes and reconfiguration of simulators. Tested using different simulator and runtime versions. "xcrun simctl --set previews delete al" My reported issues: FB20987522 FB20485454 Thank you Best regards, Jens

hi, first time submitter her, having problems with IAP and getting review approved. Apple reviewer keeps saying that attempted purchase results in error: subscription product not available. please try again later" i have verified that sandbox returns a product,. how else can i test this without just submitting again?

My app was submitted on 1/27/2026 and is still in "Waiting for Review" with no updates. I submitted a request to Support several days ago with no response to see if there was an issue that needed to be addressed, and my request to schedule an App Review session was denied.

Hello, I'm implementing the wallet extension but I found a problem in the passEntries function. This following part is giving nil ando I don't know why if let entry = PKIssuerProvisioningExtensionPaymentPassEntry( identifier: element.id, title: element.cardType ?? "Card", art: self.testImage()!, addRequestConfiguration: config! ) { entries.append(entry) } I debug and all the arguments have information but it doesn't create the entry

I applied for the Apple Developer Program on January 31, 2026, and as of today (February 5, 2026), my enrollment is still showing as Pending. The payment was completed successfully at the time of application. Since then: I have not received any requests for additional documents or verification. I have contacted Apple Developer Support twice, but have not received any response so far. I understand processing times can vary, but the lack of response from support is concerning. Has anyone else experienced similar delays recently? Is there any recommended escalation path or alternative way to reach the Developer Support team? Any guidance would be greatly appreciated, as this delay is impacting my app release timeline. Thank you.

I am trying to create a developer account for my organization. I have validated our DUNS number and Entity Name on https://developer.apple.com/enroll/duns-lookup/. However, when I try to add this number to create a developer account, I get a pop-up suggesting a mismatch in the entity and DUNS number. I have tried this several times without any success. Request you to please help me resolve this issue. Thanks. Sanket