2
votes

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.

1

1 Answers

2
votes

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.