#Failing Shorebird preview on iOS

1 messages · Page 1 of 1 (latest)

chilly walrus
chilly walrus
#

shorebird preview ios --flavor dev works fine. Happening only with the prod flavor although runs fine with flutter run --flavor prod

chilly walrus
#

Is it compulsory to use the shorebird preview after release ? Cant I just run the app with that flavor I think both will works the same ?Does this mean I have to run shorebird preview atleast once after making the release ?

image.png
chilly walrus
#

Because this is the step I followed and it didnt work.

My Flutter App have two flavors
For Android:
appname (i.e prod flavor, just name is of company instead of prod etc)
dev

For iOS:
prod
dev

I did this

  1. Created the shorebird release

shorebird release android --flavor appname --target prod.dart (this file set the URL to prod) -> Successfully created I can see on the console

For iOS:

shorebird release ios --flavor prod --target prod.dart -> Successfully created

Then I ran the app

flutter run --flavor=prod --target= prod.dart --release -> for iOS
flutter run --flavor=appname --target= prod.dart --release -> for Andorid
Both installed successfully.

Made the change in the code but did not commit.
Made the patch

shorebird patch ios --flavor=prod --target=prod.dart --release-version= versionNo
shorebird patch android --flavor=appname --target=prod.dart --release-version= versionNo

Patch created Successfully I can see in the console.

As apps are already installed in the android and iOS , ran the apps multiple times to see if they got the change but they didnt.
Then commited the code and made patch again but and open the apps again on devices but still no change.
Now I am going to run the preview command and will make the patch again with the new changes but will not run the preview command this time to see if i got the changes or not.

chilly walrus
#

but running preview for android gives this
shorebird preview --app-id dbf7e16d-2131-4152-b69f-2a9f8574a54d
✓ Fetching releases
Which release would you like to preview? 3.0.99+509
✓ Using production track (1.7s)
✓ Extracting metadata (1.0s)
✓ Building apks (14.7s)
✗ Exception: Failed to install apks: The APKs have been extracted in the directory: /var/folders/qz/h9vy0xk90gs7n9790wzwdkk40000gn/T/13503231284367788971
[BT:1.15.6] Error: Installation of the app failed.
com.android.tools.build.bundletool.model.exceptions.CommandExecutionException: Installation of the app failed.
at com.android.tools.build.bundletool.model.exceptions.InternalExceptionBuilder.build(InternalExceptionBuilder.java:57)
at com.android.tools.build.bundletool.device.DdmlibDevice.installApks(DdmlibDevice.java:196)
at com.android.tools.build.bundletool.commands.InstallApksCommand.lambda$execute$2(InstallApksCommand.java:236)
at com.android.tools.build.bundletool.device.AdbRunner.run(AdbRunner.java:81)
at com.android.tools.build.bundletool.device.AdbRunner.run(AdbRunner.java:43)
at com.android.tools.build.bundletool.commands.InstallApksCommand.execute(InstallApksCommand.java:236)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:117)
at com.android.tools.build.bundletool.BundleToolMain.main(BundleToolMain.java:55)
Caused by: com.android.ddmlib.InstallException: Failed to commit install session 1548831872 with command cmd package install-commit 1548831872. Error: INSTALL_FAILED_UPDATE_INCOMPATIBLE: Existing package de.companyname.appname signatures do not match newer version; ignoring!
at com.android.ddmlib.SplitApkInstallerBase.installCommit(SplitApkInstallerBase.java:99)
at com.android.ddmlib.SplitApkInstaller.install(SplitApkInstaller.java:85)
at com.android.ddmlib.internal.DeviceImpl.installPackages(DeviceImpl.java:1166)
at com.android.tools.build.bundletool.device.DdmlibDevice.installApks(DdmlibDevice.java:180)
.