My problem is my windows phone 8.1 app runs fine after initial install, but when the user force quits the app or the OS destroys the app it will not launch again. All I get is the splash screen and then it returns to the phone's home screen, the app must be deleted and reinstalled to be able to launch it again.
Oddly, the app will relaunch after a force quit when run on the emulator. The fail-on-launch happens only when running on a windows phone 8.1 device.
I need to be able to attach the debugger after I force quit my app so I can see what's broken when the app is launched by the user.
Related
Whenever I am starting to test an Windows Phone app (even a blank app) on emulator, I am getting error "The project needs to be deployed before it can be started". The emulator will be started & run successfully, still no luck in deploying app on emulator. Getting error DEP6100 & DEP6200.
These are the stuffs I tried till now:
Checked "deploy" option in 'Configuration Manager'.
Tried deploying Windows 10 Mobile, Windows Phone 8.1 & Windows Phone 8 blank apps on different types of emulators.
Although I am able to run apps on my device.
I am running Visual Studio Enterprise 2015 on Windows 10 Enterprise.
The Emulator is x86 based and Phone is ARM architecture. To run the app in the emulator, change the CPU to x86 in the toolbar and compile it. Now you can deploy te App to the Emulator and test it.
I faced problem like that and I fixed it by right click on project > properties > change platform target to X86.
I just started playing with Xamarin Forms, and ran into this error after following the Xamarin Forms Quickstart Guide. The error message actually said to Run the Deploy... for the project that you are trying to run. Deploying the project seems to install some Windows dependencies that might be required to run the UMP. After deploying the project, it ran without issue as a Windows Desktop app, or if you change to Device, then install emulator, as Windows Phone app.
This error was relentlessly happening to me as well, and I found out that it was because my project was saved on a SanDisk SD card. If I simply moved the entire solution to my C drive, it built without issue, but on the D drive, it would give this error.
My Windows 8.1 app only crashes when it's installed from the Windows Store on Windows 8.1. These are the different ways how I tried to install and run the app. Success means the app launched fine and showed me my first page. Fail means it crashes after showing the splash screen.
Debug the app in Windows 10: success
Start a release version from Visual Studio without debugging in Windows 10: success
Debug the app in Windows 8.1: success
Start a release version from Visual Studio without debugging in Windows 8.1: success
Remote debugging from Windows 10 to Windows 8.1: success
Remote debugging from Windows to Windows 8.1, but just start a release version from Visual Studio without debugging: success
Sideload app-packages in Windows 8.1: success
Install from Store on Windows 10: success
Install from Store on Windows 8.1: fail
I can reproduce this issue on every Windows 8.1 machine. The app just crashes a few seconds after it showed the splash screen.
I went looking in the event viewer and found an error saying that a remote procedure call failed. There's also an application error saying that combase.dll is the faulting module.
After loading the first page, the app checks if your PC has internet access. If it doesn't, it lets you know you need to check your internet connection. The app has the permission to access the internet as client.
I also configured an application-wide exception handler that catches every unhandled exception. The app then just shows an error message.
If you want to try for yourself: https://www.microsoft.com/store/apps/9wzdncrfj9d5
I am facing this weird issue with a windows 8.1 app I created.
All the other apps I have already made stay in the app stack when the phone is locked, until I close them
This app however is closed after a minute when the phone is locked, and it is not in the app stack, I have to restart it.
It is an app that consumes a webservice, so it does not consume loads of resources when the phone is locked.
When I debug it with Visual studio the app stays alive all the time.
The problem occurs on the phone, not in debug mode.
I have almost no code in the app.cs, only thing I have changed is thr start startpage.
Anyone has an idea?
I am new to windows app.Now i am create new app in vs 2012.It run perfectly in my system.How to install this app to my mobile.
First, if you want to test your app before publishing to Windows Phone Store you should have valid Developer account and developer unlocked phone. Details are here and here
To deploy app from VS2012:
Select from runnable options "Device"
Connect unlocked phone via USB
Unlock lockscreen on device - you should see home screen
Press deploy in VS2012
Enjoy your app on the phone
If you want to publish your app to Store - follow this guide
I installed Windows 8.1 RTM and installed VS2012 had a little problem while installing windows phone 8 sdk but i guess it is resolved now but still i have a weird problem.
Even i select "device" as the launch target when clicked the run button VS launches the app on the emulator not the phone. Surprisingly if i right click the project on solution explorer and select debug it this time launched app on the device.
Is there anybody faced with this kind of problem? I dont want to install everthing from scratch :)
Ok it was my fault, since the project build platform was x86 visual studio could not deploy the app to the device and hence launching the emulator. When i changed the build platform to Any CPU now it deploys my app to the device without any problem.