-
-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
F-Droid reproducible build failed #414
Comments
Can you give us some more information, like what version this happened with? |
Actually, this might be because #330 removed the unsigned release builds from repo.jellyfin.org. I'll look into it before releasing 2,3.0 :) |
The log is here. https://monitor.f-droid.org/builds/log/org.jellyfin.mobile/2030003 But there is not much information. |
I compared 2.3.0-beta.1 (last successful release on F-Droid, second beta was skipped for some reason) with 2.3.0-beta.3 (the failed build) and I don't see any significant changes that would cause the verification to fail. This makes me believe the fault is at F-Droid. The lack of useful logging in their build also doesn't help me to figure out what the problem might be. Here's hoping our next beta release just works because I'm not interested in spending hours to figuring out the problem.
|
If it's not on their end, my bet is the new signing config section. |
It shouldn't be, without the environment vars, it's a no-op on their side. However, it's possible that the default signing configuration within Gradle uses a different scheme than apksigner. Here's the relevant line in fdroidserver. |
@IzzySoft may be able to help. |
Not with reproducible builds, sorry – I'm no Android dev. |
I've published a new beta release (v2.3.0-beta.4). Let's see if F-Droid can build this one or fails again. |
Bingo! Checking the F-Droid server source code I found the culprit Doing a quick rebuild of
Reviewing apksigcopier I find 2 important details:
Comparison of v2.3.0-beta.1
META-INF/JELLYFIN.SF - apksigner
Comparison of v2.3.0-beta.3
META-INF/CERT.SF - Gradle
Missing APK Signature Scheme v3 in So in summary, if you want to continue publishing in F-Droid, it is mandatory to sign with A test run with the debug certificate using
|
Thanks @CarlosOlivo for the investigation. I didn't expect that much of a difference between Gradle signing and apksigner (I actually expected that apksigner would be used in the background). What you're saying is that the v3 signing is missing right now. I think there is an option to enable it with the Gradle signer. But that won't solve the complete issue right? |
That's right, although the option enableV3Signing can be added, the .apk header & .zip metadata are different and support by |
Ok thanks, will look into going back to apksigner. Maybe this is something @h1dden-da3m0n wants to work on. |
Fwiw, it shouldn't be necessary to change the Thanks a lot for the investigation @CarlosOlivo! |
A new beta was released today with the mentioned changes, this should fix the build in F-Droid. I'll keep this issue open until the update is available and F-Droid. |
Seems like it failed again because the hash for Gradle 7.1 is not known in the F-Droid build server:
https://monitor.f-droid.org/builds/log/org.jellyfin.mobile/2030006 |
The hash is available in the fdroidserver source (https://gitlab.com/fdroid/fdroidserver/-/blob/master/gradlew-fdroid#L169) so this probably means the F-Droid team needs to update their build server. I'm not sure if the app will be rebuild after this is done. |
Yes, the buildserver needs to be updated manully. |
Build successful!
Now we just have to wait for the publishing that will be happen in the next few hours/days |
Beta 6 is now available on f-droid! Closing the issue. |
And again today: https://gitlab.com/fdroid/fdroiddata/-/commit/ad409922be0d86c7b335652039ecf2026f3e3cc5 @nielsvanvelzen I guess this fixes it? https://gist.github.com/obfusk/61046e09cee352ae6dd109911534b12e |
Thanks @licaon-kter, I realized we didn't have the workaround after we hit release but I know how to fix it this time! We will release another version (2.5.1) soon. |
Describe the bug
Colud you please take a look? Thanks!
The text was updated successfully, but these errors were encountered: