[BUG] flutter version missing

[IzzySoft]

App Version

1.1.8

Platform

• Android
• iOS

How you installed it

IzzyOnDroid

What happened?

You've removed the flutter-version from .github/workflows/release.yml, so we can no longer build the app – as we have no means to determine it.

What should have happened?

flutter-version should have remained present.

How to reproduce

How to fix: look at e865d57 – the removed line is crucial for our builders.

Does this happen every time?

Yes, every time

When did this start?

with this release.

Screenshots

No response

Logs

No response

[cogwheel0]

I wasn't aware, sorry about that. I just wanted it build with the latest stable channel because, I didn't want to keep bumping that. I'll fix that!

[IzzySoft]

Thanks! I just tried with the last known version, that failed to be RB. Ah, thought so, it picked the latest stable – I should have known… Trying again with 3.35.2 now.

PS: While it might be clear that this way it picks the latest one, that's not good for automation on the RB end: when the RB builds run, Flutter might have just tagged a new release, and we'd be out of sync. Even more, if someone tries to reproduce a few month later… Well, you get the idea 😉

[IzzySoft]

While we wait for the build to complete: your APK size is well beyond the per-app size limit here at IzzyOnDroid. Would you consider providing per-ABI builds, and we switch to the arm64 build then? Native libs are stored uncompressed, and each ABI makes up for about 15 MB; so dropping out the x86 + armeabi, would bring the arm64-only one back into the limit. Maybe put that on the plans for the next release?

Meanwhile: Build succeeded, is RB. Leaving this issue open for your answer on the --split-per-abi.

[cogwheel0]

Thanks! I just tried with the last known version, that failed to be RB. Ah, thought so, it picked the latest stable – I should have known… Trying again with 3.35.2 now.

PS: While it might be clear that this way it picks the latest one, that's not good for automation on the RB end: when the RB builds run, Flutter might have just tagged a new release, and we'd be out of sync. Even more, if someone tries to reproduce a few month later… Well, you get the idea 😉

Now that makes a lot of sense, thank you explanation! Youre a true ambassador of FOSS, Izzy :)

[cogwheel0]

While we wait for the build to complete: your APK size is well beyond the per-app size limit here at IzzyOnDroid. Would you consider providing per-ABI builds, and we switch to the arm64 build then? Native libs are stored uncompressed, and each ABI makes up for about 15 MB; so dropping out the x86 + armeabi, would bring the arm64-only one back into the limit. Maybe put that on the plans for the next release?

Meanwhile: Build succeeded, is RB. Leaving this issue open for your answer on the --split-per-abi.

Absolutely, the new flutter versions have something to do with it. I'll make sure to split per abi from the next releases!

[IzzySoft]

Thanks a lot! Please give me an advance notice (including the file naming), so I can prepare here before the wrong APK is being picked up. Need to do that for both then, the repo updater and the (RB) builder recipe 😉

[IzzySoft]

Btw, while I'm here: APK size is at 50 MB meanwhile, while at IzzyOnDroid we have a per-app size limit of 30 MB. Would it be possible to provide per-ABi builds? An arm64 build, having dropped the other 3, would come clearly back into range then.