I am trying to distribute a Windows 10 app to our client via promotional codes generated in the Windows Dev Center "dashboard". But when I try to use the generated codes via http://microsoft.com/redeem, I get the following error message:
"Sorry but an unexpected error occurred. The error has been recorded and we will investigate. Please try to redeem your code later".
The app is uploaded and submitted. In the status field it says:
Detailed publishing status for this submission
Customers Can get packages Can see Store listing
Windows 10 clients ✓ pending
In "Pricing and availability" the app is set to: "Hide this app and prevent acquisition. Customers with a promotional code can still download it on Windows 10 devices."
I have no clue where to begin to resolve this issue, so any information would be appreciated.
Regards
I just spent 30 mins on chat with Microsoft and they're pretty good. 2 things can cause this error:
- reverse compatibility. If you're trying to install an Xbox 360 game on Xbox One it won't work. You have to install it on the 360. If I've got that wrong you know what I mean
- region settings. Your regions must be set the same as where you're living.
Related
I am just beginning working with Banno and Jack Henry plugins and i am trying to run through the Node.js quickstart but have gotten an error trying to access the local host page.
I have succesfully started the server but when attempting to access the login via localhost:8080/login.html i receive a privacy error because the server.cert file contains an expired certificate. I need somewhere to generate a new certificate or where JH has one stored for the dev learning track. Thanks in advance
Your browser should give an option (even if it is somewhat hidden) to continue with the Consumer API OpenID Connect Example (https://localhost:8080/login.html) even though the cert has expired.
For example, with Safari for Mac it should look like this:
Clicking the "Show Details" button brings up a hyperlink option to "visit this website". That'll let you move forward.
The precise steps may be different in your browser + operating system, but the general answer is the same.
I have a Windows Phone application running on a Windows Phone 8.1 device, and I am using Windows Push Notification Services (WNS) to deliver a push message to the device. Delivering push messages has worked for approximately 8 days, until I received WNS headers in the responses similar to these:
X-WNS-NOTIFICATIONSTATUS: dropped
X-WNS-STATUS: dropped
X-WNS-ERROR-DESCRIPTION: Blocked channel URL
X-WNS-MSG-ID: 2DC1361376C2827E
X-WNS-DEBUG-TRACE: DB5SCH101121937
I have not changed the push server implementation, nor the code on the Windows Phone device. There was literally no change in the build of either component. I went home at the end of a work day, and the next day, I ran a simple test only to be presented with that particular error. I have tried the following in an attempt to solve the problem:
Re-created the channel URL on the device.
Re-associated the existing Windows Phone application to the store.
Create a new Windows Phone application in Visual Studio (after association to the Store).
Re-created the Windows Phone application on the developer portal.
Used a different physical device.
Each without success. The documentation regarding WNS is sparse, there are no additional support channels that I am aware of, so I am stumped. What could be causing this particular error "Blocked channel URL", or, how do I solve it?
from your windows phone app you need to renew the url for the notification channel, because the url can be valid up to 15 days.
from the microsoft documentation:
"Request a channel each time the app launches. Channel URLs can expire and are not guaranteed to remain the same each time you request one. If the returned channel URL is different than the URL that you had been using, update your reference in your app server."
Edit:
see this link for reference https://msdn.microsoft.com/en-us/library/windows/apps/hh761462.aspx
Is there anything that can be done to get real-time error reporting from windows phone devices? I have code in my app that will catch errors to let users send them via email, but it's just not happening and yet I keep seeing errors being logged, very few but still occurs every few days, via the Dev center but without details, which is completely useless to me.
Any suggestions, tools, other would be appreciated.
Thanks.
If app crashes try get your info from UnhandledException event and write it to some kind of log file so next time app launches you can send those logs Reference
I've used it in WP8 application and worked fine. To get usefull information from exception do arg.ExceptionObject.ToString()
Use Application Insights to find out what users are doing with your app,
http://www.visualstudio.com/en-us/get-started/get-usage-data-vs.aspx
I've developed a company app for Windows Phone 8, and have gone through all the recommended steps to set it up for installation. I have a Symantec code-signing certificate, and I have generated my Application Enrollment Token and my signed XAP, which I am hosting in a public folder on OneDrive. I generated the XAP using the BuildMDILXap.ps1 script, which ran without errors. I haven't bothered with a company hub app, since we're only distributing a single app.
The AET loads OK on the phone, and asks if I would like to add the workplace account. I click "add", the dialogue box disappears, and no error comes up. There is no confirmation message, however I don't know if I should expect one.
When I load up the XAP, I get the message "Can't install company app. There's a problem with this company app. Contact your company's support person for help."
The phone has been developer unlocked (which of course isn't necessary), and I've had the app side-loaded and running on it successfully before. It was uninstalled before attempting the above, however.
I'm not sure what to do from here. I've tried recompiling and re-signing the XAP and re-generating the AET, but nothing seems to work.
After fruitlessly trying to solve this problem, I found a workaround that does what I need.
It turns out that you can post apps to the public app store, but hide them from searches, essentially making them private to anyone that doesn't have the link. That solves my first problem, getting the app published in a way that my client can access without me needing to have developer licenses for each of their phones.
The downside with that solution is that you still have to wait a few days for an update to be approved, which isn't the greatest when you're still beta-testing and need to make quick changes. However, Microsoft also have a beta program for Windows Phone apps. By designating the app as Beta, submission happens automatically within 2 hours, but you have to restrict access to specific Microsoft accounts. The latter isn't a problem because the number of devices using the app is relatively small.
This removes the need for a corporate app store in my case, and saves the expense of a certificate and the fiddling around that goes with it.
Last Week my team have submitted an application to Windows Phone Marketplace and in the end we got application failed because of the following issue
"LOB App Compliance Requirements - Requirement is App capability consent UI is shown first on first launch of app - Status - Failed. Tester given notes "No app capability consent UI is shown first on first launch of the app". Couldn't able to find out what was the exact error which made Application to fail in Marketplace. Does anyone came across such errors. Any feedback or suggestions will be useful for us.
Regards
When you use a capability, when the user launch application, a pop up should appear for ask user for access.