Has anyone gotten two or more CoronaViewer builds (two different projects) running on one device? I’ve been testing on Android and the first install runs like a charm, but when I try to run the second after install, my Nexus 4 throws a java.lang error and quits the app. If I uninstall the first and then run the second (and only) CoronaViewer build, it works fine.
I assume this is architecture related but if anyone has been able to get two running, or figured out a nice method to sandbox the installed builds, I’d be much obliged for the tip. Thanks muchly!
The reason is because the plugin has a dropbox id associated with it. Even if you build a second apk, they’re still using the same dropbox id which is why it doesn’t work.
Sign in using credentials for account I want to hook up to.
Run.
What this gives me:
Each of my clients has CoronaViewer on their Android device hooked to a separate drop box account so they can’t see each-other’s apps.
I can switch between accounts at will (have to wait for sync) and work on that app.
I hope this makes sense.
One more tidbit. If you want multiple dropbox accounts and if you use gmail, the easiest way to do that is to create new accounts using your primary e-mail account + something.
Thanks again for the tip above Ed, much appreciated. To expand on this, though, how do you handle multiple/varied build.settings/config.lua files and variables? Do you just have a if/then statement in your config.lua set to listen to a package name or a remote variable, or do you include everything from each project in your CoronaViewer build.settings and config.lua files? Love to hear your thoughts. Thanks!
I haven’t worked out a good system for that yet, but for the most part I only have to deal with Landscape vs Portrait issues (as specified in build.settings). Almost all my projects use the same base config.lua settings (i.e. I don’t customize them till the end).
Having said that, I have two builds of the APK one in landscape and one in portrait. If I’m using one and need the other, I simply uninstall and install the right one using ADB.
The reason is because the plugin has a dropbox id associated with it. Even if you build a second apk, they’re still using the same dropbox id which is why it doesn’t work.
Sign in using credentials for account I want to hook up to.
Run.
What this gives me:
Each of my clients has CoronaViewer on their Android device hooked to a separate drop box account so they can’t see each-other’s apps.
I can switch between accounts at will (have to wait for sync) and work on that app.
I hope this makes sense.
One more tidbit. If you want multiple dropbox accounts and if you use gmail, the easiest way to do that is to create new accounts using your primary e-mail account + something.
Thanks again for the tip above Ed, much appreciated. To expand on this, though, how do you handle multiple/varied build.settings/config.lua files and variables? Do you just have a if/then statement in your config.lua set to listen to a package name or a remote variable, or do you include everything from each project in your CoronaViewer build.settings and config.lua files? Love to hear your thoughts. Thanks!
I haven’t worked out a good system for that yet, but for the most part I only have to deal with Landscape vs Portrait issues (as specified in build.settings). Almost all my projects use the same base config.lua settings (i.e. I don’t customize them till the end).
Having said that, I have two builds of the APK one in landscape and one in portrait. If I’m using one and need the other, I simply uninstall and install the right one using ADB.
It looks like CoronaViewer has been silently updated and is now supporting multiple projects.
It is not a solution for the multiple client testing workflow that Ed explained here but it helps a lot on self-based development with a single dropbox account (tested only on iOS).
It looks like CoronaViewer has been silently updated and is now supporting multiple projects.
It is not a solution for the multiple client testing workflow that Ed explained here but it helps a lot on self-based development with a single dropbox account (tested only on iOS).
