Closed luizmota82 closed 2 years ago
Hey @luizmota82, path configuration rules need to get more specific as you get further down the file, since they cascade, like css. So, what's happening, is all urls are picking up the default configuration at the bottom of the file:
{
"patterns": [
".*"
],
"properties": {
"context": "default",
"uri": "turbo://fragment/web",
"fallback_uri": "turbo://fragment/web",
"pull_to_refresh_enabled": true
}
}
Move this to the top of the file and you should be good, then. Let me know if that doesn't solve the issues you're seeing, thanks!
See: https://github.com/hotwired/turbo-android/blob/main/docs/PATH-CONFIGURATION.md#rules
Worked like a charm, thank you @jayohms 🚀
Problem
Trying to trigger navigation from either native menu buttons or from app schemas, through
TurboActivityDelegate
, does not navigate to appropriate turbo fragment as declared in the.json
fileHere's my
.json
file:This is my
TurboSessionNavHostFragment
Triggering the following calls do not navigate to the appropriate fragments, it always loads on the same dashboard
Could someone please clarify what seems to be the issue here?