none
Window Phone Version Number Corrupted

    Question

  • My version number used to be 1.1.0.x and it got corrupted during an upload. Now it is 2015.625.2138.3822. I tried to set it back in Visual Studio but I get the error:

    The Version attribute of the Identity element in the app manifest must have a higher version number than 2015.625.2138.3822.

    Is there any way to set this back to a normal version number?

    Thursday, June 25, 2015 10:11 PM

Answers

All replies

  • Hello WhiteTusk,

    The version number has not been corrupted this is the standard format for appx packages.  The only way to change the version number back is to submit a XAP package.  Unfortunately you cannot go from an appx to XAP.  If you want the version number back to the 1.X.X.X format you'll need to create a new app and use a XAP package.

    -Miles


    Windows and Windows Phone Dev Center Support

    Send us your feedback about the Windows Platform

    Friday, June 26, 2015 8:24 PM
  • No, something has changed.

    Starting yesterday, when attempting to build my Windows Phone app for the store, the Package.StoreAssociation.xml file is modified beyond just the version number.

    The landing url used to be:

    https://dev.windowsphone.com/AppSubmission/AssociationLanding?windowsProductId=[APPID]

    And now it is:

    https://dev.windows.com/dashboard/Application?appId=[APPID]

    The PackageArchitecture used to be "" and now it is "unknown"

    The PackageMaxArchitectureVersion used to be "1.0.0.14" and now it is "2015.701.43.2459".

    When trying to build version "1.0.0.15" I am getting the "The Version attribute of the Identity element in the app manifest must have a higher version number than '2015.701.43.2459'" error.

    I recognize the new format as the actual appx version, but it's no longer allowing for the user-friendly version number.

    How do I fix this? I don't want to release a version 2016.


    Adam Kinney http://adamkinney.com

    Friday, July 03, 2015 3:57 PM
  • Everything begin from updating dashboard of microsoft. I dont want to change version to 2016...
    Saturday, July 04, 2015 10:26 AM
  • I ended up accepting the change and moved on. Here's the full story if you're interested: http://adamkinney.com/blog/2015/07/03/windows-phone-8-1-store-package-version-change-surprise-one-act/

    Adam Kinney http://adamkinney.com

    Saturday, July 04, 2015 9:50 PM
  • So I've found a way to bypass the store association checks to build the packages.

    C:\Windows\System32\cmd.exe /k "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\VsDevCmd.bat"
    cd <PATH TO PROJECT>
    msbuild /t:Publish /p:Configuration=Release;Platform=AnyCPU
    

    However when I upload the appxupload file, it still reports the build time stamp as the version, rather then the package version.


    Your package will still have the version you want, though store will report the time stamp, which appears the be bundle version rather then the appx version contrary to what the support team suggest.
    Wednesday, July 08, 2015 8:33 AM
  • Thanks for the Info, Adam!
    I had exactly the same problem - maybe MS thinks it should not be too easy for it's developers to submit updates. :(
    Thursday, August 06, 2015 12:18 PM
  • This is NOT true even slightly. There is no standard format for AppX packages (other than having 4 numeric fields - major.minor.build.revision).

    AppX *Bundle* versions are auto-generated using the date at build time. You can ignore these. They do appear in the store on WP 8.1, but Win10 (including Mobile) does not.

    There was a bug when the new Dev Center rolled out, which would cause Windows Phone packages built in VS to shown a bogus error message saying that your package version was lower than the last one, but it was incorrectly comparing your new package version to the old bundle version. There was a workaround for this that involved editing the Package.StoreAssociation.xml file, but the Store team finally fixed the bug a couple weeks ago (and it was a server side change), so you don't need to worry about it any more.


    Tuesday, September 22, 2015 7:36 PM
  • Hello WhiteTusk,

    The version number has not been corrupted this is the standard format for appx packages.  The only way to change the version number back is to submit a XAP package.  Unfortunately you cannot go from an appx to XAP.  If you want the version number back to the 1.X.X.X format you'll need to create a new app and use a XAP package.

    -Miles


    Windows and Windows Phone Dev Center Support

    Send us your feedback about the Windows Platform


    This is terrible advice, never give it to anyone ever again. XAP packages are legacy and not supported any more. The poster was almost certainly hitting the known (and now fixed) Dev Center API / VS bug where it compared version numbers incorrectly.
    Tuesday, September 22, 2015 7:39 PM
  • No, something has changed.

    Starting yesterday, when attempting to build my Windows Phone app for the store, the Package.StoreAssociation.xml file is modified beyond just the version number.

    The landing url used to be:

    https://dev.windowsphone.com/AppSubmission/AssociationLanding?windowsProductId=[APPID]

    And now it is:

    https://dev.windows.com/dashboard/Application?appId=[APPID]

    The PackageArchitecture used to be "" and now it is "unknown"

    The PackageMaxArchitectureVersion used to be "1.0.0.14" and now it is "2015.701.43.2459".

    When trying to build version "1.0.0.15" I am getting the "The Version attribute of the Identity element in the app manifest must have a higher version number than '2015.701.43.2459'" error.

    I recognize the new format as the actual appx version, but it's no longer allowing for the user-friendly version number.

    How do I fix this? I don't want to release a version 2016.


    Adam Kinney http://adamkinney.com


    Yeah, the incorrectly populated PackageMaxArchitectureVersion (only for Phone 8.x apps) was a bug in the new dev center service. It took a little longer than it should have but they fixed it a couple weeks ago. It now gets populated with your last package version (as before and for PC apps), and not the last bundle version which you should never see or worry about.
    Tuesday, September 22, 2015 7:41 PM
  • Yeah~ the bug has fixed.

    But since I have changed my app version to the timestamp format, there is no way to get back to the original version number style that I want.

    I think Microsoft should compare the bundle version only. By this way it will allow developers to have their own logical app version number.


    • Edited by John Forge Wednesday, September 30, 2015 7:56 PM tyop
    Wednesday, September 30, 2015 7:55 PM