Reproducible Build fails for v2026.05.01

[IzzySoft]

… due to a different versionCode – ugh?

     XML ELEM START [lineno=19, name='manifest', #attributes=7]
-      ATTR: http://schemas.android.com/apk/res/android:versionCode=8103
+      ATTR: http://schemas.android.com/apk/res/android:versionCode=10103
       ATTR: http://schemas.android.com/apk/res/android:versionName='2026.05.01'

Assuming this might be the usual Flutter bug with split-APKs, I tried building with the target platform dropped from our flutter/bin/flutter build apk --release --split-per-abi --target-platform android-arm64 – but that ended the build with

Note: Recompile with -Xlint:deprecation for details.
Running Gradle task 'assembleRelease'...                          208.6s
✓ Built build/app/outputs/flutter-apk/app-armeabi-v7a-release.apk (9.8MB)
✓ Built build/app/outputs/flutter-apk/app-arm64-v8a-release.apk (10.2MB)
Gradle build failed to produce an .apk file. It's likely that this file was generated under /home/arjun/extra/Projects/flauncher/build, but the tool couldn't find it.

Did anything in the build process change? Here's our recipe:

          - FLUTTER_VERSION="$(sed -rn 's/\s*flutter:\s\^?([0-9.]+)\s*$/\1/p' pubspec.yaml)"
          - git clone -b $FLUTTER_VERSION https://github.com/flutter/flutter
          - export PUB_CACHE=$(pwd)/.pub-cache
          - flutter/bin/flutter config --no-analytics
          - flutter/bin/flutter pub get
          - flutter/bin/flutter pub run build_runner build --delete-conflicting-outputs
          - flutter/bin/flutter build apk --release --split-per-abi

WTF… OK, dirty hack, but works:

sed -r 's/versionCode flutterVersionCode.toInteger\(\)/versionCode flutterVersionCode.toInteger() -2000/' -i android/app/build.gradle

and then add the --target-platform android-arm64 back to the flutter build command. RB now, but that's quite a dirty hack. Preferably, a clean solution can be found…

[IzzySoft]

Oh, PS, while I'm here:

! repo/com.leanbitlab.ltvL_8103.apk declares intent-filter(s): android.accessibilityservice.AccessibilityService
! repo/com.leanbitlab.ltvL_8103.apk declares sensitive permission(s): android.permission.SYSTEM_ALERT_WINDOW

Can we have an explanation on what those two are used for, for transparency?