Quinn, in your post "App Groups: macOS vs iOS: Fight!", you mention that an app must meet at least one of four criteria to access an app group container without user intervention: Your app is deployed via the Mac App Store (A). Or via TestFlight when running on macOS 15.1 or later (B). Or the app group ID starts with your app’s Team ID (C). Or your app’s claim to the app group is authorised by a provisioning profile embedded in the app (D) [1]. Our app is distributed directly (Developer ID), so it doesn't meet the first two criteria. We already had the app group ID set up to match the iOS ID (without our Team ID) and changing it now would affect our users already-stored data, so criteria C isn't really an option either. That brings us to criteria D. We've added the App Groups Capability to our App ID on the Developer site and creating a Developer ID provisioning profile with this App ID. However, for some reason the App Group Capability is not included in the provisioning profile. How then do we go about satisfying criteria D ("your app’s claim to the app group is authorised by a provisioning profile embedded in the app (D)")? If this is impossible, how can we migrate our user's data away from the affected container?

We have an app in the iOS App Store named Cloud Snippets. We also have a Mac version of the app that we'd like to distribute in the Mac App Store. App Store Connect will not let us use the same name for both versions of the app (unless we do "Add Platform" to the iOS app, which we cannot because the different versions have different pricing; the Mac app is free.) App Review keeps rejecting names like "Cloud Snippets for Mac" or "Cloud Snippets (MacOS)". It doesn't make sense for us to completely change the name since the apps work together and sync data between devices/platforms. Our users want to have both versions of the app and should be able to find both under the same name. Any suggestions?