“Apple Maps Guides”

[quote='820585021, faisalIkwal, /thread/820585, /profile/faisalIkwal'] We don't apply rules in these methods [/quote] So what do you do in those methods? In many cases a transparent proxy can get away without implementing those methods at all. If you do implement them: Make sure they return promptly. In the case of the sleep(…) method: Implement the async version and have it return promptly. Implement the completion handler version and have it call the completion handler promptly. [quote='820585021, faisalIkwal, /thread/820585, /profile/faisalIkwal'] com.apple.developer.endpoint-security.client is not present in .entitlement file. [/quote] Network Extension and Endpoint Security are separate subsystems. It’s fine to implement an NE sysex without any ES bits in it. In fact, it’s more than fine, it’s very common. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

It sounds like you’re using Developer ID signing for day-to-day development. That’s a mistake on multiple levels. I talk about this in general in The Care and Feeding of Developer ID, but there are extra issues with system extensions, where system policy requires that Developer ID signed sysexen be notarised. So my advice in this case. Use Apple Development code signing for day-to-day development. Use Developer ID for pre-release testing and distribution. There are a couple of key benefits with this approach: It lets you build and debug without enabling development mode, which is a big win IMO. Xcode’s automatic code signing works well with Apple Development signing. Even if you’re not using Xcode, you can create a small test project in Xcode, get it working, and then follow the same path it took. See Debugging a Network Extension Provider for specific advice on how to bring up a provider in Xcode. One thing that Xcode doesn’t handle is the -systemextension suffix )-: To learn more about tha

Right. When dealing with JSON it’s best to use a JSON parser rather than trying to treat it as text. And modern versions of macOS have (at least) one such parser built in, that is, jq. For example: % system_profiler -json SPHardwareDataType > tmp.json % jq -r '.SPHardwareDataType.[0].platform_UUID' tmp.json FCBBB6FF-E6F4-5372-87C0-1944DA936938 Read the jq man page for more on how it works. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

alam333, I don’t see any relationship between your issue and the one being reported by DarrenHan. And regarding your issue, let’s focus that discussion on this thread, which you’ve already posted on. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Are folks still having this problem? I just tried it myself and everything worked for me, so either this was a transient thing that’s now fixed or it’s caused by an environmental thing that doesn’t apply in my case. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If Apple were to rotate or replace the attestation certificate chain (for example, in the event of a compromised root attestation CA), would this automatically trigger a repair / re-enrollment flow on all previously enrolled devices? Or is the repair flow initiated only based on server-side decisions, such as attestation validation failures or explicit policy enforcement?

Thanks for the update. I did some investigation on my end using Charles to inspect the traffic and verify whether any Apple attestation APIs are being called. I can confirm that an attestation API is indeed triggered, but I’m not entirely sure what happens behind the scenes. Any progress on the research at your end ?

Hi Ziqiao, thanks for looking into this! I've verified using CKFetchSubscriptionsOperation.fetchAllSubscriptionsOperation() on both Development and Production (TestFlight) devices. All 5 subscriptions are present and correctly configured in both environments. The output is identical between both environments. Here are all 5 subscriptions as returned by CKFetchSubscriptionsOperation: fr-sub-v3 (FriendRequest) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=FRIEND_REQUEST_BODY, locArgs=[senderUsername] category=FRIEND_REQUEST, desiredKeys=[senderID, senderUsername] rec-sub-v3 (MediaRecommendation) Predicate: receiverID == [userID] AND status == pending badge=true, sound=default, contentAvail=false locKey=RECOMMENDATION_BODY, locArgs=[senderUsername, mediaTitle] category=RECOMMENDATION, desiredKeys=[mediaTitle, mediaType, senderID, senderUsername] fs-a-sub-v3 (Friendship) Predicate: userAID == [userID] badge=true, sound=default, contentAvail=false locK

I have the same issue and filed a bug report already: FB22324179 Since updating to iOS 26.4, iCloud remote notifications (CloudKit push notifications) are no longer delivered. The same setup worked reliably on iOS 26.3 without any changes to the app or server configuration, so this a new regression from Apple. didReceiveRemoteNotification: in AppDelegate gets not called anymore.

Just to add one more piece to this... Make a change on the Mac AppleTV makes the change instantly Apple Watch makes the change instantly iPhone only updates after you leave the app and launch it again iPad only updates after you leave the app and launch it again

Update: Even though App Store Connect is saying my domains are valid after correcting the team id, and the cdn cache has what appears to be proper values. App clips are still not working for me - meaning, every time I scan the QR code with the camera when the app isn't installed, it doesn't go to the app clip. If I get App Store to create an app code for me, it says no content to show (though this may be because the App Store is saying received for advanced app clip experiences I wrote). So I checked the CDN here: https://app-site-association.cdn-apple.com/a/v1/akin-server-side-staging.onrender.com, I can see my aasa is proper to my understanding in the CDN cache. I updated the entitlements as recommended: appclips:akin-server-side-staging.onrender.com I also reviewed several Apple Documentation pages including the Fruta, downloaded, Fruta and examined the configuration part by part. Specifically, the entitlements for both the app clips and parent target. On my iOS device, I went to Settings > Dev