ReleaseInfo returns "1.7.0" in 1.7.1 release

[Marv51]

Describe the bug

I know there has been much back an forth about the Microsoft.Windows.ApplicationModel.WindowsAppRuntime.ReleaseInfo-API I thought it was working now in the 1.7 release?
I am getting an incorrect version from the API.

Steps to reproduce the bug

When I add this line to my app that is running on the just released 1.7.1 runtime:

var versionString = Microsoft.Windows.ApplicationModel.WindowsAppRuntime.ReleaseInfo.AsString;

I thought the expected value would be "1.7.1". However the string that is returns is "1.7.0"

The Patch-property on ReleaseInfo is also 0.

Expected behavior

It should return "1.7.0"

Screenshots

I have confirmed that the output of Microsoft.Windows.ApplicationModel.WindowsAppRuntime.RuntimeInfo.Version is correctly 7000.456.1632.0

NuGet package version

Windows App SDK 1.7.1: 1.7.250401001

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 24H2 (22621, October 2024 Update)

IDE

Visual Studio 2022

Additional context

No response

[RDMacLachlan]

Hi @Marv51,

This is a known issue, The Patch property always shows as "0" in Windows App SDK 1.7.

[tpoint75]

Do we need a new runtime installer?
https://learn.microsoft.com/de-de/windows/apps/windows-app-sdk/downloads
1.7.0 (1.7.250310001)

[tpoint75]

Ahh, found it in the english version:
https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/stable-channel#version-17

[Marv51]

Hi @Marv51,

This is a known issue, The Patch property always shows as "0" in Windows App SDK 1.7.

So just to clarify, the ReleaseInfo should show 1.7.1, 1.7.2 etc. but does not because of a know issue. There is hope for this issue to be resolved at some point, but probably not until at least 1.8. Do I understand that correctly?

[codendone]

@Marv51, yes, that is correct. This will be improved in 1.7.2, where the Patch value will become yyMMdd format rather than just "0", which at least will closely match the nuget version (but not the nicer friendly version like "1.7.1").

We would like to get the nuget version and the friendly version to match in the future, which should then be matched here as well. That won't happen until 1.8+, though.