“Apple Maps Guides”

What you'll find is that there are two clients— yours and a (presumably unrelated) 3rd party client. The other ES client is basically a 3rd party logger that's not active. Ours does some auth work, but we're fairly certain in this case it's just monitoring to do reporting and follow-up scans. Do you know exactly what kicked off your helper process? Both in terms of the triggering event and the target file? No. At the time, the system had been idle for 2 hours. In this case, we do observe a system update being staged in the background, but not in all other instances. I suspect it was a FILE_NOTIFY_CLOSE. It would be insightful to know if APFS triggers that or related ES events when decompressing a file. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. I will submit unified logs that cover the period in question, but your point remains. That ES check can now act a

Our engineering teams need to investigate this issue, as resolution may involve changes to Apple's software. Please file a bug report, include a small Xcode project and some directions that can be used to reproduce the problem, and post the Feedback number here once you do. I'll check the status next time I do a sweep of forums posts where I've suggested bug reports and post any information about changes I am able to share to this thread. Bug Reporting: How and Why? has tips on creating your bug report.

I don't normally complain. But I am unpleasantly surprised that Apple shipped Xcode Version 26.4 (17E192) with its known Anthropic OAuth token bug. Xcode 26.4RC and the RC version have proven to be less stable in using Intelligence, specifically Claude than was Xcode 26.4b3. Please folks, test better before releasing.

Thank you for your post. The App Store team does not monitor the forums, and I believe you set your app as “Made for Kids” for the first time when you deployed the app. Since your app is already live, the “Made for Kids” flag and the “Kids” category are often locked to prevent developers from changing an app’s target audience without parental consent. This will be a significant privacy issue as you can see. To resolve a locked metadata field like that, you need to contact App Store Connect Support, not App Review. Visit the Apple Developer Contact Us page. The representative can file an internal ticket directly to the App Store Connect engineering team to manually unstick the metadata field on your account if appropriate. Now, depending on your app and the people affected by that change, the engineering team will decide whether to make that change. I’m not in that team now I know their process. Once App Store Connect Support unlocks the field and you successfully uncheck “Made for Kids,” you can subm

Hi, @Dominik_2 I'm a little late here but I'm having the same issue. Did you ever figure this out? I can't even get a 2019 Mac Pro to properly activate LOM and a 2023 Mac mini which gives me the same Address Already In Use error. Here's all my testing and info. Apple are you there??? Infrastructure: • Mac mini 2023 (M2, 10Gb Ethernet, MacMini.local, macOS 15.x Sequoia 15.7.4) — MicroMDM v1.13.1 • Mac Pro 2019 (MacPro7,1, Intel T2, MacPro.local, macOS 15.x Sequoia 15.7.5, T2 firmware 23P3120) • Both supervised via Automated Device Enrollment (DEP) through Apple Business Manager • Both enrolled: IsSupervised = 1, APNs working on both • Both are Controllers and Clients LOM Current State: Mac mini (Apple Silicon M2): • LOM profile installed ✓ • lom0 interface active ✓ • Port 55555 listening on * ✓ • LOMDeviceServerColsolidated path (Apple Silicon) ✓ • com.apple.AppleLOM.XPC active=1 ✓ • com.apple.AppleLOM.Watchdog active=1 ✓ • Mac Pro CAN reach mini's lom0 port 55555 — TCP conn

You can formally request new API functionality, like an animated map layer of wind data, through Feedback Assistant.