I have problem with PhoneCallManager.ShowPhoneCallUI in my windows Phone 8.1 universal app. When I make this call the phone call UI appears for a moment and then entire app disappears.
It works fine in debugger. I do specify valid phone number.
I don't have much informations, but the problem should be of the suspension manager, while you are in debug mode the app never enter in suspension mode, instead when you run the app normally and you bring up the phone call UI the app enter in suspension and crash, the problem should be the fact that you pass an object to the view, only strings and serializable element are allowed to be passed from a view to another as parameter without having issue on the suspension manager.
Related
I want to write an app that just manipulates the content of it's own tile and then silently terminates.
How do I get rid of any default window and splash screen?
Thanks!
You cannot do this fully. Tapping the tile will always launch the app so there will always be a context switch even if it exits immediately.
The closest you can get is to write a Silverlight app and not include a SplashScreenImage.jpg file. When the app starts up immediately exit by calling Application.Terminate (Runtime apps always show their splash screens while loading, but splash screens are optional for Silverlight apps).
This isn't recommended and is likely to confuse your users. A better design would be to let the app launch and do something useful such as displaying more information about what is on the tile or letting the user know what changes are being made.
As Romasz says, this may not pass certification. See Windows and Windows Phone Store Policies for the certification requirements. I suspect an immediate exit with no reason given will appear as and be treated as an app crash.
I am developing windows phone 8 app, i need to make a call to specific phone number but without call confirm dialog. Is there any way to make a call to a number without call or dont call confirm dialog?
No, every call request generated using the API require user intervention due to security reasons.
phone call task is a Launcher and hence it has its own GUI.
The phone call task launches the Phone application and displays the
phone number and display name that you specify. The phone call is not
placed until the user presses the call button.
Source http://msdn.microsoft.com/library/windows/apps/hh394025(v=vs.105).aspx
I would like to launch an application using parameters provided from a push notification on Windows Phone 8.
The behaviour I wish to achieve is that as soon as the user receives the notification, the application will be launched with the parameters provided in the notification. I.e. seamlessly present the notification in a more user friendly way.
As far as I understood there are three push notification mechanisms. Toasts, Tiles and Raw.
None of them seems to be able to handle the wanted behaviour.
Toast: The message is shown even if the application hasn't been started. It does not start the application unless clicked on but seems to be closest to the target.
Tile: Message is shown if the application has been pinned. But they may be difficult to notice unless the tile is pinned fairly high on the start screen.
Raw: Works in more power states but requires the application to be running. This doesn't seem to be a match because I want the notification to be received when the application is not running. I couldn't find information about which application states where raw notifications are handled. I would prefer all.
Did I miss something in my research? If anyone has a hint of how to put an application in the foreground from a push notification (without user interaction) it would be greatly appreciated!
My first attempt was to trigger the application start using SMS but that seems to be a no go.
See my post Launch application automatically from an SMS on Windows Phone 8
You can not automatically launch an application on Windows Phone (and neither can you on iOS or Android). What you can do is provide a URI with the Push notification so the user is taken to a page with the needed information
you can not put an application in the foreground from background without user interaction.
Is it possible to create an NFC message that will create a calendar entry on the destination phone, without requiring my app to be installed on the destination phone?
For the moment, I've implemented it by using a custom protocol URI, but I'd like this to work even when the destination phone does not have my app installed. It would be even better if it could work on an Android destination.
You cannot do this on any phone if I am not mistaken. NFC messages at the end of the day are just bytes being transferred from one mobile device to another. If the destination device does not know how (and most of them do NOT have a build in handler for calendar event) to parse that message in order to open a native application what you are trying to do will not work.
Even if you get an NFC reader and read an NFC message design for that purpose and then recreate this in your application it will NOT be universal; meaning it will not work on any device, especially on different OS devices.
Again this is what I know so far. Don't take this for granted.
Have you tried to store a vcalendar item on a tag to see whether/how a phone reacts to this?
text/x-vcalendar or text/calendar
might be the right format to use for the NDEF record. See also this so question.
If this would not work, you might write an app that takes intents from such calendar data and sends it to the calendar app on the phone (however I don't know how that step would work).
My app is running on the foreground and the phone getting a incoming call. In the scenario, the phone is not raising any event to app like deactivated or closing. How do I identify my app not running ?
You app actually is still the current foreground app (so, kind of running, but audio/video is paused for obvious reasons).
You will get an Obscured event in the app, but you can't distinguish if this due to an incoming call, an incoming SMS, toast or reminder.
Here is a link to the MSDN documentation of the Obscured event you get. There is a corresponding Unobscured event you can also detect.