Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug(live-update): reset to the default bundle if the sync has not found a bundle #272

Open
4 of 24 tasks
robingenz opened this issue Aug 26, 2024 · 0 comments · May be fixed by #281
Open
4 of 24 tasks

bug(live-update): reset to the default bundle if the sync has not found a bundle #272

robingenz opened this issue Aug 26, 2024 · 0 comments · May be fixed by #281
Labels
breaking change Breaking change bug/fix Something isn't working package: live-update
Milestone

Comments

@robingenz
Copy link
Member

Plugin(s)

  • Android Foreground Service
  • Android Battery Optimization
  • App Update
  • Background Task
  • Badge
  • Bluetooth Low Energy
  • Cloudinary
  • Datetime Picker
  • File Compressor
  • File Opener
  • File Picker
  • Live Update
  • Managed Configurations
  • NFC
  • Photo Editor
  • Printer
  • Screen Orientation
  • Zip

Version

6.3.0

Platform(s)

  • Android
  • iOS
  • Web

Current behavior

Scenario:

  1. new Live Update is published (there are no other Live Updates in this channel, it is the only one)
  2. app synchronizes and downloads live update
  3. new live update is deleted again ( e.g. via the Capawesome Cloud Console)
  4. app synchronizes, finds no update and changes nothing

Expected behavior

Scenario:

  1. new Live Update is published (there are no other Live Updates in this channel, it is the only one)
  2. app synchronizes and downloads live update
  3. new live update is deleted again ( e.g. via the Capawesome Cloud Console)
  4. app synchronizes, finds no update and performs a rollback to the default bundle

A temporary workaround is to publish the default bundle as a live update in order to perform a “reset”.

Attention: A reset should only be performed if the server returns a 404 Not Found and not, for example, in the event of an internal server error.

Reproduction

Steps to reproduce

Other information

No response

Capacitor doctor

Before submitting

  • I have read and followed the bug report guidelines.
  • I have attached links to possibly related issues and discussions.
  • I understand that incomplete issues (e.g. without reproduction) are closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change Breaking change bug/fix Something isn't working package: live-update
Projects
None yet
1 participant