Apple Maps Guides

[quote='809951021, Ionnier, /thread/809951, /profile/Ionnier'] I have a .app that runs as LaunchDaemon and configured to be an Agent (LSUIElement) that is stored in /Applications. [/quote] Wow, that’s quite a combo. Lemme see if I understand this correctly: You have a launchd daemon. That’s embedded in an app-like wrapper. Its Info.plist contains LSUIElement. Presumably because the daemon displays UI. And the daemon is run via a launchd property list in /Library/LaunchDaemons. Is that right? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='869193022, DTS Engineer, /thread/809830?answerId=869193022#869193022'] That's the classic” UNIX system machine swap [/quote] Well, I’d argue that the classic Unix swap involved a swap partition. None of this fancy, new fangled anonymous pager stuff (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can edit the questions by creating a new release without submitting the release for formal review. But I am not sure if that is enough to be considered as fulfilling the requirement. Anyone knows? In addition, for one of my apps, apple has auto computed the age rating and I found it to be accurate. So do I even need to add a new build and re-update age ratings?

two questions are still unanswered: Q1. If we do not submit a new binary and just leave the new age rating either I) auto computed by apple or Ii) updated manually by adding a new release without actually submitting the release for review Do these count? Q2. What happens if an app doesn't have new age ratings after 31 Jan 2026? Delisted? Or blocked from all future releases? Or can only submit after answering new age ratings?

Hi Ed, Thank you very much for your previous guidance. Our current app requirement is to allow users to run a Shortcut, share an image to our app, and then immediately receive some chat-based suggestions after we process the image. When using App Intent, I noticed that we cannot process the image directly within the invoked UI. It appears that this is restricted by Apple’s privacy protections—any attempt to handle the data immediately results in the background privacy indicator showing a blocked status. Therefore, App Intent does not seem to meet our need to process user-provided images directly. Following your advice, I added an Action Extension to the project. This successfully adds our app to Shortcuts as an available action. However, when I try to use the “Share with App” feature from the share sheet, our app still does not appear in the list. The only options shown are: Notes, Health, Reminders, and Freeform. Could you help us understand why our app does not show up in the “Share with App” menu,

Finally, I got the updated agreement popup—even though I had already accepted it before. Here’s what I did: Since it seemed like there was a glitch in their system (or maybe the new agreement wasn’t appearing in the Agreements section for some reason), I went to the Agreements section under Business (App Store Connect > Users and Access > Business > Agreements). Then I applied for “Digital Services Act Compliance,” which hadn’t been completed on my account, hoping this update would trigger the new popup again. I filled out the information for “Digital Services Act Compliance” and submitted it. After that, I received an email from Apple confirming they had received the trader contact information and would verify it. This morning, they sent another email saying it was verified—and, as I expected, this triggered the agreement popup again on App Store Connect. I accepted the agreement from there, and now it’s showing in the Agreements section. Still, it’s not a straightforward way to get the pop

I see, thank you for the explanation. Yes, my machine has 16 GB of RAM and I read about the VMM at https://developer.apple.com/library/archive/documentation/Performance/Conceptual/ManagingMemory/Articles/AboutMemory.html#//apple_ref/doc/uid/20001880-BCICIHAB Is there a guide for macOS on the steps you describe at the end, that is on how to allocate a swapfile, mmap that swapfile into memory, then use that mapped memory instead of system-allocated memory? I am familiar with dd from /dev/zero etc and the usual declaration of a swapfile by appending on /etc/fstab, but that is in Linux, and perhaps that does not work on macOS...

So, I got some more time to look at this today and need to change my answer a bit. Let me actually jump back to here: All the documentation I was able to consult says that macOS is designed to use up to all available storage on the startup disk (which is the one I am using since I have only one disk and the available space aforementioned reflects this) for swapping, when physical RAM is not enough. Did you actually see this in our documentation and, if so, where? If any of our modern documentation actually says that we do this, then that's something I'd like to clean up and correct. So, let me go back to the idea here: macOS is designed to use up to all available storage on the startup disk That's the classic” UNIX system machine swap and, historically, it's how Mac OS X originally worked. However, the downside of this approach is swap death in one of two forms: Soft, meaning the system has slowed down to the point that the user is now no longer willing to use the machine, even though it technically still wor

Eventually, I got an email from Apple with the subject line Welcome to App Store Connect. From the moment I enrolled, it took about 12 hours to propagate my access.

Same concerns here. I have over a dozen apps and it's not practical to submit new builds for every one just to update rating metadata on AppStoreConnect. This has got to be a serious goof on Apple's part.

i have the same issue when using a custom model to detect small objects on frame, i generate the bounding boxes and pass them to track function, the insta 360 light starts flashing which means the observation vectors are sent to device but the gimbal doesn't move at all, it does move randomly a bit when i use type .humanbody, this makes me think the issue is on the api side. can anyone from apple dev team look at this?

So, just to confirm: Apple sent an email to developers with the subject: Final reminder: Answer the updated age ratings questions. That email says: We’re reaching out because you have not provided responses to the updated age ratings questions in the App Information section of your app in App Store Connect. If you don’t answer these questions by January 31, 2026, you won’t be able to submit app updates in App Store Connect. Right, so if we don't submit these new age ratings we cannot submit new app updates after January 31st 2026, but in order for us to change those age ratings we have to submit new versions of our apps? Am I really being told to build and archive a new version of each of my apps just to update the age ratings? This is what I currently see on one of my apps: so this is great... And, just to make it even more complex than it needs to be, the email also says this: Please also note that the Texas SB2420 legislation goes into effect January 1, 2026. Under this law, making an age rating c