Let me set up the scenario.
I have two projects created identical in all facets except for Package Name and Application name. deploying to
NVIDIA SHIELD Tablet Android 7.0 (API 24)
The projects are a non altered "Android Application with Native Code – Nsight Tegra
No source or project configuration settings have been edited;
I’m running Visual Studio 2015 on Windows 10 with the latest Nsight Tegra. All SDK and NDK up to date as of today.
The scenario; I can create and run one project and deploy it successfully (AndroidNative1). When I create and run the second project AndroidNative2 (after closing fully AndroidNative1) it will build and the NVidia “Launching on Device” Dialog will appear. It will go through it’s dance of Launching Application … Done Pulling device files… Done. Starting GDB server … Error:
Cannot launch gdbserver: all options have failed.
Failed to attach: Failed to start gdbserver on the device.
Again these apk’s have two different package names and application names. There seems to still be some kind of collision between them however.
The behavior is a bit hard to understand. If I uninstall the applications and reverse the process sometimes I can get AndroidNative2 to launch and then the bad behavior is exhibited on AndroidNative1. Sometimes I get the bad behavior on Both.
If I only have one working then I can continue to uninstall it. or clean rebuild and deploy it. with no issues. but if I then go to the alternate application I get this error often not being able to return to the working one successfully.
Restarting the device has no effect on the behavior.
What am I missing?
I’m trying to learn the Tegra NSight for Visual Studio to see if it is a valid tool for some of our development.
Our development all has heavy native components and we are presently trying to evaluate tools the will help us migrate away from the command line tools.