Solved: In my development debug Scheme, I had a leftover StoreKit Configuration in the Scheme Options. The fix was to set StoreKit Configuration to "None". The latent StoreKit config was masking the App Store Connect products.

New information ... I made a text change to an existing subscription product. This does show when running the released app, but does not show in the development sandbox app. I tried clearing the app cache ("DerivedData"), restarted development machine, double-checked the bundle IDs. It appears that the App Store price changes are not propagating to the sandbox environment.

Hi App Store Commerce Engineer, Thanks for responding. I have submitted an FB: FB12654744

Hi, Thanks for the suggestions .. Yes, restarted device, tried on a real device. New subs is in the same group (there is only one). I will try to file a ticket at feedbackassistant.com

Hopefully this may help ... I started with the Apple sample at: https://github.com/apple/cloudkit-sample-sharing Added SceneDelegate Setup SceneDelegate in AppDelegate and Plist Added SceneDelegate method for userDidAcceptCloudKitShareWith The method is now being called when the share link is tapped.

FWIW I am having the same problem. -- Able to send share SwiftUI + UICloudSharingController -- Receive share on iPad -- Tap share link, and app opens (!) But the App delegate method is not called. This is with Xcode 12.5, iPadOS 14.5.1

FWIW, I've am also seeing the same problem: iOS 14.3 not receiving the NSMetadataQueryDidUpdate notification. However, moving to iOS 14.4 and XCode 12.4 has helped on an iPhone device. My app on iPhone iOS 14.4 is definitely getting notifications. OTOH, the same app on iOS 14.4 on an iPad is definitely *still not* getting notifications without a local change to the cloud. If I update iCloud documents on the iPad, a notification is recieved (NSMetadataQueryDidUpdate). So, for me, the "only" thing missing is a working NSMetadataQueryDidUpdate on an iPad w/14.4.

Yes. wrong server change token used with identiical zone names. 503 went away after using correct tokens.Thanks.