Hey,
Wondering why there is a limitation for a single app to manage a created bundle?
I get the idea on face value (you don’t want one app editing another app’s bundle), but as we shift from custom admin credentials to dev app based credentials we need to effectively unbundle each product from the old credentials and bundle with the new credentials, which seems illogical. plus if there is ever an issue with the app in question, those products bundles are locked to those credentials.
I would suggest (personally), that a app is able to remove a bundle from another app, which would make this transition cleaner. making the new app the “master” of the bundle.
That limitation is documented, in the bundles docs under Limitations: once an app has assigned components to a bundle, only that app can manage them. So there is no transfer, and the practical consequence for your migration is sequencing. Unbundle with the old credentials while they still work, using productVariantRelationshipBulkUpdate with removeAllProductVariantRelationships, then re-create the bundles from the new app. The failure case you’re worried about is the real argument for that order, since components stay owned by the app that assigned them, and an app you’ve already retired can no longer release them.
Hi,
I completely understand it is documented, but i struggle to understand the purpose of locking both bundling and unbundling to a specific app