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?
Related
I am building an Electron app in .net and using the Electron.net package and following their example web app.
But I would like to keep my .net web service running, even if the user closes the Electron window.
I'm planning to put a tray icon to allow the user to re-open the user interface if they've closed it.
But it looks like the BrowserWindow has somehow been set to terminate the application if the last window has been closed.
How can I keep it running?
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?
I am using mobilefirst for my hybrid application development (For Android, iPhone and windows phone devices). I tried with WL.App.close() but its not working for me.
Any method available for closing the Mobilefirst app?
How can we identify backbutton exit from application in Mobilefirst?
Per Google and Apple guidelines, you may not programmatically quit the application for an end-user. This is an action you must let the user do.
Hence, the WL.App.close() API no longer does that. In fact, this API method is deprecated and will be removed in a future release.
To trigger a quit of the application, you'll probably need to create a Cordova plug-in. In this plug-in you will need to cause a "silent exception" which will cause the app to crash when you choose to execute the plug-in. This way the app will quit.
Nowadays, in Android as well - tapping the Back button no longer quits the application. Rather it too will put the app in the background. This is the expected behavior.
What you could do, for Android and Windows Phone 8 is to override the Back button's default action by using WL.App.overrideBackButton and there too trigger an exception to quit the app.
Or - let the user quit the app...
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.
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.