I have updated my app (Baby Songs) today by adding some lullabies.
When I tested my app on the device, everything worked great.
But when I download the app from the store (https://www.windowsphone.com/en-us/store/app/baby-songs/3c30a535-6483-410f-9fc1-a2248a77f9b0) the app crash at launch.
Can give me some track to understand this crash ?
I have try to rollback to previous commit, and the application still crash...
When I install the .xap manually (with wp power tool), everything works...
I have submit .xap file on my own account on beta (my account use the old dashboard, don't know why) And there is no crashs.
For me, it's definitively a problem with the new dashboard.
I also had the same incredible problem...
There is (at least) a bug in the WP 8.1 OS with 50 character long "Identity Name" (what is the key to update the app).
I have described it in detail here:
App don't start after update over the store
Related
This is really annoying. Microsoft needs to grow up and fix such silly issues.
I already have a developer unlocked device in which I was able to debug until now. All of sudden it started showing device is not unlocked for developer. Now when I am trying to register it is showing iPOverUsbSvc is not running. I restarted the service. Stop and start the service. Phone and system both restarted. Nothing working for me.
I tried this but nothing seems to be working
Okay finally go the solution. I needed to change the name of device from File explorer and it worked
But the error message we get of no use.
Thanks
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
The Windows Store App Cert kit fails to start.
Normally the flow is:
Start App Cert Kit
Choose Windows Store Application
Choose App
Choose Certs to Run
Run Certs
Save results
Currently, it fails just before 'Choose App'.
I get this result:
I have tried uninstalling and reinstalling, installed all updates, running appcert.exe reset. All to no avail.
I think it may have to do with the same issue I get with the Windows Store app. I have 38 languages installed (our app supports all of them) and the Windows Store app doesn't like it. I've had to escalate with customer support repeatedly for this, and have not had it resolved properly. I wonder if the same issue applies here.
So I was unable to start the UI, but I was still able to run the appcert by manually calling it on the command line as described here. It worked fine. One thing to note is that between each attempt, make sure to run appcert.exe reset.
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.
I'm running into what seems to be a serious usability problem for users trying to use a Google Drive app from more than one account. In order for an app to be able to use Drive APIs on a user's behalf, the user must install the associated Chrome Web Store app while logged in as that user. The problem is that the Chrome Web Store seems to look for an app being installed per browser, whereas the Drive API needs the app to be installed per user.
As far as I can tell, the only way to install the same app for multiple users in the same (Chrome) browser is to install with one user, then log in as the second user, uninstall the app (which the CWS says is already installed), and then reinstall it (so that Drive will mark the app as installed for the second user). This is a very confusing experience, because during this process the app and the CWS are sending the user mixed messages about whether the app is installed.
I'm not sure if there's a canonical app to test for system bugs like this. Is DrEdit live somewhere? But if you want to see the problem behavior in our implementation, install the Graphing Calculator by Desmos.com as one user, launch it and log in using google drive and verify that everything is working. Then log out from the app, and use https://accounts.google.com to log in to google as a different user, and try using the app again. The app will tell you that it isn't installed (that's what Drive's APIs are telling us) and direct you to the CWS, which claims that the app is installed.
We are aware of the issue. And I agree this is a really bad experience for users using the same Browser (and the same Chrome session). One of the issue is that the account you are logged-into chrome can be different than the account you are logged into Google Web (Gmail, Chrome Web Store, Drive etc...) Therefore the Chrome Web Store has to make a choice to either use the apps's install status on the Browser or the Web Google account.
If you write an FAQ for your users maybe you can suggest that the most effective way to install the app for the second user is to simply install it using another browser like Firefox. Especially since Firefox won't be impacted by this issue because the app doesn't get installed on Firefox, only on the Drive account :)
The bug is filed internally, now we can only wait for it to be prioritized and fixed/sorted-out. We are also working on some other way for apps to have an install flow that doesn't involve the Chrome Web Store so that it will be less impacted by all of he Chrome Web Store/Chrome browser intricacies.
I'll make sure to ping our eng team on that issue again.