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.
Related
What happens when a developer updates an app? Does the user that updates the said app download a whole new app or is the windows app store smart enough like play store to just download the changes?Can anyone give logical explanation how it works in windows store?
>>Does the user that updates the said app download a whole new app or is the windows app store smart enough like play store to just download the changes?
When the developers created package for their project, and chose generate app bundle always, the user can download faster with an app bundle, because they only download the assets that they need. Then they don’t need to download a whole new app to update. If the developers didn’t choose this, the user may need to download a whole new app.
>>Can anyone give logical explanation how it works in windows store?
For example, if you create a app, then you choose generate app bundle always when packaging your app and publish this in the Windows Store. The customer need to download 100MB to require this app. After a period of time, you update this app, the customer just download the assets that they need to update our app, maybe just download 10MB.
I will attempt to be clear. Well, in the old web store of Windows Phone 8 before I could download manually any app or game, via the link: "Download and install manually" as you can see
in this image It is a feature that was lost with the arrival of the new store of Windows 10.
Ok. Now, in the following video Download and Install Apps (XAP/APPX Files) on WP8.1 via PC you can see at time t=53 sec, appears at bottom of page the link http://www.windowsphone.com/en-us/store/app/vimeo/the App ID/xap?apptype=regular
After the user clicks on 'Download and install manually' a popup box appears. Now you can see inside the pop-up box that the downloading of the app is downloaded from: http://cdn.marketplacecontent.windowsphone.com
But in fact the complete address follows this format:
http://cdn.marketplacecontent.windowsphone.com/public/the App ID?downloadname=name of the app.type of file(xap, appx or appxbundle)
For example, this is the direction of the game Tentacles: Enter the Mind from the Microsoft CDN server:
http://cdn.marketplacecontent.windowsphone.com/public/8915ee7c-c55d-4e8f-a0b6-f80497e6f26e?downloadname=tentacles-enter-the-mind.xap
As you just seen, the old web store of Windows Phone 8 could download apps and games from the Microsoft CDN server. Even with the new store Windows 10 you can still download apps from Microsoft CDN. There are website that somehow can download apps and games from the Microsoft CDN server such as: www.appx4fun.com www.windowscommunity.in and www.winphonehub.org to mention some.
Based upon everything I said, you have any idea of how to I can access the Microsoft CDN server to download apps without resorting to third-party stores? I would like to know how they do it.
NOTE: All apps can be downloaded manually using this address:http://cdn.marketplacecontent.windowsphone.com/public/the App ID?downloadname=name of the app.type of file(xap, appx or appxbundle)but for it to work you need to know the ID of the app you want to download and the type of file. How can I find the ID of the app? Know the ID is a very important information!
Well, that's all. I hope your answer
Regards.
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 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.
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.