Issues

Stacks from NavigationStackFactory, even with a persistence provider, return INavigation<T>, which has no Save/Load methods, so persistence needs a downcast
ktsu-dev/Navigation#76 · opened on Sep 30, 2026
1
When a NavigationChanged handler throws during Undo, the stack is already undone but the provider records the action as not undone, so Redo is disabled
ktsu-dev/Navigation#75 · opened on Sep 30, 2026
1
Setting NavigationItem.DisplayName to "" or null makes the whole saved history unloadable: LoadStateAsync returns false while HasSavedStateAsync returns true
ktsu-dev/Navigation#74 · opened on Sep 30, 2026
1
NavigateTo copies the whole history on every call, even with no undo provider; with an undo provider each retained action keeps two full snapshots (O(n) per navigation, ~125 MB at 50k entries)
ktsu-dev/Navigation#72 · opened on Sep 29, 2026
1
A cancelled or interrupted SaveStateAsync truncates the state file and destroys the previous save; HasSavedStateAsync then says true while LoadStateAsync returns false
ktsu-dev/Navigation#71 · opened on Sep 29, 2026
1
A loaded state with currentIndex: -1 but non-empty items is accepted, and the next NavigateTo silently deletes the whole restored history
ktsu-dev/Navigation#69 · opened on Sep 28, 2026
1
JsonFilePersistenceProvider.LoadStateAsync throws UnauthorizedAccessException for an unreadable state file, while other read failures return null
ktsu-dev/Navigation#66 · opened on Sep 28, 2026
1
Concurrent NavigateTo throws ArgumentException and corrupts history, despite README's "Thread-safe operations"
ktsu-dev/Navigation#57 · opened on Sep 26, 2026
2
Undo after GoBack, Clear or LoadStateAsync drops the newest page and jumps to an unrelated state
ktsu-dev/Navigation#55 · opened on Sep 26, 2026
1