When you switch applications or by pressing the Windows button application terminates. But on the first page of this application does not occur. In debug mode, this also happens. The application consumes 28 megabytes of memory. So the system should not terminate it.
Using Prism for windows phone and Unity 3.5 prerelease.
The crash occurs cause GetNavigationState doesn't support serialization of a parameter type which was passed to Frame.Navigate.
Related
I am building a UWP application, also i am using desktop bridge which allows the UWP app to launch a win32 application and to communicate with it, to process some data that the UWP app can't give me its result.
The usual behavior of the is that the win32 app is launched for the UWP app, it process the data and then send the response to the UWP app and then it closes.
If for some reason the win32 app opens mutiple times in row, the UWP app crashes(it disappears) when i try to reopen the app, for example while debugging, it takes me to the App.g.i.cs, and say that there is a Session state service failed exception.
For some research i saw that this exception is related to prism, but i explained the behavior above in case it will have any effect on this exception.
Is it possible to know what is the source of this exception so we may able to handle it?
I have a UWP that also contains a desktop bridge component. The UWP contains the interactive code, including handling session management (login and logout). The desktop app runs in the background - it displays no UI most of the time - but must always be running when the app's user is signed in (the UWP and desktop components share auth). If the desktop app is not running when the UWP starts, but the app is signed in, the UWP needs to start the desktop app. Similarly, whenever the UWP signs in a user, it needs to start the desktop component (if it isn't already running). Signing out a user doesn't strictly require exiting the desktop app, though it wouldn't hurt. Critically, the desktop component must not (automatically) exit when the UWP exits, so there's no guarantee on launch of the UWP whether the desktop app was launched by a previous instance (and is still running) or not.
The problem is, I can't find a way for a UWP to detect whether its desktop bridge component is already running, or to kill an already-running instance. The methods in FullTrustProcessLauncher do not return a Process object or any other way to monitor the desktop app.
How can a UWP detect if its desktop bridge component is running? If it is running, can the UWP stop the desktop bridge app?
We are developing a new Windows Store App with C# now. It is strange that the app crashed occasionally but haven't given any infomation . Now we deploy an IDE on the Surface and use it to run our code. The app crashed as the same, and the IDE didn't give any information.
So we want to know if Win8 system will kill app at some special cases ?
By the way, our all code blocks had using try-catch and we use async and await very carefully.
Most crash happend when the App access some network service.
Thank you very much!
every body!
I think there is not any systematic mechanism to make our app crash. But some bugs on the system really influence the quality of the software.
As our app, it crashed many times when using grouped GridView and when the pages enabled NavigationCachemode. After removing these features, it crashed less.
I don't have a WP7 device yet. Everything is functional in My App on a Simulator, but when my customer test it, app does not function at all. e.g. VDO is not playing.
Is there a way to get a crash log from Windows Phone 7? (like iPhone).
You can easily create your own crash report. Basically this is what you have to do:
In your App class add an handler for the UnhandledException event
inside the handler prepare a log with everything you need (stacktrace, memory allocated, etc.)
use an email composer Task to send the report.
You can also check BugSense which is a cross-platform(iPhone,Android and Windows Phone) tool that collects and analyzes crash reports from mobile apps.
Disclaimer: I have developed the WP7 plugin.
With Visual stuido 2010, it's simple to set up SL4 to debug with an out-of-browser installed app. I followed the instructions from here and everything seems to set up fine. Debugging from the browser runs the program just fine, but running from the OOB program gives a different result. After starting, the screen will go blank and then hang forever. I have some concerns that it might be because of some of the technologies that we're using.
Firstly, there's a popup that happens because we're using WCF RIA Services (formerly .NET RIA Services).
"RIA Services will fail unless the silverlight project is hosted and launched from the same web project that contains the RIA Services."
This seems to just be a warning, but I have a suspicion that this warning might be telling me that RIA Services needs to have the .web project as its startup project.
We're also using prism and the error has an odor of a Prism error too. (something loading and then not ever appearing)
Has anyone else had any issues with OOB debugging in SL4? Is anyone else OOB debugging in SL4?
Sorry it's so vague. It's a complicated mess. The only message I see is the italicized popup warning. Then the window (which was previously showing the background of our application) just goes blank
There is currently a known issue with debugging an Out of Browser Silverlight 4 application when using F5 to launch the application from within VS 2010. The question I have is whether or not the application launches without debugging (-F5 or running it from the shortcut)? In the case of using F5, a dialog typically appears with the following error dialog “Unable to start debugging. A fatal error occured. For more details, please see the Microsoft Help and Support web site. HRESULT=0x80070018” and then the application appears to hang. In this case detaching allows the process to continue and then reattaching should allow you to debug the process.
If this is completely blocking or you’re trying to debug code running at startup (like the page startup event), one possible way to get around this would be to put in a call to System.Diagnostics.Debugger.Break, start the program and then attach when dialog pops.
This can be caused by the OOBA install being older than the version you are trying to debug. Remember, Silverlight OOBAs do not automatically update themselves to the latest version of the XAP file that may be available on the server. You have to update them yourself. If you get this error and you have included the auto-update logic in your app, just bounce out of VS, run the app so it auto-updates, then go back in and debug.
Alternately, you can uninstall the app and re-install it. That will ensure you are debugging against the latest VS build.
I ran into this same issue with VS 2008 and Silverlight 3. If I got it, I just jumped out and updated the app then re-ran it in VS and had full debugging.