feat(live-update): add `fetchBundles(...)` and `fetchChannels(...)` methods

[robingenz]

Plugin(s)

• Android Battery Optimization
• Android Dark Mode Support
• Android Edge-to-Edge Support
• Android Foreground Service
• App Review
• App Shortcuts
• App Update
• Asset Manager
• Audio Recorder
• Background Task
• Badge
• Bluetooth Low Energy
• Cloudinary
• Contacts
• Datetime Picker
• File Compressor
• File Opener
• File Picker
• Live Update
• Managed Configurations
• NFC
• Photo Editor
• Posthog
• Printer
• Screen Orientation
• Screenshot
• Speech Recognition
• Speech Synthesis
• Torch
• Zip

Current problem

It is not possible to receive a list of bundles and channels from Capawesome Cloud directly via the plugin. Currently, this is only possible via the Rest API.

Preferred solution

Add a fetchBundles(...) and fetchChannels(...) method.

Alternative options

No response

Additional context

No response

Before submitting

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

[felixgabler]

Hi! It looks like fetchChannels(...) shipped in 8.2.0 (#787), but fetchBundles(...) hasn't landed yet. Is it still planned?

Our use case: we use customProperties (e.g. critical=true) on bundles to force-apply important updates at startup. The problem is that fetchLatestBundle() only returns the single most recent bundle — so if we publish a critical bundle and then a non-critical one a few hours later, users who open the app after both were published never see the critical flag. The intermediate bundle's metadata is invisible.

With fetchBundles(...) (assuming it returns customProperties for each bundle), we could check whether any unapplied bundle in the chain is marked critical and force-apply accordingly.

Is this on the roadmap? Happy to provide more details on the use case if helpful. Thanks!

[robingenz]

@felixgabler Thanks for your interest! No, we don't plan to add a fetchBundles(...) method to the plugin API since there hasn't been enough demand in the community. Most customers publish a native update whenever a critical live update is needed, which means all future live updates target the new native version. In combination with our @capawesome/capacitor-app-update plugin, you can notify the user as soon as a native update is available.

That said, we will continue to monitor the demand for this feature and may consider adding it in the future. In the meantime, a possible workaround would be to store the timestamp of the last critical live update as a custom property on each bundle, along with the bundle's creation date. Your app would then store the creation date of the currently applied bundle locally and, whenever a new live update is available, compare the two dates to determine if a critical updatewas published in between.