Reproducible Build fails for v0.5.1

[IzzySoft]

The zip ordering does not match. Could it be you've built this APK using Android Studio, with the Jetbrains JDK? In that case it would help if you could, for release builds…

• switch to a different JDK, preferably (by order): OpenJDK, Temurin, Adopt.
• build from the command line, using ./gradlew clean assembleRelease

[IzzySoft]

PS: in addition, our repo updater rejected the APK, because of…

! repo/com.prajwalch.torrentsearch_18.apk declares flag(s): usesCleartextTraffic
! com.prajwalch.torrentsearch_0.5.1.apk failed ManifestCheck; needs to be quarantined

I know this flag was already set for a while; can you please shortly outline what it is needed for, so we can put it on the "allow list" with the explanation? Thanks in advance!

[prajwalch]

The zip ordering does not match. Could it be you've built this APK using Android Studio, with the Jetbrains JDK? In that case it would help if you could, for release builds…

• switch to a different JDK, preferably (by order): OpenJDK, Temurin, Adopt.
• build from the command line, using ./gradlew clean assembleRelease

But how could that happen? I ran the cleaning task more than 5 times before starting to build and Jetbrains JDK is what I have been using from very first version.

I guess it's time to ditch AS for building the release build.

[prajwalch]

PS: in addition, our repo updater rejected the APK, because of…

! repo/com.prajwalch.torrentsearch_18.apk declares flag(s): usesCleartextTraffic
! com.prajwalch.torrentsearch_0.5.1.apk failed ManifestCheck; needs to be quarantined

I know this flag was already set for a while; can you please shortly outline what it is needed for, so we can put it on the "allow list" with the explanation? Thanks in advance!

"Used to communicate with the local Torznab providers such as Jackett and Prowlarr."

[IzzySoft]

But how could that happen?

Wish I knew. We had the same "picture" now 2 or 3 times, it was always that combination. No clue what AS does "under the hood" there.

I guess it's time to ditch AS for building the release build.

Guess so, yeah. Ideally, use something that has its "release workflow" public (that allows e.g. us to cross-check when "things happen"). Second best (and possible with a "simple build recipe" like yours): Clean builds when building locally provides you with an example script for clean builds, only needing minor adjustments (such as the path your code resides in).

That said: afraid we have to mark v0.5.1 failed, as it cannot be repaired on our end (and repair on your end, would mean a different APK than the one already distributed). The next release hopefully brings the shield up again then.

"Used to communicate with the local Torznab providers such as Jackett and Prowlarr."

Thanks! Added to the white list, APK was accepted now by our updater.

[prajwalch]

But how could that happen?

Wish I knew. We had the same "picture" now 2 or 3 times, it was always that combination. No clue what AS does "under the hood" there.

I guess it's time to ditch AS for building the release build.

Guess so, yeah. Ideally, use something that has its "release workflow" public (that allows e.g. us to cross-check when "things happen"). Second best (and possible with a "simple build recipe" like yours): Clean builds when building locally provides you with an example script for clean builds, only needing minor adjustments (such as the path your code resides in).

Not gonna deal with AS again. It's a right time to add a release workflow on GH.

That said: afraid we have to mark v0.5.1 failed, as it cannot be repaired on our end (and repair on your end, would mean a different APK than the one already distributed). The next release hopefully brings the shield up again then.

No problem with that. Let's hope that the next version/release will fix everything.

"Used to communicate with the local Torznab providers such as Jackett and Prowlarr."

Thanks! Added to the white list, APK was accepted now by our updater.

Awesome, Thanks you :)

[IzzySoft]

Not gonna deal with AS again. It's a right time to add a release workflow on GH.

👍 The link rather is about building at the command line – but yeah, I agree a GHA also makes the required steps transparent for whoever wants to build themselves 🤗

Let's hope that the next version/release will fix everything.

🤞