A Microsoft operating system that runs on personal computers and tablets.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I'm facing a strange issue. I sideload my UWP app(version: 220.127.116.11) on my machine. Then, I updated app to the new version 18.104.22.168.
When I rebooted the OS, I found that the app revert to the original version(22.214.171.124). It's so strange.
I wanted to know what causes this problem.
I made a simple test about this but I could not reproduce this issue. May I know what's the OS version of your device? Another thing I want to know is how do you update your app?
@Roy Li - MSFT I'm collecting more detailed information to clarify my question with you. @Körmöndi István The question was not related to the last (fourth) section of the version number. I mentioned the version 126.96.36.199. This is just one example I gave.
Sure, please let me know when you got the message
@Roy Li - MSFT "May I know what's the OS version of your device?" The OS version is 1909(build 18363.449). "Another thing I want to know is how do you update your app?" I sideload my app(version 188.8.131.52) by the "Add-AppDevPackage.ps1" powshell file. When I want to update my app to new version 184.108.40.206. I will un-install the version 220.127.116.11 at first and then sideload the new package. Once the app sideloaded successfully, I also will run it and check the version number that diaplayed in my app. The version number was right at this time. But once I logout and login the system account or reboot the system, the app will revert to the version 18.104.22.168.
If you cannot reproduce this issue on your side, you might need to get help from the relevant teams(technet or ...). Let them tell you something that might be causing the problem. Thank you again.
Is there any log in below location on issue computer about your issue ?
@Andy YOU Do I need to provide the above all logs for you?
@Andy YOU Can you give me a response? Instead of keeping silent. You let me check the event logs. I have checked them. But there are thousands of records in each log. Can you narrow it down? What types of logs do I need to focus on? Or are there any key pieces of information that might be relevant to this issue? Or, in your experience, what are the possible causes of the problem? With these measures, I can do some troubleshooting first. It will save our time.
Sign in to comment
Sort by: Most helpful
How did you managed to change the very last (forth) section of version number?
When you open Package.appxmanifest with project editor (Packaging tab), you can edit only the first three section, however you can overwrite the entire version number using the xml editor.
The related Microsoft documentation claims that last section of version number is reserved for Store use.
Modification of last section may not be recommended for sideloaded applications either. Leave 0 on the last section and use the first three sections for version control.
Maybe it helps.
"For Windows 10 (UWP) packages, the last (fourth) section of the version number is reserved for Store use and must be left as 0 when you build your package (although the Store may change the value in this section). The other sections must be set to an integer between 0 and 65535 (except for the first section, which cannot be 0)."
Sign in to comment