I am in the finishing staging of creating my first Window Phone 8 application. I am using MVVMCross as the MVVM framework for the application. The application is running great in debug mode on both the simulator and my connected phone. The issue I am having is the application will not run on my phone unless it's attached via debugging. When I click on the application on the phone it simply flashes but never launches the application.
Some additional information after using Crittercism to catch the exception:
0 at Cirrious.CrossCore.Mvx.ResolveTService
1 at Mobile.Contacts.Phone.App.b__0()
After further review I realized that I had the following setup code inside
if (System.Diagnostics.Debugger.IsAttached)
var setup = new Setup(RootFrame);
setup.Initialize();
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.
I am able to generate & install windows phone build in my Microsoft Lumia 640. Its running on Windows OS 8.1.
But as soon as I run application generated by CN1 build server, it gives error
An internal application error occurred: java.lang.RuntimeException Unsupported operation as per below screen shot.
For a testing purpose I created new CN1 Project and without changing any code / theme.res I just sent windows phone build and it ended up with the same error.
Unfortunately I didnt get any log output from windows phone, as it doesnt support Logcat like Android. Also I tried to grab Isolated Storage by WP Power Tools but there was nothing in it.
Anyone faced / facing this in Codename One windows phone build ?
The Windows Phone port is the least mature of the Codename One ports having gone thru 3 rewrites due to changes from Microsoft.
We are now debating the 4th rewrite, in the meantime some community members did their own port which should be more complete:
https://github.com/Pmovil/CN1WindowsPort
So as the short answer I suggest using that. For an explanation on how we got here read on.
The reason we didn't already start with the 4th port was Microsofts project astoria that they suddenly (might have) canceled. We were relying on this project for future Windows Phone support but now that its status is unclear we are in a bind.
We also have the JavaScript port & the Windows desktop port as options for targeting windows phone alleviating some of the problem.
If MS cancels the project for good we'll dedicate the resources for a complete rewrite of the port, but that will take time. However, we don't want to start off on such a huge effort and suddenly be faced with a huge shortcut of Android compatibility.
I have a Windows 10 Desktop application that needs to use a Windows Runtime API.
Solutions I tried:
Enabling Windows Runtime libraries from within my Windows Desktop application – the API was available but failed;
using the API in a Windows Runtime background task. There I have not found a reliable trigger so far. The best would be to trigger the background task from my Windows Desktop application.
start the Windows Runtime App from Desktop application using the IApplicationActivationManager – works fine, but the suddenly popup of an screen that disappears after few seconds will annoy the customer;
For solution 2., Is there a way to trigger a Windows Runtime background task from my Desktop app?
Issue solved by using AppServices, see https://msdn.microsoft.com/de-de/library/windows.applicationmodel.appservice.aspx
I'm facing a weird problem. When I'm trying to debug my app on Windows Phone Emulator I'm getting this error:
Deployment failed because no Windows Phone was detected. Make sure a phone is connected and powered on.
However Emulator is launched, the app is deployed correctly and I'm able to debug it without any problems. I'm writing this question because this error is a bit annoying. I'm using the same settings on another machine and everything works fine there.
I'm using Visual Studio 2013 Ultimate / Win 8.1 with settings like below:
I found a problem. I have 3 Windows Phone projects, one of them (which was in fact not marked as a startup one) was targeting the physical device, and that caused the problem. Problem was solved by switching Target device in project properties -> Debug to emulator.
I have a desktop application created with TideSDK, I need this application to launch at windows startup, but can't find how, I mean, when the application is installed or launched by first time, I want it to setup to launch with windows startup. If someone has worked on it, it will be very helpful.
Thanks.
This is currently not a function. Please create a github todo for a feature request.