Bryan Oltman

It looks like there are a few different issues at play here. Please correct me if I'm misunderstanding any of these. 1. https://github.com/flutter/flutter/issues/105977 seems to suggest that the app itself...

Was able to reproduce this locally. After looking through our CLI code, nothing is jumping out at me as obviously wrong. I'm going to poke around in our updater code...

It appears as though the hash of the `libapp.so` on my machine is different than what is ending up on the device: My machine: ``` bryanoltman@moltman ~/shorebirdtech/samples/add_to_app/my_flutter_module/build/host/outputs/repo/com/example/my_flutter_module/flutter_release/1.0/flutter_release-1.0/jni/arm64-v8a (main) ✗ ⑆...

 The differences between the two seem to be small and isolated to the end of the file.

 The string table appears to be different as well

On a lark, I tried reproducing with an older version of Flutter (3.22.3), and the issue reproduces there as well.

### Workaround **Setting the project's `targetSdk` to 33 in the app's build.gradle resolves this issue.** Obviously, we should support newer versions of android as well, and Flutter seems to have...

This should be fixed by updating your app's build.gradle like so: ```groovy buildTypes { release { // ... // Add this line packaging.jniLibs.keepDebugSymbols.add("**/libapp.so") } } ``` Please reopen if this...

This will work if you move `--target-platform android-arm64` to before the `--`, so: `shorebird release android --artifact apk --flutter-version 3.22.3 --target-platform android-arm64 -- --obfuscate --split-debug-info build/debugInfo --dart-define=isProduction=true --dart-define=onlyBuildArm64=true` We should...

Reopening so we don't forget to fix the issue of failing to recognize `--target-platforms` when passed after `--`