Closed bryanoltman closed 2 months ago
The app also has "an extension and some native code (non plugin) on our end for some Bluetooth interactions"
I'm unable to reproduce this by creating a new Flutter project with this pubspec, so I believe the issue is not with the dependencies (or at least not solely with the dependencies).
We believe this is due to the release being created with --build-number
and --build-name
, and the patch targeting that release using --release-version
, causing the patch aab to report a different version number than the release aab. This shouldn't matter, but these numbers seem to be finding their way into the classesN.dex files.
Comparing the output of dexdump
between a release and a patch build generated in this manner:
bryanoltman@moltman ~/Desktop
⑆ diff release_classes2.dexdump patch_classes2.dexdump
1,2c1,2
< Processing 'release.aab 2/base/dex/classes2.dex'...
< Opened 'release.aab 2/base/dex/classes2.dex', DEX version '037'
---
> Processing 'patch.aab 2/base/dex/classes2.dex'...
> Opened 'patch.aab 2/base/dex/classes2.dex', DEX version '037'
63323c63323
< value : 10328
---
> value : 1
63328c63328
< value : "2024.06.18"
---
> value : "0.0.1"
When running
shorebird patch android
, Discord usermichaelgolfi
is reporting seeing an unexpected native changes warning (thread):Their pubspec.yaml file (organized for readability):