Izzy

> and I can't issue a new release just for that purpose. Be welcome to ping us when you're ready to release (i.e. have the commit ready which you will...

A pointer, @puutaro: if you build from a dirty tree (like with the current release: you've committed ffbf0185148ccb6cb34b6e4c0050ad0ec1825113, then changed `versionPatch` in `build.gradle.kts`, **then built without committing your changes before**...

PS, while I'm here: ! repo/com.puutaro.commandclick_84.apk contains signature block blobs: 0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE) This can easily be avoided with a minor addition to your `build.gradle`: ```gradle android { dependenciesInfo {...

Oh, sorry to read I'm causing additional trouble there. We could simply disable RBs for a while (recipes can be set to "do not update") until things have settled on...

I should look if there's something like a "pre-tag" hook. Then I could offer that to "the forgetful". Something like: "check if versionCode(now) is bigger than versionCode(last_tag). If not, reject."...

> I will create a v1.14.1 release soon soon™ 🙊 Friendly reminder, as people already reporting to the repos (e.g. at IzzyOnDroid) assuming we missed the release… So any chance,...

Thanks @KamWithK – no complaints! As stated, just a "friendly reminder" in case it "went under" 😉 (and a "request for information" if it's still on the table 🙈)

Thanks! That went through smoothly. Will show up with the next sync then 😃

We got similar reports here at IzzyOnDroid ("errors out when attempting to download anything") with the suggestion to remove the app, so I tested it myself. On a Wilefox Swift...

> Out of the problem you said the crash when set the format to "ask" is the largest issue that I faced For me, the log said the requested format...