Hi Jaycee. That happens when using the stock Flutter engine (e.g. flutter run, flutter build) rather than Shorebird's e.g. shorebird preview
#No Shorebird Engine
dapper rapids
carmine root
The Shorebird Engine is only available in release mode when running a release that was generated by shorebird release <platform>
fast ingot
Oh, can i be able to develop and fix bugs while in that mode @dapper rapids and @carmine root
dapper rapids
Shorebird only works in release mode. Where as typical Flutter development is done in Debug mode. flutter run runs flutter in debug mode, where you have hot reload.
fast ingot
So basically, i can develop and only test when i have released a patch to shorebird's console huh ? @dapper rapids
dapper rapids
What are you attempting to develop/test?
(It's very possible there are changes we should make, but I'm not sure I understand what the context is yet.)
fast ingot
So i have a UI prompt to detect to user when a patch is available, so i am using the shorebirds package, i want to test that the UI is been triggered only when there is a patch update.
dapper rapids
shorebird preview should work for that.
If you don't want to make a real patch, you can also make a fake copy of package:shorebird_code_push for your code.
Which doesn't actually talk to our engine/servers.
wide sleet
https://docs.shorebird.dev/guides/staging-patches/ might be worth a read too (it walks you through creating a patch for testing without releasing it to users)
dapper rapids
package:shorebird_code_push is tiny. Doesn't really do much other than talk to our engine: https://github.com/shorebirdtech/updater/blob/main/shorebird_code_push/lib/src/shorebird_code_push_noop.dart
fast ingot
Also, is there a way to get a progress when downloading progress the patch ?
fast ingot
Alright thank you so much, let me give all this a try and i will get back if any more concerns. 😊😊😊