search

SchabanBo / qlevar_router

Manage you project Routes. Create nested routes. Simply navigation without context to your pages. Change only one sub widget in your page when navigating to new route.
MIT License
86 stars 22 forks source link

Route observers stopped observing #108

Closed electraport closed 1 year ago

electraport commented 1 year ago

I have had a weird experience over the past few days. I have updated and made too many changes to know for certain that it's an issue with most recent Flutter or Dart SDK, but I am posting here mostly to see if anyone else experienced it.

Symptom #1: The /#/ returned to the path for web views, even though no change was made to the call to QR.setUrlStrategy(); or the module that it resides in, which has been stable code for some time.

Symptom #2: My route observers stopped firing, with no error or event. Per the issue I just commented on, I am using a GetX service and observers on the route push/pop to set the page title (among other important things) and like Thursday or Friday the route observer just stopped firing. I was working on one specific page which is of course unaffected so I didn't notice for a while that it was an issue which is making it hard to point to exactly the problem.

Sitting down now to dive into troubleshooting. If I find something related to the router I'll send a PR, but the main reason for the issue is - has anyone noticed the above symptoms relative to updating to the latest Flutter or Dart SDK's in VSCode?

PS F:\ElectraPort\project_repos\client-apps\UnityUniClient> flutter doctor -v
[√] Flutter (Channel stable, 3.7.3, on Microsoft Windows [Version 10.0.22621.1105], locale en-US)
    • Flutter version 3.7.3 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 9944297138 (10 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1

[√] Windows Version (Installed version of Windows is version 10 or higher)

[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at C:\Users\qkram\AppData\Local\Android\sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.16)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools
    • Visual Studio Build Tools 2019 version 16.11.32602.291
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2021.2)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[√] VS Code (version 1.75.1)
    • VS Code at C:\Users\qkram\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.58.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22621.1105]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 109.0.5414.120
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 109.0.1518.78

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!
electraport commented 1 year ago

Whoa, for future readers, I was in the middle of a websockets implementation with a new server and for a few days the client was loading with a half-hung websocket that I can only speculate was interfering with the main event loop somehow...once I got the websocket working reliably, this resolved itself along with it. If you get these symptoms, look for a stream/subscription problem somewhere else causing issues.