I submit a test Windows Phone Silverlight Project 8.1 and get this error when submit
The package identity associated with this update doesn't match the uploaded appx: "2e740376-677c-4df8-b1af-95b72863f017"
Windows Phone 8.0 project dont meet that error. Any suggestion? Thanks
I ran into the same problem, but the solution is simple - the Package identity name and Windows Publisher Name in Windows Store Dashboard must match with the values inside the uploaded xap package.
You can find these values in the Windows Store Dasboard in the App identity section:
You then need to copy and paste these values inside your Package.appxmanifest file. Note you have to open this file using text editor. These values are not editable using the UI editor:
I had the same issue and fixed it by going to my dashboard, looking inside my in-progress app, clicking details and there I could see my package id. I copied that and pasted it inside my package manifest file.
Exactly as the error states, your package identity doesn't match. The GUID in your WMAppManifest.xml and Package.appxmanifest have to be identical (and would be so, had you done a new project, or upgraded an existing project). The Package Identity name also have to match with the values from the Store submission process.
And if you're submitting to an existing application ID on the store, you obviously have to use the same GUID as you previously used for submitted.
Related
I have a UWP Application, which needs to be build for two different project configurations i.e for two sets of Microsoft store Application identity and client id and client secret.
So for making two different builds all I do is change the identity tag in package.appxmanifest file. I need to test PushNotifications using WNS for these two project configurations.
The issue is when I manually set the identity tag in package.appxmanifest, the app doesnot receive a notification, but when I asssociate it with the store with the App in Windows store, the app starts getting push notification.
Is there any other file or certificate that needs to be removed for manually changing the identity tag, and making the App work?
the identity tag (inluce phone product id and package name) of the app must be the same as displayed in app store to enable push for this package. When you asssociate it with the app in store, Visual Studio did the copy paste for you.
To have difference build setting, just create a new app in dev center, asssociate your package with it before building to get new configuration.
My requirement is to associate a .exe file with a Windows Store 8.1 app. Is it acceptable to give a link through about section of the store app to a web address from where the user can download the .exe file. Will there be any problem with the certification process. Please suggest any suitable alternative if possible.
There is nothing in the Windows Store Policies that says otherwise. You can't attempt to run the *.exe file programmatically of course, but you should be fine otherwise.
Since the app is network-capable, remember to add a Privacy Policy (see here) detailing whether any user information is sent to an external website/server.
Changing app version (1.4.0.0) in WMAppManifest.xml but when publish on store it show 1.0.0.0 while uploading \ updating the app in windows phone store and also while update the app, I need to “add new” in update app section and all related information should be filled up, please let us know is any alternate way to avoid to fill all relevant data again & again.
thanks,
Sunil
When you update you app for Different versions, you upload a different .Xap file each time so the information that you neeeded to fill is for your new .xap file's Description along with Version number that is the Description for new .xap file and About the Key Updates what you have done in current submission and the new Screens for displaying about new update so There is no way to retain same
infomarmation that you have filled before for old versions. everytime when you upload new version .xap, You needed to fill it again for your new Update Version.
When you update your App in Windows Phone Store. You should choose 'Replace', and after the app uploaded. You should modify the version shown on that page to your app version, like 1.4.0.0 manual.
Is there an API that allows to me to programmatically pull the latest update from the store and refresh the current version that the user is using? If not, is it possible for the current app to programmatically know that there is a new version available?
Any samples/examples would be highly appreciated.
You can't programmatically install any Store software. But you can programmatically open the Store to let it do the user manually.
That said, there's no official Store API which you could ask about app versions (you might be able to parse the Store's HTML pages, but I recommend against this approach).
What you can do: Put a small XML file on your website which contains the latest app version number. Your app then can read this file and compare this desired version against the running app's version. If the app is outdated, the app can show a message box to the user.
I ended up using WNS and Azure Notification Hub to send a push notification to the app when it is launched. The notification is in the form of a toast message that essentially states that a new release is available. But if you updated/downloaded the app after xx/xx/xxxx, no updates are necessary.
I know it is a little cludgy but at least the users now know that the version of the app that they are using may be dated. I control the notification through Azure Mobile Service (which is free for up to 10 apps) and can fully modify the actual script.
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.