-
Notifications
You must be signed in to change notification settings - Fork 229
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
uses-sdk element cannot have a "tools:node" attribute #46
Comments
I use last stable Android Studio 0.8.6 and remember that there are same error with gradle tools 0.13.2 but than it was fixed just updates to 0.9.1 and gradle tools to 0.4.1 and if it works - can you notify me please? if not I try to reslve it via gradle scripts - main idea of using tools:node="replace" is to resolve merge conflicts with oter libs and make ASNE modular |
Thanks for your feedback. I've already updated to Android Studio 0.9.1 and gradle tools 0.14.1 but this doesn't solve my problem. I've also Invalidated the caches as suggested here, and this doesn't help. |
I also have the same problem (and I am the author of the suggestion mentioned above) |
I found a temporary workaround:
I'm guessing the manifest was already merged for that specific build type. |
is it possible to remove tools:node="replace" in ASNE? |
using this workaround compiles my app android.applicationVariants.all { variant -> but it slows my app down. i.e: listview doesn't scroll smoothly anymore. |
I am also with @edward-s: AS 0.9.2, Gradle 0.14.1, and Android build tools 21.1.1. @TheMedo workaround is not an option and @edward-s workaround is not an option either since I have multiple builds with different package names and references that require that to be turned on. @gorbin is removing tools:node="replace" in ASNE an option? |
Same here, is it possible to remove tools:node from ASNE without causing to much problems? |
I was in the hospital and could not keep track of the project or fix anything but for now I'm fine and very grateful to you for the issues. I am very interested in this project and will develop it further. If I remove tools:node it should break merge different libraries in project, trying to find another solution. Work on it now... I agree with @alenz316 workaround with different studios not an option - try to find another way to solve it. But hot fix until I solve it Thanks everyone for your support |
sory for my bad language
Until now, @gorbin 's ASN library work fine for me. I hope this studio android issue resolved soon, Thanks |
I remove uses-sdk and fully update all to last versions of libs and sdks |
Excellent news! |
Woohaa! Go for it! On Thu, Nov 20, 2014 at 2:29 PM, TheMedo notifications@github.com wrote:
Quentin DOMMERC |
THANK YOU! |
just released 0.3.3 version to maven - fully updated to sdk, api, plagins versions p.s. |
Seems to work fine now with 0.3.3, thanks for fixing it! |
thank you!!! |
Still have the Problem. Please Help |
updated to 0.3.3
|
@matantsu your problem is not related. You have over 65k methods in your project. Check https://developer.android.com/tools/building/multidex.html |
I still have this problem, Android Studio 1.2.2 |
I Found a solution to this problem, In AndroidManifest file -add this tag: |
@mohamed-habib, can you post some code? |
I don't understand what code exactly do you want? |
|
I've updated Android Studio to version 0.9, and gradle build tools to version 0.14, now when i try to build my application (which is using ASNE) I got this error:
Error:Execution failed for task ':app:processDebugManifest'. Manifest merger failed : uses-sdk element cannot have a "tools:node" attribute
I've searched in my code, and I'm not using tools:node="replace" anywhere, but ASNE is using in manifest (both in core and "modules").
Any idea how I can solve this problem?
The text was updated successfully, but these errors were encountered: