This repository has been archived by the owner on Oct 29, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 149
NavigationManager does not work anymore on Hybrid Apps #476
Comments
Hi @Lele0037 , I'm not sure what could have caused this, but if you're looking to gain some new features as well as lots of bugs fixes, I recommend using this fork of Mobile Blazor Bindings by @Dreamescaper : https://github.com/Dreamescaper/BlazorBindings.Maui |
you can temporarily fix it by overriding navigateTo, by suppressing history recording, you can add it to index.html, something like that
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A year ago (circa) I built an hybrid app using Mobile Blazor Bindings:
dotnet new blazorhybrid -o <my app>
Suddently (maybe due to a recent Google/Android update?) the NavigationManager seems not to be working anymore: my app simply does not navigate to the page it is supposed to go. In another words, the function
does nothing at all. It does not even throw an exception.
I noticed, tinkering with the chrome console while the app is running, that when I try to navigate using the javascript function underneath I received the following error:
Could someone please help me? My app was working perfectly last week and now all the devices where the app is installed are failing one by one. My only guess is that something changed with the default Android Web View app (I noticed it has been updated recently).
The text was updated successfully, but these errors were encountered: