When tracing a package using the FRF by using ProcessMonitor, we often see attempts to access using paths like:
C:\Users\XXX\Local\AppData\Packages\YYY\LocalCache\Local\Microsoft\WritablePackageRoot\VFS\Local AppData\...
Most of the time these things don't get found and the FRF functions move on, but sometimes I see something getting created and later on the application tries to use it and can get confused and fail.
The ShouldRedirect function should not return a redirection path to something input into the function under WritablePackageRoot.
When tracing a package using the FRF by using ProcessMonitor, we often see attempts to access using paths like: C:\Users\XXX\Local\AppData\Packages\YYY\LocalCache\Local\Microsoft\WritablePackageRoot\VFS\Local AppData\...
Most of the time these things don't get found and the FRF functions move on, but sometimes I see something getting created and later on the application tries to use it and can get confused and fail.
The ShouldRedirect function should not return a redirection path to something input into the function under WritablePackageRoot.