Thanks for the reply!!I've watched the WWDC 19 video. It just glosses over permissions entirely without any details, except to say that a mechanism for Health is added in watchOS 6. Notifications also has an explicit permission system (I have not looked nn detail at it), but I am only trying to use CoreMotion which in iOS 5 needed permission on the paired phone AND inside the Watch app on the paired phone. I can not find an API to request permission on a standalone watch in watchOS 6. I have a switch statement on the result oflet auth = CMAltimeter.authorizationStatus()What should I execute in the case .notDetermined ?

This still happens. I just spent 12 hrs!!!! downloading Xcode 12.01 from the store to replace v12. Now app launches to device take 2 1/2 minutes after launch screen appears. Deleting the specific iOs DeviceSupport folder for the device's version of iOS did the trick. After the folder deletion, Xcode reloaded the symbol tables from the device and all was well. App launch time now back to 1-2 seconds.

I also have this problem with UserDefaults in Catalyst. I tried @daspoone 's solution of adding "user-preference-write" = TRUE to the entitlements file and POOF! the app crashes basically can not find entitlements file! It may be that these warnings are just log noise as @Quinn suggests (my app's preferences seem to be read and written just fine), but with every new release of Xcode, there is more and more unhelpful garbage in my debug console!

Thanks, but this is a side step, not an answer. I am aware of CreateML as a developer tool. It is great, and I have built many mlmodels with it, but it is somewhat limited, and the playground tool CreateMLUI offered finer granular control and more extensive outputs. I have a training data set which produces a model with sub-par performance. I want to try CreateMLUI (if still possible)for diagnostics purposes.

I fixed the layout reversion issue by calling my method that mods the layout constraints from an override of viewDidLayoutSubbviews in each affected VC For the moment, I am sticking with the NSWindowDidBecomeMainNotification event to trigger activation events in my viewControllers, despite the slight increase in overhead by observing the event in all open VC.

The 12.6 Gb is the size of the Compressed download, after expansion, the app is around 35 Gb, depending on options. You need about 45-50 Gb during decompression.

Thank you Quinn! Your note is the only reply from Apple that explains the issue and why you can safely ignore the warning when our code is not involved. Thank you! Other Apple folks have addressed this in other threads but provide only a robotic answer to file a feedback report. You da man!

MrOfu: I get the same, superfluous warning whenever I close a Webkit window: [assertion] Error acquiring assertion: <Error Domain=RBSServiceErrorDomain Code=1 "target is not running or doesn't have entitlement com.apple.runningboard.assertions.webkit" The suggestions to add BackgroundModes and web view.uiDelegate, separately or together had NO effect on this "feature", ie worthless Apple warning.

Two possible solutions to CocoaPods breaking with Xcode 14.3 (it is due to Path change in Xcode) change the script in CocoaPods as noted above download Xcode 14.2 and use it until the new revision of CocoaPods is available

Yes! What ever you did seemed to clear the logjam. The file completed processing, allowing me to submit for review. Additionally, this new app was reviewed and accepted in record time today: Submitted 14:23, In Review 15:02, Accepted 15:22 Good Job!