Im having problems getting the Reminder notification to launch my App once it's touched. Through the MSDN step by step guide and documentation found HERE, I know that, if the user does not touch any of the buttons (snooze/decline) but touches the popup itself, the Uri defined in the reminder should be opened inside the App. However, once I do that, not even the App itself is launched, let alone the specified Uri.
To make sure the problem wasn't on my App, I've created a new application and copied the exact code found on the page linked above, and while it does schedule a Reminder, once it pops up, touching it only makes it disappear, still not launching the App nor the specified Uri (which exists, yes).
I've already searched a bit around here, and even though I've found a couple of questions similar to what I'm asking (such as this one), it relates to WP 7, while Im having problems with WP 8.1.
The user in the previously mentioned question figured out by himself that one needs to have the app closed for the popup to launch it at the specified Uri. However, even doing so, nothing happens with me, both on the emulator and the device. I have even removed it from the suspended/previously used apps, but still nothing happens.
I have also found this, but nobody answered, and I don't have enough rep to comment on his question asking if he found the solution :/
I'm using VS 2013 Professional Update 3, Windows 8.1 Pro 64 bits, The Windows Phone 8.1 SDK and Emulator and a Nokia Lumia 620 with Windows Phone 8.1 on it. My apps are Windows Phone Silverlight 8.1. If anyone wants, I can link to the binaries for the test app I've built, but it's really a copy & paste from the tutorial from the first link I mentioned.
If anyone could help me on this, I'd reeeeally appreciate, because I feel like I'm missing something really small and stupid, but can't figure out what. Other than that, it just seems like a bug on WP 8.1.
Thanks in advance, and sorry if it's an already solved question, but as you can see, I tried to find the answers and couldnt...
Just wanted to say, to whoever finds him/herself struggling with this problem, that I - sort of - solved this problem.
I got in touch with a Microsoft Developer Evangelist who told me that indeed, this feature was removed from the 8.1 API. He refused to admit it was simply a bug, even though he agrees on that fact that the "Uri" property still being there is confusing. I'm not sure whether to believe him or not on this matter (I still think it's a bug), but at least I found out the problem was not me.
In the end, the only viable solution was to convert the whole project back to WP 8.0. Since Visual Studio does not allow one to do it by simply editting the project file, I had to copy all files to a new project by hand. Luckily, there were no major issues while doing so. Now the "go to URI" behaviour works just fine!
Hope it helps someone :)
Related
Since a while I am working with HoloLens2. My last OS-Versions were 10.0.18362.1005 and 10.0.19041.1109. I am developing with Unity 2019.4.7. My whole code was and still is running great on those old OS-Versions. Now I updated to OS-Version 21H1 and I have huge problems with everything including networking.
For example, my Mixed-Reality-WebRTC Pluging (from Microsoft), which only supports ARM-Architecture, does not work anymore on my new Device. The app crashes after it was successfully starting.
Another thing is, that the DevicePortal does not transmit virtual inputs. Again, on my older HoloLens2´s Virtual Input works great.
Also, even if I disable WebRTC parts of my Project, I still get an Exceptions in my Networking-System which I can´t assign to any cause. In term it is useful for you, I work with windows.Networking Library and in special with DatagramSocket.
I would be really glad if anybody could help me with this. Is OS-Version 21H1 restricted to any specific Unity- or VisualStudio Version (here currently I use 16.4.5)? Or is it Restricted to specific Networking Libraries? Thanks in advance!
Now I was able to fix the Networking Exception. The reason for that is located within my UDP-Communicator which uses DatagramSocket. Since earlier .Net.Sockets was not available at HoloLens2, now it is and I coincidentally came across this information. So I switched my implementation to .Net.Sockets which already exists in my project for editor-usage and now basic networking works fine.
Also, I was able to make WebRTC work again. With one of my Provisioning-Packages I disabled the usage of microphone for mixedReality and it seems like access to those audio-informations is mandatory for MR-WebRTC.
Unfortunately, I still have the same issues with Device Portal.This really looks like a bug.
I am trying to setup a development environment in Visual Studio Community for development with Xamarin.Forms. In order to make sure the Android Emulator was working, I followed the QuickStart Xamarin.Android tutorial found here.
When I Start Debugging with any number of Virtual Devices the output is always the same; the application does not show up, but the AVD successfully starts up and I can also successfully interact with OS; when trying the close the AVD (with the x icon on the top right) a pop-up dialog appears saying "There were Deployment Errors. Do you wish to continue? Yes\No". The frustrating part is that no matter my response there is absolutely no useful error informations, or warnings or messages for that matter. You may think this is a duplicate question but it is not. I have had problems with a similar problem in which the fix was to downgrade my Android SDK BuildTools to a version lower than 24.0. The was to circumvent an upstream bug that provided the error message: java.lang.UnsupportedClassVersionError blah blah blah. The problem here is I get NO error and my highest version Build Tools are version 23.0.3 which should be fine. Here is a pic on start-up:
AVD
Unfortunately as I am only a begginer user I am not permitted to post more links and images. Apologies for the images as links I am still only permitted to post images in this way.
Thank you for taking the time to help me out.
Hi anyone with a similar problem, this is what worked for me in this particular case. I started the AVD before starting Debugging, the application then showed up in the emulators device menu and everthing is working. I have been stuck with this problem for Five whole day trying dozens of things. Pheeeeuuuuuuw!
So far I've been unable to find an answer to my question. I might be blind, or just Googling the completely wrong words, I don't know, but here's the question.
In many apps (Both on iPhone and Android) they have these floating tips that assists the user in using the app. For instance "Touch here to open notifications", and "Touch here to access settings", etc.
Now I'm looking for a solution that would hopefully work for both iPhone, Android and Windows Phone, but an answer to any one platform would be appreciated nonetheless, as I'll presumably be able to translate it into the respective Xamarin code.
Mockup (Taken from some other thread here on SO, that was never answered)
if you want a tip floating on your view you may use PopUpWindow in android. It pretty easy to implement as well
I'm trying to use voice command service in windows phone 8.1 application, but I can't find the appropriate namespace (Windows.Phone.Speech).
Is it only available in wp8 or Silverlight ?
Thanks a lot!
I ran across this question while looking for the answer to this myself today; so hopefully this will help someone else.
Yes! It does exist in Windows Phone 8.1 (WinRT). It is now called VoiceCommandManager however, and is under Windows.Media.SpeechRecognition:
https://msdn.microsoft.com/en-us/library/windows.media.speechrecognition.voicecommandmanager.aspx
Noting also that they are deprecating this in Windows 10 (there is a note to that effect on the page), which probably accounts for why this was so hard to track down. I also found this handy sample project:
https://code.msdn.microsoft.com/windowsapps/Voice-Commands-for-Windows-2f808ac6/
I want to use DatagramSockets in a WP8 app to talk to an SSDP/UDP device (a Sony ActionCam) but I can't find the Windows.Networking DLL as it's not in any of the normal places you add references from. It does seem to live in various places on my Windows 8 machine but if I try to add it from somewhere like %Windows%/system32 it tells me it's not possible (which I guess because there's no Type Library?).
So can someone please tell me what I am missing? Is there some other SDK I need to download? I've looked all through the MSDN docs and though it mentions the namespace in plenty of detail it doesn't tell me how to find or add it for a WP8 app (typical MS).
Hope someone can help me - I'm clearly missing something obvious but I don't understand what or why.
Ok, I solved it - I have absolutely no idea why this was happening but it seems like VS2012 was the culprit. In desperation I saved the code I needed, deleted the entire solution and recreated it and now I can see the Windows namespace members.... bizarre! Also very, very annoying - I have wasted hours on this, apparently all because of some internal issue with VS2012.
Thanks for your input Tico, apologies if I wasted your time!
Just to follow up on this - I had the same issue. For me, I had to select .Net Framework 4.5 instead of 4.0. Creating a new solution in 4.0 within VS2012 wouldn't allow access to the Windows.Networking library. But 4.5 worked perfectly.
Just another idea of what might have gone wrong since i myself stumbled upon that mistake right now. Instead of a windows phone class library i added a portable class library (supporting windows phone 8 and windows store 8+ with .net 4.5). Seems like that combination doesn't support Windows.Networking