Desktop - (which works on Catalina) - I'll give /tmp a try thank you

@Etresoft thank you - this worked perfect. I moved it to Dev and it works fine

I've submitted this as FB9314120

Thank you but that's not what I'm asking - perhaps I asked it badly. When I make a request for playlists with the term "Jazz" I would like to get back playlists from all curators not just Apple Music. This would happen to include Blue Note. The point is I wouldn't know ahead of time that Blue Note is a curator - I would like more discoverability in the APIs I could find the categories available with one query and use a returned value such as Jazz to query all playlists or curators. In fact I'd like more - but that would be a great start, Best, Daniel

Thank you - I appreciate the work you're doing with this API - it's a great demo of the power of async APIs

Downloading beta 4 right now - I just want to tell you how much I appreciate you taking the time to close the circle on this. Thank you, Daniel

Should a PreviewAsset be a PlayableMusicItemType so that it can easily be played?

That's very disappointing. I appreciate your response but Apple is encouraging people to embrace this less expensive subscription. I don't think customers will understand that this doesn't give them access to the entire library or that it would effect a third party app. If you ask them "do you have a subscription?" They will think "yes I do." And now it looks as if the lack of service is in the third party app. Given that you have just released these APIs that allow us to offer great functionality from within a Swift app, I would request that Apple reconsider this decision. I appreciate that the decision isn't yours and that you have the unfortunate task of explaining and defending a decision you didn't make - but the result is I can't go forward with my app as it will anger too many customers and they won't understand that the issue is with Apple not me.

Joe - any update on questions 2 and 3?

Joe - what are we supposed to use for playback in a Mac app? This seems like something that should be called out in an overview or intro doc.

Thanks - those two bullet points were exactly what I was asking. Perfect. Thank you

In playing further and watching past Core Data videos about migration I believe the answers are (1) We can move from an optional type to a non-optional type in our SwiftData classes if we provide a default value. (1a) No migration at all seems to be required or it is a light migration that is invisible to me (2) Since I'm using CloudKit I can't change the types from Int16 to Int as I can't remove items from the CloudKit schema. It's not a big deal as I already used a computed property to convert from the Int the app uses to the Int16 the schema requires. Swift computed properties make this wrapping of types really easy to do.

I'm seeing the same thing but only when I attempt to delete a record that is somehow corrupted