Wrong path to Environment.SpecialFolder.LocalApplicationData.

[JiuLing-zhang]

Description

The path I get is inconsistent with the actual.

Test source code:
LocalApplicationDataPathError.zip

Steps to Reproduce

1.Create MAUI App.
2.Get path using Environment.SpecialFolder.LocalApplicationData enum.
3.Check the path using everything.

Version with bug

Preview 14 (current)

Last version that worked well

Unknown/Other

Affected platforms

I was not able test on other platforms

Affected platform versions

Windows SDK 10.0.19041

Did you find any workaround?

No response

Relevant log output

No response

[v-longmin]

Verified the issue on VS 17.2.0 Preview 2.1 [32317.152.main], it's repro. Repro project:
LocalApplicationDataPathError.zip

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[XamlTest]

Verified this on Visual Studio Enterprise 17.6.0 Preview 3.0. Repro on Windows 11 with below Project:
5900.zip

[softlion]

Issue verified 10 times, no fix for release in october. MMmmmm...

[bsloehr]

For anybody migrating an app from XF to MAUI and made use of the LocalApplicationData folder in Android, the work around is mentioned here: #21438

[keegan-gehrig]

Are there any workarounds for getting Windows.System.Launcher.LaunchFileAsync(IStorageFile, LauncherOptions) to work in WinUI and allow files stored in the LocalApplicationData folder to be launched from a .NET MAUI app when this environment variable is giving me the wrong path to the local files? As it stands right now, this bug is just causing my app that I'm working on converting from Xamarin.Forms to MAUI to always get a ". contains an incorrect path." error after selecting a program to open a file stored in this folder with. If no workarounds exist for LaunchFileAsync, then is there any alternative that can be used that's actually able to launch something properly from the LocalApplicationData folder (for WinUI specifically)?

Edit:
I ended up finding my own workaround for the WinUI issue. It seems like this should work for what I need specifically, and hopefully it can provide some assistance to others as well. If there's anything wrong with this method, please let me know, but this does seem pretty safe from what I've tested so far:

var localAppDataPath = Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData); var localAppDataFullPath = $"{localAppDataPath}\\Packages\\{Windows.ApplicationModel.Package.Current.Id.FamilyName}\\LocalCache\\Local"; if (!filepath.Contains(localAppDataFullPath)) filepath = filepath.Replace(localAppDataPath, localAppDataFullPath); var file = await StorageFile.GetFileFromPathAsync(filepath); var launcherOptions = new LauncherOptions { DisplayApplicationPicker = true, }; await Windows.System.Launcher.LaunchFileAsync(file, launcherOptions);

[jfversluis]

I think this has to do with a packaged app vs unpackaged app. We have taken that into account in the FileSystem APIs. Otherwise, I don't think this is something we control, but rather something in WinUI or the .NET runtime even.

Thanks for all the input here!