Unity App Closes Won't Launch when VS isn't Running the Project

Unity Engine
,
1

Hey guys,

My problem is just as the title states. My Unity App will launch and close properly as long as the project is running in VS first. I can launch it in VS, exit the App on my phone and relaunch the app from my phone just fine. However, if I try to just launch the app from my phone once it’s installed, it just won’t do it. I’m fairly new to development for WP8 and it is probably something simple I’m just overlooking. Some advice would be much appreciated.

Thanks,
Kris

Edit: There are no error messages when this happens. I see the Unity splash screen for half a second and then it closes out.

2

I’d like to clarify the issue first:
when you deploy app using VS (run/debug on device), everything works fine, the app is installed properly and can be later launched on phone itself, event if it’s not connected to computer?

What is the other way you install app on your phone?

3

Sorry for the confusion. The problem is I can no longer launch the app from the phone itself once it is no longer connected to the computer.

4

Hey, did you check the log on the phone? It might shed some more light and might even contain the solution.

5

I am getting a similar problem. It’s not getting past the Unity splash screen.

Here’s what i have found. If i wipe the app from the phone,deploy to the phone, the app launches connected to VS and when connected to computer running from the phone but not connected to VS, and disconnected from computer.

If i deploy over the top of the app it works whilst connected to VS, connected to computer and running app from phone, but if I disconnect from computer it fails to load (it’s just stuck on Unity splash screen). This occurs in Maser mode. In debug/release mode it “appears” to work ok in all 3 scenarios.

Trying different things, it “appears” that I can make it work by doing the following. If I build solution from within Unity, rebuilding an existing VS project and deploy incrementally on top of existing app on phone and DONT change anything in VS project ( for example I have set ActivationPolicy=Resume in WMAppManifest.xml) then the problem will be present (excluding the DEbug/release caveat - sorry this probably sounds like incoherent rambling!). If I change the ActivationPolicy back and forth then it works with fairly certain regularity.

I’m not saying it’s anything to do with the ActivationPolicy(It will it fail on both settings as per above) it’s something to do with not modifying the VS project in some way, setting to Master and deploy. This is further backed up with deploying as Debug or Release mode first then changing to Master. Of course I may be wrong about this.

There is no error msg because it work connected to computer even if not running in VS, so I can’t provide any error messages for you.

My workflow on WP8 is to keep building from within Unity, running the resulting solution built, then finding errors, closing down VS. Make the changes in Unity and repeat. Just thinking it probably is possible to just create the VS project once then use VS as the base for making changes.

6

Hmm I may know what is up. Rebuilding the solution forces phone to reinstall the application from scratch. If you are not doing that, visual studio sometimes fails to correctly pick up project changes if you change something and deploys only part of the stuff that needs to be deployed, thus corrupting application state. I have encountered this before. The only solution I found is to “rebuild” the solution in visual studio before deploying if you changed anything (like debug->master, for example).