Same UWP app [Win 10 build 16215 Local Machine or Win 10 Emulator (x86) 10.0.10586] using NavigateCommand from Login to Home (MasterDetail) as shown in YouTube https://www.youtube.com/watch?v=cBgMPW-Bcx8 => All navigation without problem
Problem only happens if I replace BACK the NavigateCommand back to NavigateAbsoluteCommand Automatically created by AppMap
=> The problem, at the Login Page, click Home ( crashes the app when it is NavigateAbsoluteCommand AND not NavigateCommand )
I'm sorry, but I do not understand your issue. Could you please provide more details? Maybe provide a sample app.
Using the tutorial shown by the youtube. I use Visual Studio 2015 upgrade 3 App Map Extension to create the visual studio project.
Without using the NavigateAbsoluteCommand - Only the standard NavigateCommand, all Navigation Works.
So, NavigateAbsoluteCommand code created by the Visual Studio 2015 App Map extension causes error.
I was confused because you can't create a UWP app with the AppMap. However, I manually added an UWP app and see what you mean. It seems the URI format is evaluated differently on UWP. Will be an easy fix. For now, just manually change the command to use the NavigateCommand instead of the NavigateAbsoluteCommand. As long at the target URI has a "/" in front of it, it will be seen as an absolute navigation.
As we are approaching Q4 2017 with Windows on Arm, we can use XAMARIN FORMS to develop UWP app (for running ARM64 native and Win32), AND WPF (win32).
I urge that UWP be included in the App Map.
Furthermore, I notice that there is increasing interest with UWP in Xamarin Forms Forum. In particularly, this one is relevant to App Map
FYI: I use Prism Unity to create the Xamarin Forms PCL, and I added an UWP app
The reason UWP is not include in the AppMap is because our XF controls currently do not support UWP. It's not a limitation in the AppMap directly, and can easily be added. We realize that UWP is starting to gain more interest and we are planning on adding UWP support by Oct/Nov timeframe.