-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bump AGP #98
Bump AGP #98
Conversation
Tagged 1.7.16+106 for fdroid build |
Why is this reverted? https://monitor.f-droid.org/builds/log/com.jithware.brethap/108#site-footer |
This change: https://github.com/jithware/brethap/pull/98/files causes this error: https://gitlab.com/fdroid/fdroiddata/-/jobs/4171315412#L1270 This reversion: e4633cb lead to a succesful build: https://gitlab.com/jithware/fdroiddata/-/pipelines/848428435 This file https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.jithware.brethap.yml should look like: https://gitlab.com/jithware/fdroiddata/-/blob/62740be33895aad739139fafb2a2f26598e1b6b1/metadata/com.jithware.brethap.yml I believe the issue is with the |
Referencing https://f-droid.org/docs/Build_Metadata_Reference/#build_prebuild
|
Ok, so when do you scan the deps if they get pulled only in |
Scans in the past occurred during the build job. An example scan detection occurred when I added wear os support to brethap. I had to create a separate fdroid branch for fdroid builds which removes gms. See #60 |
Those are at the end of a build, for the APK, and only in the Gitlab CI (for now). It's not certain that all pulled autoupdates are built by the CI or that a contributor reaches the failed CI job and disables it in time. |
Other Flutter apps can be scanned (https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/de.jbservices.nc_passwords_app.yml#L151) and have a newer AGP (https://gitlab.com/joleaf/nc-passwords-app/-/merge_requests/110) |
Yes and no That CI builds multiple apps, in the same VM, so if one installs Java 17 then all the other apps that follow it will get build with that... Hence my bet is that your cause and effect line of thinking is wrong. :) As 104 built just fine with the AGP changes: https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/com.jithware.brethap.yml?ref_type=heads#L764 right: https://f-droid.org/packages/com.jithware.brethap/ ? |
Ok got it. It's actually my fault. I myself forgot that "That CI builds multiple apps, in the same VM, so if one installs Java 17 then all the other apps that follow it will get build with that..." Then again, since I have no domain knowledge, the error was unknown to me, and I've put the burden on you @jithware and I've confused you too. Locally, I've build 106 now, and builds fine. I've added Java17 afterwards, and it failed as the CI did. So, please put back the AGP fix and we'll reenable 108 and carry on :) |
108 builds fine too, hence: https://gitlab.com/fdroid/fdroiddata/-/commit/0ee46a0bf64af83d2fa22af87b2c4f35155f2bad |
https://issuetracker.google.com/issues/184872412 This is an issue of AGP 4.1. Updating AGP to 4.2 or above should fix it.