feat(live-update): Support downloading a specific bundle by channel and bundle ID

[bradenbiz]

Plugin(s)

• Accelerometer
• Age Signals
• Android Battery Optimization
• Android Dark Mode Support
• Android Edge-to-Edge Support
• Android Foreground Service
• App Review
• App Shortcuts
• App Update
• Apple Sign-In
• Asset Manager
• Audio Player
• Audio Recorder
• Background Task
• Badge
• Barometer
• Biometrics
• Bluetooth Low Energy
• Cloudinary
• Contacts
• Datetime Picker
• File Compressor
• File Opener
• File Picker
• Geocoder
• Google Sign-In
• libSQL
• Live Update
• Managed Configurations
• Media Session
• NFC
• OAuth
• Pedometer
• Photo Editor
• Posthog
• Purchases
• Printer
• RealtimeKit
• Secure Preferences
• Screen Orientation
• Screenshot
• Speech Recognition
• Speech Synthesis
• Share Target
• Square Mobile Payments
• SQLite
• Superwall
• Torch
• Zip

Current problem

I want to load a specific bundle from a channel and there's no way to do it. sync({ channel }) only ever downloads the latest bundle — if I want an older bundle from the same channel, it's simply not possible unless it happens to already be cached on the device from a previous sync.

Preferred solution

Add support for downloading a specific bundle by channel and bundle ID:

downloadBundle({ channel: '2.3.4-test', bundleId: 'hg78372js-23f4-5678-bh8u-12345j12d1d1' })

Requiring both ensures the bundle is looked up within the correct channel, which mirrors how bundles are organized in Capawesome Cloud.

Alternatively, add fetchBundle({ channel, bundleId }) (similar to fetchLatestBundle) that returns the metadata (including downloadUrl) for a specific bundle, so the caller can then pass it to the existing downloadBundle. This would follow the two-step pattern already established by fetchLatestBundle + downloadBundle.

Alternative options

The existing downloadBundle({ bundleId, url }) could work, but there's no way to retrieve the download URL for a specific bundle programmatically through the plugin. Getting it would require making direct HTTP calls to the Capawesome Cloud REST API outside of the plugin, which is exactly the kind of thing the plugin is supposed to abstract away.

Additional context

The use case I'm looking to fulfill with this is a debug/QA workflow where we want to load a specific known build on a device — for example, testing a feature build that isn't currently at the head of its channel, or rolling back to a specific previous bundle that one of our users is experiencing bugs on. There is currently no way to target an older bundle by ID without it already being cached locally, which it may or may not be, depending on the device being used.

Before submitting

• I have read and followed the feature request guidelines.
• I have attached links to possibly related issues and discussions.

[robingenz]

Hi there! Thanks for reaching out and sharing your use case.

Currently, we don't have a fetchBundle method because it sidesteps the core logic of Capawesome Cloud (similar to Ionic Appflow), where the goal in production is to always ensure users are on the latest version of a specific channel.

For the QA and debug workflow you described, we usually recommend creating a dedicated channel per feature or support case. You can deploy any bundle to these channels—including older ones from different branches. When combined with the fetchChannels method, your QA team can easily toggle between different features or bug reports.

If that doesn't fit your workflow: Since you already have the bundleId, the simplest workaround is to construct the download URL yourself and pass it directly to the existing downloadBundle method:

https://api.cloud.capawesome.io/v1/apps/{{appId}}/bundles/{{bundleId}}/download

This is a quick manual implementation that should solve your problem without needing a plugin update.

Because of these existing alternatives, I’m going to close this as not planned for now. Feel free to reach out if you have more questions!