Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: ClearAllDanglingCalls onResume in web app after upgrading to flutter 3.22.0 #108

Closed
2 tasks done
uberchilly opened this issue May 15, 2024 · 6 comments
Closed
2 tasks done
Assignees
Labels
bug Something isn't working

Comments

@uberchilly
Copy link

uberchilly commented May 15, 2024

Description

After upgrading to flutter 3.22.0 in my flutter web app on each resume I get bombarded with lots and lots of logs clearAllDanglingCalls

Minimal Reproduction

Steps to reproduce the behaviour:

  1. Upgrade to flutter 3.22.0
  2. Run minimal flutter app with auth library on web

Exception or Error

Uncaught (in promise) InternalError: too much recursion
packages/flutter_web_auth_2_platform_interface/flutter_web_auth_2_platform_interface.dart 38:47  clearAllDanglingCalls
packages/flutter_web_auth_2/flutter_web_auth_2.dart 88:21                                        _cleanUpDanglingCalls

Expected Behaviour

To work like it does with flutter 3.19.6

Screenshots

No response

Additional context

No response

Device

Desktop Computer

OS

Windows 11

Browser

Chrome

Flutter version

3.22.0

flutter_web_auth_2 version

3.1.1

Checklist

  • I have read and followed the entire troubleshooting guide and it has not provided the solution I need.
  • I have provided all the information I can.
@uberchilly uberchilly added the bug Something isn't working label May 15, 2024
@Sernrbia
Copy link

I have the same issue

@ThexXTURBOXx
Copy link
Owner

Sorry - I did not even get notified about the 3.22.0 release. Will fix ASAP and release a fixed 3.x version. The same fix will be applied in the 4.x pre-releases as well.

ThexXTURBOXx added a commit that referenced this issue May 15, 2024
@ThexXTURBOXx
Copy link
Owner

It is a very interesting issue... I don't know why it actually worked flawlessly in 3.19.x - it should have caused this problem from the beginning, but I am glad it didn't!
I will push the new update in a minute as version 3.1.2.

@ThexXTURBOXx
Copy link
Owner

The new version has been published. I will close this issue. If it still persists (for some reason), I will probably need a bit more information

@uberchilly
Copy link
Author

From my initial tests it works now, thank you for the quick fix!

@ThexXTURBOXx
Copy link
Owner

Thanks for the feedback, perfect! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants