“Apple Maps Guides”

I signed up and paid on the 25th. After no response I called apple tech support. 2 hours later. The response is they can’t help me but would push my request up the chain. I just paid a second time thinking it may be a glitch. Honestly this is unacceptable. When my app had a million users will it take three weeks to reach apple when something goes wrong?!?!

Thank you again for your previous response. I'd like to follow up on one specific aspect: are there any special enterprise programs or partnerships (for example, for medical device manufacturers or healthcare institutions) that allow an app to obtain additional background execution capabilities or enhanced HealthKit access beyond what is available to a standard Apple Developer Program member? I understand that for a typical developer, continuous background execution is not permitted. However, I'm trying to determine whether there is any alternative path that would enable more persistent background health data monitoring for medical-grade applications. If such programs exist, I'd appreciate any guidance on how to explore or apply for them. Thank you for your time and insight.

I saw the same issue on my Apple Watch Ultra 2 + watchOS 11.3 (22S555), as mentioned here. I haven't yet tried with watchOS 26, but if you follow the documentation to add underwater-depth background mode in your Info.plist, and the issue is still there, I’d suggest that you file a feedback report – If you do so, please share your report ID here. Thanks. Best, —— Ziqiao Chen  Worldwide Developer Relations.

We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature and is better suited for the Apple Support Communities https://discussions.apple.com/welcome I would recommend to post it there instead of the developer forums.  Travis

In relation to the OP experience, since a few weeks, my app also has received an unprecedented amount of SIWA user complaints indicating they are not getting our emails. Investigation on a subset of these feedbacks have ruled out user error (spam, outdated redirect email address). Like OP, we're always getting a success response code when submitting emails to Apple's relay server. I had opened an issue in feedback assistant a few weeks ago: FB22012678 Are you still able to investigate the case of need one with fresher logs? FYI I've been using SIWA for several years, and something clearly started to happen a few weeks/months ago. Thank you

If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Request a call with an Apple representative to discuss the outcome of the review. Make this request in the App Store Connect communication. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.

I’m not the right person to address that. I don’t have any in-depth experience with HID stuff. Sorry, that would be me and I apologize for having missed your post until now. (thanks to Quinn for giving me a heads up!) Questions reordered for clarity: At what stage is it enforced: activation, personality matching, provider attach, or before Start()? First off, as general background, I have a forum post here that has an overview of the IOKit->DEXT loading flow. In any case, entitlement validation is implemented as a secondary stage of the IOKit passive match process, with each family handling the details of entitlement validation. For reference, this is how the PCI Family does these checks. Is com.apple.developer.driverkit.builtin required for a third-party IOUserHIDEventDriver to match a built-in internal trackpad IOHIDInterface? I haven't actually looked at the HID families implementation in detail so it's possible there are other requirements, but, yes, at a minimum the built-in entitlement is required. I

Hello richardbe, Thanks very much for your detailed investigation into the crash. Can you please copy your findings into a bug report on Feedback Assistant? Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Afterwards, please post the FB number to this thread. Bug Reporting: How and Why? has tips on creating your bug report. Also, it would be very helpful to our engineers if you can attach the JSON-formatted .ips crash report to the bug report by following the instructions in Posting a Crash Report and Acquiring crash reports and diagnostic logs. Thank you for reporting, Richard Yeh  Developer Technical Support

If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review: Reply to the message from App Review in App Store Connect and request clarification. Request a call with an Apple representative to discuss the outcome of the review. Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines. Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.

This is still happening in the debug console, app not crashing. Wonder if this is something I can ignore? A fix is documented elsewhere? Not fixed? The Apple sample app SwiftDataFlashCardSample prints the same log messages than my app I just started to implement. On macOS Tahoe 26.4 (25E246), Xcode Version 26.4 (17E192).

Thanks for bringing this to the forums. [quote='821062021, hsbc-uruguay, /thread/821062, /profile/hsbc-uruguay'] Any improvements or new tools available since the 2022 DTS post? [/quote] I’m glad you asked (-: Recently the App Store Connect folks updated their documentation to describe a technique for transferring app groups between teams. See App Store Connect Help > Transfer an app > Overview of app transfer > Apps using App Groups [1]. Given that, it’s now possible to use an existing technique — using an app group ID as a keychain access group — to preserve keychain access across an app transfer. I’ve just updated App ID Prefix Change and Keychain Access to describe this approach. Now, this is all very ‘bleeding edge’, and thus it’s possible that you might run into snags. However, it’s certainly an option worth exploring. [quote='821062021, hsbc-uruguay, /thread/821062, /profile/hsbc-uruguay'] We just finished an app transfer to our developer account. [/quote] The option I’m describing typically r

Thanks Quinn, that was exactly the right pointer. We traced through the disassembly of xzm_main_malloc_zone_init_range_groups on macOS 26.3.1 and correlated it with the open source in rel/libmalloc-792 (xzone_segment.c:1210-1250). Here's what we found: The CONFIG_MACOS_RANGES path computes: ptr_reservation_size = XZM_RANGE_SEPARATION + XZM_POINTER_RANGE_SIZE + XZM_RANGE_SEPARATION = 4G + 16G + 4G = 24 GiB ptr_start = 16GiB + (entropy % 736) * 32MiB It then calls mach_vm_map with VM_FLAGS_FIXED for 24 GiB at ptr_start. The 736 granules cover [16 GiB, 39 GiB), ensuring the reservation fits under the 63 GiB commpage limit. Why dylibs land above 16 GiB: The binary is a Chromium component-build test binary (browser_tests) that loads 516 Chromium dylibs plus system libraries (1543 images total). The main executable alone consumes 5.54 GiB of VA (4 GiB __PAGEZERO, 517 MiB __TEXT, 1.04 GiB __LINKEDIT). The 516 Chromium dylibs add another 10.19 GiB of aggregate VM (2.26 GiB __TEXT, 3.86 GiB __LINKEDIT). Combined with