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=
Related
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 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
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.
I have successfully published an app on windows phone store without any problem but when i try to publish an update of the xap file i had some problem.
First I don't understand if have to replace the xap file or add new xap file with higher version number.
Second, if I update the version number in the app manifest and upload the app in developer console, the version number is always 1.0.0.0. It's a bug or is normal?
I tried to add a new xap with higher version number but when a user with installed app receive the update the app crash on startup, but the app works if is installed from scratch.
Developer console is very confusing for me, I never had problems with android developer dashboard.
Here you have a little guidance - if you hadn't seen that before. Here is also a documentation about updating process.
From my experience it goes like this:
when you click Update, then the new submission is started
you choose there to replace your XAP file with the new compiled one - don't worry it won't delete old file unless new passes certification and you choose to publish it (watch out for automatic mode)
you modify the version number at this website, (this numer is used only for Store purposes), if you change the number before replacing the XAP file, the number will be old again (probably page reload).
your 'InApp' version number is taken from AssemblyInfo.cs (or in Project Properties) in your App. You should also change version number in WMAppManifest.xml -> Packaging
you should use 'Add new XAP' file if you want to make the App to run on different OS versions
be aware that files on IsolatedSorage are preserved.
Hope this helps.
I am having a windowsPhone 8(lumia) device and I want to debug my App in Real Device.I used Developer Phone Registration.The problem i am facing now is,If click register button a small window appears and Vanishes after 15 seconds and cant able to register,plz help me.
Make sure you're running Developer Phone Registration from Windows Phone SDK 8.0, on Windows 8 - 64 bit.
Unlock phone screen during registration
Windows will ask you to enter a valid Windows Phone Developer account (which cost you $100)
You need to connect to Internet
Are the date and time set correctly on the phone? In SETTINGS | date + time, turn off the Set automatically setting and then retry registration. After registration succeeds, turn this setting on again.