-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Build is failing while generating the framework-8.0.0.aar file #757
Comments
Hi @janpio, |
Is this reproducible in a new, plain Cordova app? A minimal reproduction repository would really help to debug and later fix this issue. More information on how to create one: https://github.com/apache/cordova-contribute/blob/master/create-reproduction.md |
Also: The image contains a reference to Gradle 6, I am not sure this is supported. Is |
Think you're misreading the output here. The reference to Gradle 6 is simply for a warning that deprecated features are used that will be removed in gradle 6. The actual gradle version used is 5.4.1, with the latest version being currently at 5.5.1. There is known issues using gradle 5.x however, as reported at #754 and #718 so perhaps this is related. |
Thanks, @breautek.
As per your suggestion, created a minimal reproduction repository/Sample in https://github.com/girigiramesh/reproduction-sample
FYI: Executed the command "brew upgrade gradle" in the terminal. It updated Gradle from 5.4.1 to 5.5.1. Used 5.5.1 version which seems the latest in both the above scenarios and getting the same errors. |
Thanks @breautek, I misread that.
I am confused with this workflow. What are you doing exactly and how? |
Hi @janpio, |
Not really, that looks like a totally vanilla Cordova Android setup. This is now relevant:
|
Hi @janpio,
|
Why are you trying to create that aar file manually outside of the usual build context of Cordova Android? |
Hi @janpio, |
I have to sound like a broken record, by why are you doing this? To support API 28 you usually would remove the old Cordova Android 7.x platform, then add the new Cordova Android 8.x and just build your app using |
Hi @janpio,
|
Why do you need the .aar? |
Hi @janpio, |
I still don't know what you are doing with that .aar 🤷♀ . But well, I tried to reproduce and failed with
|
Hi @janpio, |
Just as an FYI, the aar files for all Cordova-Android releases are also published to Bintray: https://bintray.com/cordova/maven/cordova-android/8.0.0 |
Fails with 8.0.0 for me as well. But as it is fixed in |
Thank you @dpogue. |
This was fixed in #676. As for the released contents that are on Bintray, for version 8.0.0, I manually patched to create that release. This fix came after 8.0.0 was released to npm and that is why master was fixed and not 8.0.0. |
Hi @erisu, @dpogue, |
Hi @janpio, |
No, there is no ETA for releasing this. You can always check out master and work from there if you really need this, or apply #676 manually to a fork of yours. |
Hi @janpio, |
Hi @janpio, |
Hi @janpio, |
|
Bug Report
I am faced with a problem wherein framework-8.0.0.aar file, the build is failing. However, the file is being generated and the same is building versions upto 7.1.4.
Problem
I am faced with a problem wherein framework-8.0.0.aar file, the build is failing.
What is expected to happen?
The aar file should be generated successfully.
What does actually happen?
The build fails and an error is shown.
Information
I am faced with a problem wherein framework-8.0.0.aar file, the build is failing. However, the file is being generated and the same is building versions upto 7.1.4.
Below are the steps I followed to generating the framework-8.0.0.aar file through the cordova-android repo.
Command or Code
I am faced with a problem where in framework-8.0.0.aar file, the build is failing. However, the file is being generated and the same is building versions upto 7.1.4.
Below are the steps I followed to generating the framework-8.0.0.aar file through the cordova-android repo.
Environment, Platform, Device
Mentioned above.
Version information
Checklist
The text was updated successfully, but these errors were encountered: