You can pass --enable-icon-stack-fallback-generation=disabled as a flag to the asset catalog compiler. Go to project -> Your target -> Build Settings -> Search for "Asset Catalog" -> Add the mentioned flag in Asset Catalog Other Flags. In this case versions prior to 26 will continue to use the previous app icons. However for my project this caused problems when uploading to App Store Connect apparently due to missing png icon files. This has never been a problem before and the app seems to be displayed with the correct app icons at all times. I am also using alternative app icons. I am yet to further investigate this to file a good feedback report.

It is best to submit these through https://feedbackassistant.apple.com

My request took around 4 weeks to be approved.

I finally figured this out. It's really weird but I found the issue. In the initializer of the TimelineProvider struct of the UpNextWidget(), I created a SwiftData modelContainer. Once I remove that from the initializer to the function that will need the ModelContext, it works reliably as expected. Obviously this can not be intended behavior. I filed a feedback with a sample project based on the template for Live Activities that illustrates the problem. FB17655658

Have you tried the .onOpenURL modifier? This works for me

I am not sure I exactly understood your problem. However why are you not using a background refresh of an app that fetches and uploads that data to your server. In that case you can use MusicKit and have nothing to do with tokens. Am I missing something here?

I use https://github.com/ggruen/CloudKitSyncMonitor for a similar use case and it works quite well for me.

There is no need to add a MusicKit Capability in Xcode. You only have to provide a NSAppleMusicUsageDescription in your Info.plist.

There is no need to act as a dummy switch. What you describe might be possible using Scenes in the Home app, meaning no code at all. It is definitely possible to directly adjust these devices using HomeKit (the developer kit, not the app). That will be possible on all platforms, but you might have to use Mac Catalyst.

Beta App Review is not as strict as App Review but why do you have a problem with being reviewed in the first place? Usually it takes less than 12 hours to get your app approved for TestFlight and if you do not have a malicious app you should have absolutely no problem passing the beta app review from my experience.

This looks like a bug to me. You should definitely file a bug report for that. In my app I am using musicPlayer.setQueuer(with:)You can test whether that makes a difference.

You need to infer a type manually and tell which property should match yours. MusicCatalogResourceRequest<Song>(matching: \.id, equalTo: song.id.rawValue) This is what you are looking for. Apart from that I strongly advise you to switch using IRSC (or UPC for albums) instead of the song id. The song id (or album id) can change at any time. Read the explanation here

Just a quick idea: Can you access that relationship programmatically? So if you add a button that tries to print that relationship, does that work? Currently there is a bug that @Query does not update the view after an iCloud Sync. I filed a bug report for that. FB14619787 If you can indeed access that relationship you might be able to work around that by using this package (https://github.com/ggruen/CloudKitSyncMonitor) that can update your view whenever the iCloud sync status changes.

Great that you were able to fix the problem yourself. It would be great if you could file a bug report since this does not look like correct behavior.

@SpaceMan You should use this instead: public func fetch<T>(_ descriptor: @Sendable () -> FetchDescriptor<T>) throws -> [PersistentIdentifier] { return try self.modelContext.fetchIdentifiers(descriptor()) } and you use that like: guard let loaded = try? await dataHandler.handler.fetch( { FetchDescriptor<MyModel>(predicate: #Predicate { model in model.somebool }, sortBy: [SortDescriptor(\.someKeypath)]) }) else { return }