-
Notifications
You must be signed in to change notification settings - Fork 342
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
Migrate to latest Android SDK, AGP and protobuf plugin #763
Conversation
* Bumps to Dart 2.17 minimum and upgrades melos to 3.1.0 * Update root pubspec.yaml with the correct workspace name Co-authored-by: Taym Haddadi <[email protected]> * add missing underscore --------- Co-authored-by: Taym Haddadi <[email protected]>
@Taym95 the build failed but I can not see the logs; please could you invite me to code magic so that I can ? |
I will invite you: Welcome to Gradle 8.0! For more details see https://docs.gradle.org/8.0/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) FAILURE: Build failed with an exception.
BUILD FAILED in 33s Build failed :| |
You need to set JAVA version in:
|
@Taym95 I created a personal codemagic account and the build runs through - wondering what the issue is here? |
Still same issues; `
|
@Taym95 I am not part of the ble team anymore in codemagic. @werediver is admin he can add him. I personally think we should make the build results available public if possible, else maybe we need to consider a different CI |
Is there a world in which you'd accept a PR to switch to GitHub actions altogether? |
@Taym95 You are the owned of the team, so you should have all the rights. Regardless, the fix is explained above. @ened can implement the fix without being a member of that Codemagic team, it's just a YAML-file change (the file is in the repo, "codemagic.yaml"). |
Codemagic seems to use "codemagic.yaml" from the main branch when building a p/r. The configuration should be updated in a separate p/r. @Taym95 If you're willing, you may be in a better position updating Codemagic configuration, because you can see all the CI stuff. |
@werediver This won't work - the gradle system in use currently is not compatible with Java19. This will yield class file errors like:
My suggestion is to merge this PR now (as mentioned I tested on. my personal code magic account and built the branch directly). If things are not right, you can always revert. |
Any progress on this? We need protobuf updated to update other packages. |
@ened can you update the java runtime to 17?
|
any updates? |
@@ -1,4 +0,0 @@ | |||
org.gradle.jvmargs=-Xmx3072m |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct this file is removed? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really. It should stay.
@@ -1,6 +0,0 @@ | |||
#Wed Sep 29 14:33:41 CEST 2021 | |||
distributionBase=GRADLE_USER_HOME |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it correct this file (also) is removed? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, should be there to let devs of the package specify which Gradle wrapper version to use.
Any update on this? |
@ened do you need help with the last remarks. I really would like to integrate it so we are compliant to AGP8 and new protobuf |
Any update on this merge request? |
@Taym95 @werediver Currently, |
This was merged with #830 |
fixes #630
fixes #761
closes #754