I have implemented In App Purchase functionality in my Windows Phone app. It is in beta version.
I have bought some products when testing the app.
So how do I restore products purchased state? I just want to test the functionalaty of the newly on the same device.
UPDATE: For example i have bought SomeProductName and test functionality. Now i need to mark SomeProductName as not bought.
Restoring the state of a purchased product is not possible in test using a beta app as you wanted. It is only possible in "Test using the emulator" or "Test using the emulator with real in-app purchase". See the section "Testing in-app purchase" (row "Allows resetting purchases") in this blog post: http://blogs.windows.com/windows_phone/b/wpdev/archive/2013/11/27/options-for-publishing-windows-phone-beta-apps-and-testing-in-app-purchase.aspx
Althought I guess there are some work arounds which should work, such as:
Create a copy of the product with a new ID
Submit new version of the beta app
Related
Is it still possible to enable authenticated (no-quota) push notifications for company app on Windows Phone?
There were a couple of blog posts by Windows Phone team documenting the process to enable no-quota push notifications for company app but now, on development portal, it is not possible to upload a certificate without linking it to an app.
https://blogs.windows.com/buildingapps/2013/12/10/enabling-no-quota-push-notifications-for-company-apps-on-windows-phone/
https://blogs.windows.com/buildingapps/2013/06/06/no-quota-push-notifications-using-a-root-certificate-authority/
I'm sure Microsoft added this feature a couple of years ago but now it seems to has been removed.
Do you know if authenticated push notifications for company app is still supported by Microsoft?
This is because you have the old developer account UI , and I think you should upgrade to store dev :
Unify windows phone developer account with store developer account
However , there was old trick for enterprise testers to test their apps by passing windows store with Build it Beta, it is similar to testflight, or hockeyapps.
Update:
if you are saying that you have updated your account, and you got the new dashboard simply follow :
Dashboard>apps>services>push notifications
as appears in image below
I'm very, very new to Windows Dev Center, and I'm hoping someone will be able to clear some things up for me. There is an app already within the Store and I want to submit a new version of the app after beta testing. From what I have researched, you can add another submission to the app, and publish it to the store. Then when it's in the store, I'm able to define the visibility of the app. This link is where I get this information. But, if I do this, does this mean that the previous submission is now null and void and can't be found? I think that would be the case? Is there no way to beta test the new version of the app without taking the current version out of the store? Is it recommended to upload a new app named "Blah Blah Beta" and then create a new submission on the original app after the beta gets the okay?
I'm used to iTunes connect and how they do the beta testing, so I'm not sure of the proper protocol in the Windows Dev Center. iTunes Connect you're able to have the current version in the app store, and upload new builds that can be tested.
I hope someone can clarify this for me
Thanks in advance.
I have deployed my UWP in windows store. The app is available in windows store, however, it can be accessed only using the link provided by MS https://www.microsoft.com/store/apps/9nblggh5cdck. The app is not available when I search in windows store. I have used exact name and alternate names, but it's not showing in windows store.
Any suggestion, why it it not available in windows store?
Thanks!
If your app is public (not Beta or Private) it'll take time to be available through the search (Site & Devices) .. around 72 Hours or more in some cases!
UPDATE 1:
That's odd.. I suggest to update the submission and make it Private (2nd option) then after your submission is published.. send another submission and make it Public (1st option).. maybe that will update the servers status and the cache..
Same here. My app not showing in the search result.
It's bug windows store.
https://social.msdn.microsoft.com/Forums/ru-ru/ba1c37da-861d-4108-b905-f1b574a401c6/app-disappeared-from-store?forum=wpsubmit
https://social.msdn.microsoft.com/Forums/windowsapps/en-US/66d1e7d5-9185-419b-ae79-8f457d060f41/my-app-cannot-be-found-in-the-store?forum=wpsubmit
petition:
https://www.change.org/p/microsoft-satya-nadella-bill-gates-windows-store-policy-team-windows-store-fix-windows-store-search-by-title-and-by-keyword-none-searchable-no-results?recruiter=358739216&utm_source=share_petition&utm_medium=copylink
Thank you every one,
I emailed this to Microsoft and then I received reply with following statements:
We have reviewed your app and have moved it up in rank such that you
should see it in the Search results soon.
Within 10 hours after this email, I saw my app in the store.
Thanks to Windows Store Policy Team!
I have a app in Windows Phone Store which is target Windows Phone 8.0 platform.Recently, I'm testing my app on Windows 10 mobile so I won't get in trouble when people upgrade to Windows 10 Mobile.
I found a serious problem for me when testing it. My app will get a complete different "ANID2" value some time. I use "ANID2" value to identify my user and they may lost their data temporary and much worse that the user might get data which is not belongs to him/her.
Here is the reproduction steps:
Write a app to fetch "ANID2" and display it. The app project template is : Blan app(Windows Phone SilverLight target Windows Phone 8.0)
Deploy it to a WP8 or WP8.1 device and record the anid2 value.
Now depoly it to another phone running WP10 with the same Microsoft Accout logged in WP8 of course.
See if the anid2 value is different with the value on WP8.
If they are the same. On WP10 , go open the Store to download and install another app which you never installed before with the Microsoft account. Now,reopen the anid2 test app on WP10. you might find the anid2 value changed.
If the anid value first run on WP10 is different from the value on WP8, then you just wait, wait tomorrow or after tomorrow.During you wait ,you shall not install any new app on the WP10 phone. The anid2 value will eventually changed to the value shown on WP8. Now repeat steps introduced in step 5. You might also find the anid2 value changed.
The result is shown below:
Publisher ID: {0707BD2B-5621-4E0C-83DA-E2B0A5E3B850}
Anid2 Last Time : bUyJ5mwgnjm9b4lyBmThbKr/5VFbsCMTNHpgej+nOcs=
Anid2 Now : XJd6gLP8UDaVBdRB8AI/ZOTM0cThXMxp1msQjFuq5WY=
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.