Posts

Post not yet marked as solved
8 Replies
0 Views
Hey thanks for replying! You can file a feedback report for this and use a private scoped database to initialize your container as a workaround. Done! FB9179243 recordName and modifiedAt are default fields on every record type, so if they are missing you should definitely file a feedback report with CloudKit. I have a feeling this might just be a display issue in the CloudKit dashboard UI - Maybe new with the new dashboard update? I've never really used CloudKit 'in anger' so I don't really know. What appears as 'Name' in both the "Records" table and "Record Details" sidebar, seems to be "recordID" if filtering, and also in the field dropdown when you are creating the index. So I guess it is there, it's just not named what I was expecting. And it's the same situation for modified. Does this sound right? This looks like you tried to use a database file with the public database that was previously syncing with the private database. If you can reproduce this from a clean (empty) database file and some set of steps we'd appreciate a feedback report with a test case in it we can run I am definitely using a coredata database file that has never touched the private database. It's reproduce-able. I've tried with a few different CoreData schemas to see if it was something I was doing there but that appears to have no effect. The TLDR is: If the core data store is empty, creating records will send them up to CloudKit If the store is NOT empty, and the database syncs (e.g. app launch), you will get the "Custom zones are not allowed in public DB" errors Once you are in this state with the ""Custom zones are not allowed in public DB" errors, changes from the device will no longer make it to iCloud However, if you make a record off-device (e.g. In the Dashboard, via the API, or from another device), it will make it down to the device. I created a feedback: FB9179204
Post not yet marked as solved
8 Replies
0 Views
As soon as i wrote that message i realised it will never work for changes to fields inside the objects - as the datasource is of type <String, NSManagedObjectID> so its obvoiusly only going to change if objects change based on their ID and nothing else. RIP.
Post not yet marked as solved
8 Replies
0 Views
DId you ever figure this out? I can only have it work for added/removed items - if their actual content changes then it doesn't report a change.
Post marked as solved
6 Replies
0 Views
I believe it's a bug - if you actually run your app it will work as expected
Post not yet marked as solved
3 Replies
0 Views
Does something like this work?.navigationBarItems(trailing: Button(action: { print("HI") }) { Text("Say hi") } )
Post not yet marked as solved
4 Replies
0 Views
Ok disabling ScreenTime in iOS12 has fixed my issue 😀
Post not yet marked as solved
4 Replies
0 Views
Weirdly, I have had 2 people try my code with their account. One has the same issue, and the other could play explicit songs just fine.
Post not yet marked as solved
4 Replies
0 Views
Done (took me a while to find - its moved to screen time but if you search for restrictions in settings the search still shows it as being in general but its not there 😀)Didn't fix it.
Post not yet marked as solved
1 Replies
0 Views
You can!The MusicKitJS library has a wrapper for basically everything the MusicKit API has - but the documentation isn't super great right now. My strategy is to call the things using MusicKitJS, then check the network tab in chrome to see the URL it hit, then look at the MusicKit documentation for the API to figure it out🕵♂https://developer.apple.com/documentation/musickitjs/musickit/apiA basic example of getting your recommendations: MusicKit.getInstance().api.recommendations().then(function(recommendations) { console.log(recommendations); });It seems to contain basically everything you get right now on the "For You" screen of Apple music.
Post not yet marked as solved
1 Replies
0 Views
Did you submit a radar for this?
Post not yet marked as solved
6 Replies
0 Views
Thank you that script worked for me as well. was having the same auth issue. Edit the script to do something like: console.log(jwtToken) on line 18 and thats the developer id you want for the player to work 😀