“Apple Maps Guides”

Hi SeoulForest and everyone, I’m joining this thread to share additional information regarding the reported issues with AlarmKit. While I don’t have a solution yet, I have both received user reports and personally experienced the same or similar behavior. The occurrence is rare (about once a month), but it happens consistently enough to be a reliability concern for an alarm-based feature. My Implementation Context: I have implemented a system that schedules approximately 60 fixed-schedule alarms. The Issue: Alarms occasionally fail to trigger at the scheduled time. Comparison: I set Local Notifications using the exact same date objects. These notifications arrive perfectly on time, which confirms there are no errors in the date/time logic itself. Observed Behaviors: Delayed Triggers: Alarms sometimes fire several minutes late, or in some cases, not at all for a long period. Midnight Firing: I have observed instances where an alarm that failed to trigger at its scheduled time would suddenly fire around midnigh

workaround until apple fixes it: alias simpaste='pbpaste | xcrun simctl pbcopy booted' then run simpaste in terminal before pasting in the sim, this has been working for me (so far)

We should not be expected to all file feedbacks for Apple to fix a critical bug that should not have shipped in the first place. CloudKit is opaque and difficult enough to implement and test that there is sometimes no way to know if we are at fault or if it’s some quirk of the system. Only apple could have caught this bug with certainty and they should be performing a root cause analysis about why it shipped at all. Apple’s own sample app fails. Why is that not an automated test?

Enrolled: Monday, March 23. That's when you applied for a membership, right? You wouldn't be posting this topic if you are already enrolled in the developer program. Received the 2 business days to process email. What have you done with it? It'll take Apple, Inc. several steps to make enrollment good. Apple, Inc. is a Certificate Authority. So they won't approve enrollment application without their identity verified, I suppose. You don't mention which membership type you are applying for. That's partly why some people ignore your cry for help.

Would it make sense for Apple to change the default iOS 17 minimum deployment target to 17.5 since that it the newest version with a simulator available? Or is there any reason that it would make sense for Apple to release and iOS 17.6 or 17.7 simulator? Should I submit a Feedback Assistant report?

Thank you, my apologies for the hallucinated entitlement. I read your post shortly after I posted here. One other thing, what's the documented behavior if Apple Music is in the foreground but not playing anything, and my app attempts to do player.play()? I have experienced a queue success but playback failure on MacOS (so using ApplicationMusicPlayer), only if the user has the system's Apple Music up. What's the documented behavior if the user has something actively playing on the system music player?

Thank you! this is very helpful and clarifies the issue a lot. I will go ahead and file a request for a Core HID development variant. Regarding the SIP / AMFI workaround: I understand the security concerns, and I agree that lowering system security is not an ideal solution. Of course there isn't a way to enable that only while the app is in use isn't it? That would be an acceptable risk for me. Or is it inherently a reboot-level change? In parallel, I will also explore mapping to keyboard and mouse events as a fallback, even though that is not the original target and is clearly less suitable than a true controller-visible solution. More broadly, I think it would be very valuable to have a simple user-space API for controller virtualization available to hobbyists and personal developers as well, even if limited to development builds. I understand it's possible on Windows. Thanks again for the detailed explanation.

xcrun simctl list just hangs for me. I found my Intel based Mac Pro still works with the same set-up. One of my Apple Silicon Mac minis sort of works, one does not no matter what I try.

I'm now wondering if this is a macOS 26.4 issue. I clean everything out again, reinstalled Xcode Xcode 26.3 (17C529), did the simulator updates (and waited for Xcode to stabilize its other downloads), rebooted, and all the simulators it had installed were in status unavailable state again. How could anybody at Apple not have encountered this, and why was it released to the public?

Hi, does anyone have a phone number to contact apple developer support? i have sent several emails but still no answer. thank you