You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Christian Cook (JIRA)" <ji...@apache.org> on 2015/12/09 10:09:11 UTC
[jira] [Updated] (CB-10140) Use application id instead of package
name when running
[ https://issues.apache.org/jira/browse/CB-10140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Cook updated CB-10140:
--------------------------------
Description:
I've been working on a new plugin for Cordova which will allow you to easily deploy different build types in a system lifecycle e.g. alpha, beta and store. This will allow multiple instances of the same app on your device in different states. Currently I've hit a bit of an interesting bug/issue when using this in conjunction with the run command. When the plugin operates it dynamically changes the application id depending on the state so com.test.app becomes com.test.app.alpha and so son. Because of this, when running the app from the CLI it then starts using the incorrect ID (it uses the packageName from the Android Manifest and tries to run nothing or the wrong instance).
EDIT: See the PR for a suggested fix, and if you wish to try and replicate this issue the plugin is now available here: https://github.com/CookieCookson/cordova-plugin-lifecycle
was:
I've been working on a new plugin for Cordova which will allow you to easily deploy different build types in a system lifecycle e.g. alpha, beta and store. This will allow multiple instances of the same app on your device in different states. Currently I've hit a bit of an interesting bug/issue when using this in conjunction with the run command. When the plugin operates it dynamically changes the application id depending on the state so com.test.app becomes com.test.app.alpha and so son. Because of this, when running the app from the CLI it then starts using the incorrect ID (it uses the packageName from the Android Manifest and tries to run nothing or the wrong instance).
Below I have put together a solution which solves this issue. Would somebody be able to assess this and give me your thoughts on the improvement?
https://github.com/CookieCookson/cordova-android/compare/master...CookieCookson:applicationid
> Use application id instead of package name when running
> -------------------------------------------------------
>
> Key: CB-10140
> URL: https://issues.apache.org/jira/browse/CB-10140
> Project: Apache Cordova
> Issue Type: Improvement
> Components: Android, CLI
> Reporter: Christian Cook
> Priority: Minor
>
> I've been working on a new plugin for Cordova which will allow you to easily deploy different build types in a system lifecycle e.g. alpha, beta and store. This will allow multiple instances of the same app on your device in different states. Currently I've hit a bit of an interesting bug/issue when using this in conjunction with the run command. When the plugin operates it dynamically changes the application id depending on the state so com.test.app becomes com.test.app.alpha and so son. Because of this, when running the app from the CLI it then starts using the incorrect ID (it uses the packageName from the Android Manifest and tries to run nothing or the wrong instance).
> EDIT: See the PR for a suggested fix, and if you wish to try and replicate this issue the plugin is now available here: https://github.com/CookieCookson/cordova-plugin-lifecycle
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org