question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build error on Android with NS 4.1

See original GitHub issue

NS Core project - using 4.1.

Getting the following error during build

`Unable to apply changes on device: emulator-5554. Error is: Failed to build plugin nativescript-google-maps-sdk : Error: Command ./gradlew failed with exit code 1 Error output:

FAILURE: Build failed with an exception.

  • What went wrong: Could not resolve all files for configuration ‘:releaseCompileClasspath’.

Could not find common.jar (android.arch.core:common:1.0.0). Searched in the following locations: https://jcenter.bintray.com/android/arch/core/common/1.0.0/common-1.0.0.jar

  • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 1s `

I created a new folder structure

./app/App_Resources/Android/src/main/res/values and added the xml file there with the api key.

In the above, I had the create the src/main/res/values folder - wasn’t there before.

I also added the meta entry to AndroidManifest.xml file.

The demo program seems to store the xml file in Android/src/main/assets folder - not sure which is correct.

Also getting this error message

No manifest found in /Users/asrock/Documents/test/app/App_Resources/Android/src/main/AndroidManifest.xml

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:46 (1 by maintainers)

github_iconTop GitHub Comments

3reactions
erjdrivercommented, Jun 13, 2018

I can confirm the solution here worked.

https://github.com/NativeScript/android-runtime/issues/1081

Just made the change - removed and reinstalled the latest android.

Thanks.

2reactions
sserdyukcommented, Jun 14, 2018

I think patching the global build.gradle file is a working workaround, but I wouldn’t call it a solution. I followed up on android-runtime/issues/1081.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Android build warning Mapping new ns to old ns
I installed Android Studio Arctic Fox (2020.3.1) and i started getting that same error on vscode! Mapping new ns to old ns blah...
Read more >
[Solved] Mapping new ns to old ns Flutter [Solved] - YouTube
[Solved] Build Warning : Mapping new ns to old ns.Flutter gradle error fix. ... How to Speed Up Android Studio? | GeeksforGeeks.
Read more >
Question - Gradle build error after import Unity IAP 4.1.2
all external tool is use on unity recommand. This is error warning show to me build error com.android.build.gradle.internal.tasks.
Read more >
Known issues with Android Studio and Android Gradle Plugin
If Studio doesn't start after an upgrade, the problem may be due to an invalid Android Studio configuration imported from a previous version...
Read more >
Android Platform Guide - Apache Cordova
As of Cordova-Android 6.4.0, Gradle is now required to be installed to build Android. When installing on Windows, you need to add Gradle...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found