Skip to content

Android package name mismatch issues #2187

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

Closed
bradmartin opened this issue Nov 1, 2016 · 1 comment
Closed

Android package name mismatch issues #2187

bradmartin opened this issue Nov 1, 2016 · 1 comment

Comments

@bradmartin
Copy link

This is kind of difficult to explain, but here is what I did and couldn't figure it out for a couple hours until it dawned on me what I did couple days ago.

I was running livesync, all was going well and then I started to prep for releasing the app so I changed the package name in the package.json, and I forgot to change it in the app.gradle located in app_resources/android. I had forgotten all about app.gradle that I set the package name there weeks ago when I started the app. So it's value didn't match what the package.json value for the app was. So I did my build, started to livesync and the CLI synced everything but the app was not launching (obvious now) but it threw me off for a while.

You all will know better than I on maybe some informational message to the user about this when the CLI is running, most people won't remember to track that down cause they probably rarely touch app.gradle. Curious to hear what you all think, if you need more info let me know.

@dtopuzov
Copy link
Contributor

dtopuzov commented Aug 2, 2017

Looks to be duplicate of #2825.
Warning message will be added with NativeScript/android#810

@dtopuzov dtopuzov marked this as a duplicate of #2825 Aug 2, 2017
@dtopuzov dtopuzov closed this as completed Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants