@DTS Engineer, if I receive this error code when attempting to create records, what are your thoughts on me traversing the sandbox and deleting the CloudKit directory to mitigate this? Hopefully a fix in 18.4 or later, but is there anything I can do safely now?

FB16452716 - Core Location / Documentation: Create documentation about NSLocationRequireExplicitServiceSession since it is missing from Core Location docs

@DTS Engineer The Swift Charts example code falls into this trap too. It embeds a NavigationSplitView inside a TabView. This sample code should be updated if this layout is to be avoided because it causes unexpected behaviors. I was just running this example code and the view modifier to require tabs wasn't being respected. I guess 'as designed'? https://developer.apple.com/documentation/charts/visualizing_your_app_s_data

FB15382945 - HealthKit: Give third party developers access to the internal heart rate zones recorded and associated with Activity app workouts

@cfc I have successfully saved and related .workoutEffortScore samples to workouts, just like the Fitness apps. The documentation is practically non-existent on the new types. To make matters worse, there was no developer session describing these APIs at WWDC24. If you're the author of the workout, it should just work. You do need to query the sample and use a workout predicate to fetch it. It doesn't add the sample to the workout like the Builder API does with other sample types.

FB15131454 - Settings: PRODUCTION ISSUE - Sharing an ips file from device analytics does not open my app on iOS and iPadOS 18 RC, works on iOS 17.6.x

Just mark your reply was the answer.

@Gualtier Malde I documented a few of my use cases in here: FB13596401 - Core Bluetooth: Enable ability for visionOS device to be a peripheral - CBMutableService init is unavailable

Thanks @eskimo. In case it wasn't obvious this is related to my other post you replied to for some stuff I'm working on. https://developer.apple.com/forums/thread/746376 Not useful to me agreed, but would it be useful (or required) to the Console app on Mac to attempt to parse the report into the friendly view? I will try removing keys that are not documented and see if the Console app can represent the 'translated report'. If I find anything that breaks I'll update my feedback.

Thanks Quinn @eskimo for putting that post together. I figured I would run into some limitations or that what I want to build would simply not work in a sandbox. It is easy (easier) for a developer to know where they placed their app binary DSYMs, but not intuitive where system framework DYSMs are located. This is a very related feedback that you can check out: FB12349101. The bigger flaw in my plan is symbolication of system frameworks only works if you had access to that device and os combo.

Yes, CoreLocation will bring the app back from user-terminated state. This works for both the GPS based and Beacon based APIs. However becoming a legitimate iBeacon isn't an easy task if you have a battery budget.

I would suggest you file feedback for this. I too want this as a capability and it is rather limiting for a brand new device. Fingers crossed just a V1 of software sort of thing and not a long term constraint. FB13596401 - Core Bluetooth: Enable ability for visionOS device to be a peripheral - CBMutableService init is unavailable

@Developer Tools Engineer Any comment on what happened or what was performed to resolve it? If none that can be shared, what is the best course of action if it occurs again? I will mark my feedback as resolved.

FWIW, Apple Music, as of iOS 17.3, still shows "Find Friends" -- "Apple Music will periodically check the contacts on your devices to recommend new friends.". Given ALL of the discover user APIs are deprecated, one only using CloudKit would then have to create a new record type that saves user contact info. By design, in order to query that data, it would have to be public otherwise you couldn't perform query operations on it against your contact info.

I spoke with the CloudKit team during WWDC23 about this feature. They said, unfortunately there is not a replacement and that I should file feedback. I did - FB12341314. The feedback got a reply saying there is not plans to replace the functionality. Apple Music is accessing user contacts if you look at App Privacy Report, previously it felt like they were using this feature to build their discover users. This feature was underrated and might be gone forever. I suggest you also file feedback.