F-Droid build failed
See original GitHub issueFAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'CovidCertificate'.
> Could not resolve all artifacts for configuration ':classpath'.
> Could not resolve ch.ubique.gradle:ubdiag-android:7.0.2.
Required by:
project :
> No matching variant of ch.ubique.gradle:ubdiag-android:7.0.2 was found. The consumer was configured to find a runtime of a library compatible with Java 8, packaged as a jar, and its dependencies declared externally, as well as attribute 'org.gradle.plugin.api-version' with value '7.0.2' but:
- Variant 'apiElements' capability ch.ubique.gradle:ubdiag-android:7.0.2 declares a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares an API of a component compatible with Java 11 and the consumer needed a runtime of a component compatible with Java 8
- Other compatible attribute:
- Doesn't say anything about org.gradle.plugin.api-version (required '7.0.2')
- Variant 'runtimeElements' capability ch.ubique.gradle:ubdiag-android:7.0.2 declares a runtime of a library, packaged as a jar, and its dependencies declared externally:
- Incompatible because this component declares a component compatible with Java 11 and the consumer needed a component compatible with Java 8
- Other compatible attribute:
- Doesn't say anything about org.gradle.plugin.api-version (required '7.0.2')
Could you please take a look? Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Fdroid build fails when adding a new app
It seems Proguard is failing, but the build works fine during my test. The pipeline is stuck at the end of the log,...
Read more >The Life - Build failed - Apps - F-Droid Forum
Please check The Life in F-Droid build status. The build failed but I was able to compile and publish on Google Store and...
Read more >Build log for failing build - Apps - F-Droid Forum
The latest build of my app failed, but I cannot find the build log to analyze the issue. Metadata here (I see that...
Read more >FDroid build error - pip3 command not found
Hi, started today, I have a build error. The same app with the same configuration yesterday was built successfully.
Read more >Could not build app...: Failed to find any output apks
Hello, I have installed a local fdroid server and can build my app through the metadata .yml file. After building the log has...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks again @linsui for merging my MR with lightning speed!
I’ll track bringing F-Droid back into the main release (instead of separate releases) in #304.
Here’s a status update, comparing v2.6.1 the official and F-Droid’s CI builds:
diffoscope
andapksigcopier compare --unsigned
don’t verify it. However, with our simple script the two APKs verify. Python abstracts away the unzipping, thus all the files contained in the APK/ZIP seem to be reproducible, but the ZIP metadata isn’t.The F-Droid docs mention 2 potential culprits. However opting out from zipflinger is deprecated and will be removed from Android Gradle Plugin 8.0, and for “ZIP entry info” it describes only the problem not a potential solution. We’ll continue to look into it.