I am suffering from a problem trying to open the Application Deployment tool. It always gives me this error when I try to open the program:
Exception from HRESULT 0x89721200
PS: The Windows Phone developer registration cannot find my device and shows the
IpOverUsbSvc error.
How do I fix the issue?
This error can occur when the SDK's language is different to your system's language format. Try changing your system's language or else reinstalling the SDK with the same language.
First, your operating system display language, your SDK and windows Phone must have the same language.
Second, check: Are the date and time set correctly on the phone? In SETTINGS | date + time, turn off the Set automatically setting and then retry registration.
If the registration succeeds, and you have a certificate error or anything wrong then download the Preview for Developers in your phone and unlock it.
Related
I am using the webusb API in Google Chrome to try to connect a device to the browser. It worked with webserial API, but I am having trouble getting it to work with webusb API.
I am using HTTPS (Github pages)
I enabled #new-usb-backend for my browser
I can open the device and select configuration, but device.claimInterface(0) is not working (and I can confirm that 0 is an interface number).
None of the two interfaces this device has seems to be claimed
The error I get looking at chrome://device-log is
Failed to claim interface: Access denied (insufficient permissions)
I'm not sure where to go from here. I would appreciate some help.
Thank you.
device.claimInterface(1) worked. I heard somewhere mac automatically claims interfaces. Perhaps the first interface was claimed, although the api indicated otherwise. Anyhow, something about the second interface worked that didn't work in the first.
That error message indicates that there is either an existing driver that has claimed the interface or (Windows only) the WinUSB driver hasn't attached to the interface in order to enable applications like your browser to claim it. On Windows you can use the Zadig tool to force Windows to change the drivers being used for a USB device.
If the device can be opened using the Web Serial API then that indicates that the operating system has already loaded a serial driver for the device and so it has claimed at least some of the device's interfaces.
Why, if the Web Serial API works to connect to your device, are you trying to connect to it with the WebUSB API instead? Are you now on a different operating system which doesn't provide a USB serial driver compatible with the device?
How can we log exceptions and error for windows Phone8.0 app
I also want a mechanism to delete the logs after a period of time
Is there a method other than ISO to log error
thanks in advance
Write them to files in isolated storage. You can write code to iterate over the file system to clean them up. If this is just for testing use Windows Phone Power Tools to manually remove logs.
An alternative is to build a logging service and have your devices connect and write to it when they have a data connection.
we have a windows 8.1 app in the windows store that sometimes crashes or hangs and we are unable to receive reports about hangs and crashs reported by the user via the store.
Collecting of telemetriy data is enabled in the store like mentioned in this MSDN-Article(http://msdn.microsoft.com/en-us/library/windows/apps/hh967787.aspx).
So I did a crash of the app by myself, took a look in the WER-ReportArchive(%localappdata%\Microsoft\Windows\Windows Error Reporting) and found a .cab & .wer-file. So I think the report was sended to microsoft, but theres still no crash or hang documented in the Dashboard of the App Store.
I tried to get a crashdump via Windows Error Reporting - LocalDumps (msdn.microsoft.com/en-us/library/ bb787181%28VS.85%29.aspx), but this dump is only generated when an error occurs.
In my case mostly the app just hangs!
I also tried to configure Windows Error Report - Registry Entries (http://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx), but it seems most of the entries are just ignored.
I noticed WER is creating a dump-file of AppHangs as well, before sending the data to Microsoft (memory.hdmp in ReportQueue). But this files are deleted immediately after sending.
Does somebody know a way to get memory dumps and further information for AppHangs as well?
Thanks in Advance.
I think you could use the posibility of Just-In-Time or postmortem debugging via setting registry key for AeDebug, if you can create the crash.
Have a look at:
Improving apps with Quality reports
https://blogs.msdn.microsoft.com/windowsstore/2012/06/27/improving-apps-with-quality-reports/
Debugging a Windows 8.1 Store App Crash Dump
https://blogs.msdn.microsoft.com/ntdebugging/2014/01/13/debugging-a-windows-8-1-store-app-crash-dump/
Configuring Automatic Debugging https://msdn.microsoft.com/en-us/library/bb204634(vs.85).aspx
Using WER: Collecting User-Mode Dumps https://msdn.microsoft.com/en-us/library/bb787181(v=vs.85).aspx
Enabling JIT-Attach Debugging https://msdn.microsoft.com/en-us/library/2ac5yxx6.aspx
I have a WP8 App where I want to store the crash logs if and when generated.
Is there any way of fetching the crash dump file from Windows Phone 8 programmatically?
As far as I know, you can't retrieve the crash dumps that are automatically sent to the DevCenter. However, what you can do is subscribing to the global unhandled exception event handler, store the exception contents in the isolated storage, then do whatever you need with it (like sending it to a remote server). That's what many applications do, and it's even automated by some libraries (such as Telerik).
You can achieve that by using a logging system as MetroLog. You'll be able to collect these crash logs if you configure GlobalCrashHandler that will ensure that a FATAL log entry is written if an unhandled exception occurs.
You can install it using NuGet
Install-Package MetroLog
Here's an quick example:
using MetroLog;
using MetroLog.Targets;
LogManagerFactory.DefaultConfiguration.AddTarget(LogLevel.Trace, LogLevel.Fatal, new FileStreamingTarget());
GlobalCrashHandler.Configure();
ILogger log = LogManagerFactory.DefaultLogManager.GetLogger<MainPage>();
log.Trace("This is a trace message.");
You can find a tutorial explaining how to add it on your project at http://talkitbr.com/2015/06/11/adicionando-logs-em-universal-apps. Also there is an explanation regarding retrieving these logs.
Several weeks ago side loading was working on my windows phone 8 device. I had installed a valid enrollment token (.aetx file). I was able to successfully side load signed .xap files (either via downloading in IE or attaching to an e-mail). All was good.
Then I ran down the battery and left the device for dead for over a week. When I tried to run the old side loaded apps they worked. But when I tried to side load a new xap I got an error message that said something about it having been too long since the enrollment token was verified with Microsoft. I wish I'd written it down, because I can't get the error to show up again.
Now when I try to side load apps nothing happens at all. It pops up the familiar dialog that confirms I want to install the app ("Would you like to install [my app] from [company name]?"), then I click install and the dialog disappears and the app isn't installed.
When I try to install the .aetx again it pops up the dialog to install, I click install, and then nothing (same as the first time). Xap files still won't install.
Guessing that the phone needs to re-verify the enrollment token with Microsoft I tried waiting 24 hours, but that didn't help. I'm running out of ideas.
In lieu of a direct answer, could someone help me at least get an error message? Nothing shows up in the output window in Visual Studio when I try to side load while debugging an app and I'm not able to find any OS level error logs.
Did you try to install the aetx on another phone or did you try to reset your phone? You should also watch out for invalid date and time on the phone. I've run into similar problems with Lumias which keep on resetting to the 1.9.2012 7:00. The aetx was then declared invalid and was not installed.
Incidentally, it eventually started working for me again. I can't recall now how long it took, about a week I think, but I'm guessing eventually it called home and re-activated the enrollment token.