Yes, thanks – that builds! Can you give me a ping once that PR is merged and a new release including these changes is available? For some background of my question:
At IzzyOnDroid we support [Re...
We need to adjust the recipe once manually to establish that change. Next releases then should work automatically, as the recipe will be "copied & adjusted" automatically. So yes, a one-time ping –...
> I can imagine a world where there's a json file read at build time to generate the necessary code.
That would still prevent reproducible builds then (as that JSON file might change between bui...
That doesn't help with the [listing at IzzyOnDroid](https://apt.izzysoft.de/packages/com.tasomaniac.openwith.floss), which uses the APKs provided by the developers themselves. The APK from F-Droid ...
Looks like I had success with 1.3.6 finally: adding some steps from your workflow (removing the firebase references; seems you've added those steps there in December), the diff got much smaller. Wh...
I've checked your app if its build is reproducible (see: [Reproducible bulds, special client support and more in our repo](https://android.izzysoft.de/articles/named/iod-rbs-mirrors-clients?lang=en...
At IzzyOnDroid we support [Reproducible Builds](https://reproducible-builds.org/) (see: [Reproducible Builds, special client support and more at IzzyOnDroid](https://android.izzysoft.de/articles/na...
Happy new year to you as well – and congrats! You probably already received your welcome toot: the release is RB, so with the next sync around 7 pm UTC, the green shield will be up :partying_face:
Ah, OK. Then I simply reset here and wait for the next "full release". Steps are already in the notes and applied in a few seconds, so no big deal. At least we know we're on the right track then, t...
Go ahead mark it a "proper" release – that's RB :partying_face: I've removed the directory rename, and included the `rm -rf` for the JARs – went smooth as butter!
```yaml
build:
- rm -rf _Em...
Oof: Fedora 41 would have zlib-ng instead of zlib (in addition to all the other things, like embedded paths), making RB difficult. Maybe we wait until you have building with Github actions set up. ...
> Seems to have resolved itself again I think, I see 0.6.5 on izzyondroid.
But not RB, the green shield is not up (other than on F-Droid, a failed RB at IzzyOnDroid doesn't delay/disable an upda...
Not talking about f-droid's builders (we don't use those at IzzyOnDroid). We use [rbtlog](https://github.com/obfusk/rbtlog). The setup is described in our wiki under [Verification Builder](https://...
@kelson42 forgive me, but I cannot monitor hundreds of projects. So a ping would be really appreciated. Otherwise it will simply take longer, and might include a failed build 🤷♂
> These two permissions are used to save and restore the backup files.
Thanks! Added that to the "green list" of your app. Just out of curiosity: the app only supports Android 8+ – and backups j...
I went by your workflow and use OpenJDK-17 (zulu is not possible here; but if that's the culprit, you could try switching to "temurin" – or "oracle", which is supposed to be OpenJDK but I could not...
> Yeah sure, I am making the changes in code for this.
Wonderful! If you give me a ping when that release is up, I can adjust things here before the regular daily run, processing it manually in ad...
> OwnDroid need location permission to get saved Wi-Fi list. It doesn't read user's geolocation.
Thanks! Added that to the "green list":
```yaml
android.permission.REQUEST_INSTALL_PACKAG...
> it's version is 8.10.2
Yupp, that's what `kotlin-tooling-metadata.json` said and how I [fixed the build](https://codeberg.org/IzzyOnDroid/rbtlog/src/branch/izzy/log/recipes/com.bintianqi.owndr...
> Regarding the versionCOde increment. Thank you for letting me know. I had no idea this was an issue.
You're not alone there. I see this more often than I thought, especially with Flutter proje...
That can take years, @dessalines – and until then, our builders needlessly try to verify your app and are doomed to fail. Wouldn't it be better to find a "work around" until Google fixed it? You wo...
> had to manually check the "set as latest" checkbox.
Oof? That must be a new MS invention. I cannot remember ever having had to do that, back when I had my projects here at Github (moved them a...
OK, no warnings from the scanners – except for the anti-warning:
? repo/io.suvam.dhaaga.lite_16.apk no longer carries sensitive permission(s):
android.permission.READ_MEDIA_VIDEO andr...
It seems your APKs stick with "1" as `versionCode` – which means there won't be any update notifications for existing installs, as Android would consider the new releases as "already installed":
...
Ah, a new release! But oh, it got more complicated:
```diff
-rw-r--r-- 0.0 unx 56 b- 52 defN 1981-01-01 01:01:02 05cd8676 META-INF/com/android/build/gradle/app-metadata.propertie...