Hey guys, Please I need help. I am trying to build an APK for android, and it keeps giving me the following error. I tried everything out there online, and never worked. Please help.
BUILD FAILED
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ‘:transformClassesWithJarMergingForDebug’.
ANDROID_HOME : not set
HTTP_PROXY : not set
http_proxy : not set
HTTPS_PROXY : not set
https_proxy : not set
IONIC_HTTP_PROXY : not set
PROXY : not set
proxy : not set
@Sujan I’m bit lost how to update all the pieces in the project after Ionic CLI : 3.19.0 update,
How do I update Cordova Platforms?
Thank you in advance.
Alex
Thank you @Sujan12 , does anywhere exist a “current” set of libraries that work together? Or even set of libraries the went along in a past? It is almost impossible to release or even serve projects started in September 2017. Upgrading stuff and fighting versions conflicts is now 30% of my daily routine, which actually contradicts the advantage of hybrid apps,
Edit:
Same as you always did:
This is the problem. I have never set the android version manually all the documentation uses simple ionic cordova platform add android which installs the version defined by the CLI. Meanwhile Ionic releases dozens of CLI updates (some weeks every day) but there is no hint I’m supposed to update ie Cordova Android platform or other stuff. There is no reference in the CHANGELOG, so how should I know the combinations? What is the good practice here?
I have a question for everybody. So recently angularfire2 released an update which made fetching data nit working unless u update the syntax and add the right words. Noe, what if the app is live, so we would have a completly not working app until we fix the stuff and wait for 2-3 days until the app store and google play approve the binary!!!
Ionic CLI updates have absolutely no influence on Cordova CLI or platforms. Updating Ionic CLI is 100% painless in regard to your actual code dependency versions.
If you have pinned your Cordova and other npm dependencies versions, you can just continue using them. They won’t break.
If you want to update something because you wnat a newer version or something is broken, you have to actually read the changelogs and releases of those to find out what is going on.
In your case, you came here posting with a problem. The baseline you have to do here is to update everything to newest versions to make sure your problem is not solved by this and all the debugging would be for naught.
In general: npm outdated tells you which of your dependencies are outdated.