wrong APK at release-4.1?

[IzzySoft]

The APK at release-4.1 identifies as

package: name='com.onefishtwo.bbqtimer' versionCode='23' versionName='4.0'

while according to the build.gradle at that commit it should be 24 and 4.1. The output-metadata.json at the release seems to confirm it's the wrong APK:

{
  "version": 3,
  "artifactType": {
    "type": "APK",
    "kind": "Directory"
  },
  "applicationId": "com.onefishtwo.bbqtimer",
  "variantName": "release",
  "elements": [
    {
      "type": "SINGLE",
      "filters": [],
      "attributes": [],
      "versionCode": 23,
      "versionName": "4.0",
      "outputFile": "app-release.apk"
    }
  ],
  "elementType": "File"
}

It unfortunately does not state the commit the APK was built from. Could you please check, and create a new matching release (too late to replace that one now, as it has already been distributed)?

[IzzySoft]

Any word, @1fish2 ?

[1fish2]

Yes. The next app release is coming but it's a low priority.

[IzzySoft]

Thanks! Wasn't sure if you might have missed the notification 😉

[IzzySoft]

Hmpf, seems to not come back from hibernation or something. Guess blocking modules in RL? Some rough ETA yet?

[1fish2]

Bigger priorities in RL. Whoa, 15 months! The next release is proceeding in the background. At this point it needs to support Android 15 and 16, which at least brings back lock screen widgets. Also it turns out that the app's notifications didn't get through to a smartwatch because MediaStyle doesn't (undocumented). It's fixed in the MaterialDesign3 branch.

The main thing remaining is lots of testing, be it manual or getting Gemini to write tests. The latter sounds like it'd be quick but it took 3 days to build a test of enforceIntentFilter that way.

Hang in there.