It's been a week waiting for the review Despite requesting a quick review and contacting technical support via email, there has been no change so far. What can I do? Apple ID: 6756184295
Search results for
Apple Maps Guides
151,754 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Thanks so much again for your time and effort, Kevin! I did look into the documentation and tried different approaches, but none seem to work. I also found a BLE sample project on the Apple Developer Documentation, and it is also terminated after some time. Yes, and that's expected. Across most/all our background APIs, the focus isn't on ensuring that processes never terminate but is instead on relaunching the process and returning it to normal operation. Case in point, this is the real problem here: However, unlike the documentation states, I wasn't able to implement State Restoration and receive Characteristic updates once the app is terminated because of Memory Pressure. Why? Is the problem that you're not being relaunched or is state restoration failing? What happens from the accessory side? One side note here is that what triggers the relaunch is activity from the BLE accessory, so if your accessory never generates activity back to the iOS device, then you may not relaunch. May I suggest updatin
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
Error: RoomCaptureSession.CaptureError.exceedSceneSizeLimit Apple Documentation Explanation: An error that indicates when the scene size grows past the framework’s limitations. Issue: This error is popping up in my iPhone 14 Pro (128 GB) after a few roomplan scans are done. This error shows up even if the room size is small. It occurs immediately after I start the RoomCaptureSession after the relocalisation of previous AR session (in world tracking configuration). I am having trouble understanding exactly why this error shows and how to debug/solve it. Does anyone have any idea on how to approach to this issue?
We are seeing a strange lifecycle issue on multiple MDM-managed iPads where application(_:didFinishLaunchingWithOptions:) is not called after the device is idle overnight. Even if we terminate the app manually via the app switcher, the next morning the system does not perform a cold launch. Instead, the app resumes directly in: applicationDidBecomeActive(_:) This causes all initialization logic that depends on didFinishLaunching to be completely skipped. This behavior is consistent across four different supervised MDM devices. Environment Devices: iPads enrolled in MDM (supervised) iOS version: 18.3 Xcode: 16.4 macOS: Sequoia 15.7.2 App type: Standard UIKit iOS app App: Salux Audiometer (App Store app) Expected Behavior If the app was terminated manually using the app switcher, the next launch should: Start a new process Trigger application(_:didFinishLaunchingWithOptions:) Follow the normal cold-start lifecycle Actual Behavior After leaving the iPad idle overnight (8–12 hours): The next launch skips didFinis
@DTS Engineer thanks for your reply! Though most of the info is clear, I find some insights worth additional clarifying: based on your reply, is it correct that as of now there is no requirement to implement Declared Age Range API for macOS apps? based on your reply, is it correct that this policy applies ** only to the new** Apple Accounts, created in TX after Jan 1st 2026 (as well as UT, LA, after their respective deadline dates)?
Topic:
App & System Services
SubTopic:
General
Tags:
Hi @Umeki, To enable all the technologies and access all the signals Apple has made available to comply with regional age assurance requirements, starting with Texas, you must build your app against the iOS 26.2 and iPadOS 26.2 SDKs and later, with Xcode 26.2 (17C52) and later. To view the latest Xcode versions and SDKs, see here. As of iOS 26.2 and iPadOS 26.2, age assurance includes the following signals: Declared Age Range API — Determine whether a person using your app is in an applicable region that requires additional age-related obligations. When a child account, or their parent or guardian, chooses to share age information, the Declared Age Range API will return the age band or age category, depending on legal requirements in the region. The API will also provide information about the method used to confirm the age band or category, whether parental controls are enabled, and whether the user is eligible for age gated features. For more details, see the following documentation: AgeRangeService
Topic:
App & System Services
SubTopic:
General
Tags:
Apologies if I misunderstand things completely. I am no developer, so memory management is completely foreign to me. OK. So, stepping back for a moment, I think what's helpful to understand is that one of the VM system’s basic primitive operations is designate that a range of address space corresponds to the contents of a file. That process is called mapping a file and is how, for example, executable files are loaded into memory so that they can be executed. That is, what part of what running an executable actually means is map the contents of that file into memory and start executing at a specific point. Similarly, the basics[1] of swap files are simple create a file and designate which parts of it correspond to specific memory ranges. Mapping VM address space to file ranges with what mmap() does. That is, a low-level mach memory function like vm_allocate() (what malloc calls within its implementation): https://web.mit.edu/darwin/src/modules/xnu/osfmk/man/vm_allocate.html ...basica
Topic:
App & System Services
SubTopic:
Core OS
Hello, Our Xcode Cloud builds are successfully archiving but fail every time during the Export archive for app-store distribution step. The issue appears to be a persistent authentication failure with App Store Connect that we are unable to resolve. Primary Error: The build logs show a critical authentication failure. IDEDistribution.critical.log shows: App Store Connect request for store configuration failed for account Session Proxy Provider... Unable to authenticate with App Store Connect. DVTITunesSoftwareService.log specifies the error is DVTITunesSoftwareServiceFoundation.DVTServicesSessionProviderCredentialITunesAuthenticationContextError.proxy. The build process eventually terminates during the IDEDistributionSymbolsStep with an Rsync failed error, which we believe is a symptom of the earlier authentication failure. Troubleshooting Already Performed: We have already taken the following steps without success: Verified the account used for the integration has Account Holder and Admin roles. Confirmed th
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Store Connect
Continuous Integration
Xcode Cloud
We are using AgeRangeService.requestAgeRange(ageGates:in:) with an age gate of 18 to verify adult users. The system prompt always displays the lower-bound wording (“17 or Younger”), even when the app’s requirement is to verify users who are 18 or older. We understand the UI is system-controlled; however, this wording causes confusion for users, QA, and product teams, as it appears to indicate a child-only flow even when requesting adult verification. Based on the demonstration video, it appears that they have another more coherent message. In Apple's example, it is different, and it is correct that we need to specify 18 years or older in the implementation. A little more context might be helpful, but we are creating a kind of wrapper with React Native that receives that value as a parameter, which is 18.
Hi @chou_ios, Where legally required, you must check the age of the people using your app, starting with new Apple Accounts created in Texas on or after January 1, 2026, which has obligations only for iOS and iPadOS apps. To learn more, see Next steps for apps distributed in Texas. To test content revocation in Sandbox on iOS and iPadOS 26.2 and later, please see the documentation below: Testing Age Assurance in Sandbox https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox Cheers, Paris X Pinkney | WWDR | DTS Engineer
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
For testing permission response we can use the sandbox account However, when testing permission requests using the AskCenter API, none of the ask API works for me in xcode 26.2 rc and iOS 26.2 rc. For SignificantAppUpdateTopic, I got errors like The user is in a region that does not support this type of ask in the console log, but I've already set my billing address to Texas. For CommunicationTopic, the console shows several XPC-related errors, and I’m not sure which of them are relevant. Both of them show an alert view of Can't ask, An unknown error occurred Can someone help to guide us how to test the request flow? Thanks
Hi @coderFeng, @mr846, Where legally required, you must check the age of the people using your app, starting with new Apple Accounts created in Texas on or after January 1, 2026, which has obligations only for iOS and iPadOS apps. To learn more, see Next steps for apps distributed in Texas. To test content revocation in Sandbox on iOS and iPadOS 26.2 and later, please see the documentation below: Testing Age Assurance in Sandbox https://developer.apple.com/documentation/storekit/testing-age-assurance-in-sandbox Cheers, Paris X Pinkney | WWDR | DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
Hi @oleksiikaharov, You wrote: While requestAgeRange(ageGates:) seems to work just fine for iOS app, for macOS app it always throws Not available error (DeclaredAgeRange.AgeRangeService.Error.notAvailable) Where required, Apple uses age assurance methods to confirm an Apple Account holder’s age, and share age categories with you through the Declared Age Range API. Where legally required, you must check the age of the people using your app, starting with new Apple Accounts created in Texas on or after January 1, 2026, which has obligations only for iOS and iPadOS apps. To learn more, see Next steps for apps distributed in Texas. Then, you wrote: Also, after giving permission, is there a way to actually revoke it? In Age Range for Apps menu I can only view the list of apps that have my consent to share my age range, but not the ability to revoke it. To test content revocation in Sandbox on iOS and iPadOS 26.2 and later, please see the documentation below: Testing Age Assurance in Sand
Topic:
App & System Services
SubTopic:
General
Tags:
Hi @skitudeiosdevelopers, You wrote: [...] What is the correct and Apple-approved approach for handling age verification and restricting access for minor users on iOS versions prior to 26, given that the Declared Age Range API is not available on those systems? To enable all the technologies and access all the signals Apple has made available to comply with regional age assurance requirements, starting with Texas, you must build your app against, you must build your app against iOS 26.2 and iPadOS 26.2 SDKs with Xcode 26.2 (17C52). View the latest Xcode versions and SDKs here. Existing adult accounts and child accounts for kids and teens will not be affected. To learn more, see Next steps for apps distributed in Texas. Cheers, Paris X Pinkney | WWDR | DTS Engineer
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
Hello, we get in touch as we need some guidance from Apple regarding age verification for minors in our app. Our app supports iOS 17 and above. The Declared Age Range API is available only starting on iOS 26, but we must comply with legal requirements (e.g., Texas SB 2420) and ensure that minor users cannot access certain sections of the app, regardless of the version of the operating system. Our question: What is the correct and Apple-approved approach for handling age verification and restricting access for minor users on iOS versions prior to 26, given that the Declared Age Range API is not available on those systems? We want to ensure that our implementation aligns with the regulations, the App Store Review Guidelines and platform expectations.