User Profile

Our app accesses Apple Music and the user's music library. It is installed & running fine on lots of iOS devices. Thanks to a recent release using Catalyst it's also now installed & running fine on a number of Mac's. However we've just had an error reported by one of our Mac users which I don't understand. Specifically: The app is connecting to the user's Apple Music account no problem It then asks for cloud capabilities instead of getting both musicCatalogPlayback and addToCloudMusicLibrary (as we'd normally expect) it's only getting the former. Our app requires addToCloudMusicLibrary to operate. So in the code snippet below it prints "No add to library capability": SKCloudServiceController().requestCapabilities { (cloudServiceCapability, error) in     if let error = error {         print("Error: \(error.localizedDescription)")         return     }     guard cloudServiceCapability.contains(.musicCatalogPlayback) else {         print("No music catalog playback")         return     }     guard cloudServiceCapability.contains(.addToCloudMusicLibrary) else {         print("No add to library capability")         return     }     print("Good to go") } My initial assumption was that the user had not enabled iCloud Sync, but this has clearly been enabled. What else could cause this? The Mac in question is an M1 MBP. We don't have many M1 installs so I'm somewhat concerned this could be an M1 / Catalyst issue. Thanks in advance.

Hi there.We are experiencing an issue where our App keeps getting rejected because it's returning an "SKErrorDomain error 1" whenever it calls requestUserToken during App Review. The strange thing is that it seems to run perfectly for all of our TestFlight users & developers. Code snippet here: SKCloudServiceController().requestCapabilities(completionHandler: { (cloudServiceCapability, error) in // Lots of error checking here guard cloudServiceCapability.contains(.addToCloudMusicLibrary) else { // Raise an error... return } guard cloudServiceCapability.contains(.musicCatalogPlayback) else { // Raise an error... return } let newDeveloperToken = "a developer token generated by python script" SKCloudServiceController().requestStorefrontCountryCode(completionHandler: { (countryCode, error) in // Lots more error checking here SKCloudServiceController().requestUserToken(forDeveloperToken: newDeveloperToken, completionHandler: { (token, error) in guard error == nil else { // Error: "The operation couldn't be completed. (SKErrorDomain error 1.)" gets thown here during App Review return } // Success // We never get here during App Review! }) }) })Can anyone give us a pointer on where the issue might be? I've asked App Review to check they are logged-in with an Apple Id with a valid Apple Music account, and I've double-checked that our developer token does not expire for a long period. Is there anything else that we should check on regarding our Developer token? Any ideas would be very welcome.Thanks in advance!

Hi there.I'm hoping someone can tell me the "approved" method for showing potential users my app via an App Preview.Some background: My app allows users to capture music playlists from a range of different web pages & apps. It does this via a share extension, so when the user sees a playlist they want to capture they simply "share" it with my app and it does the rest. So far, so good - the app has been live for some time and several releases.Unfortunately the latest version of my app, which includes an App Preview of the share extension in use, has just been rejected with the following message: Guideline 2.3.4 - Performance - Accurate Metadata Your app previews include content that does not sufficiently reflect the app in use. Specifically, your previews: - Show footage other than the app in use.This is entirely accurate: there is a brief view where you can see a playlist in Safari. It's there because that's how my app works - you can bring up a web page with a playlist in Safari and invoke my share extension to import the playlist. That's what the App Preview shows, and I feel it would be misleading to users if they could not see that's how it works.However I'm being rejected for showing this.Could anyone shed light on the right way to show a share extension such that it doesn't breach App Review guidelines?Thanks in advance.