-
Notifications
You must be signed in to change notification settings - Fork 259
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
Cognito Error during Android plugin registration: The client tried to add a plugin after calling configure. #312
Comments
Hi @alextekartik please see this issue: #99
|
Thanks @fjnoyp for the info. Pressing back is a common task, and killing the FlutterActivity can happen in low memory situation (which is hard to reproduce so pressing back is a way to mimic what would happen). Other plugins deal with the situation on the native side (i.e. the issue only happens with the cognito plugin for the 10+ plugins I have). If you get a Missing plugin exception on issue #99, it is just because the registration fails which could be solved on the native side. |
Thanks for that insight @alextekartik I'll investigate what you said. |
This is fixed in #345 which will be part of next release. You would have to still catch the exception |
Describe the bug
In some specific Android restart scenario AuthCognito plugin fails to register (typically the second time).
To Reproduce
Unfortunately I don't a small project to reproduce. But basically, there is a crash when:
Expected behavior
Pluging Registration ok. When plugin registration fails, we end up with a Missing Plugin Exception (that could happen on other plug).
Screenshots
I had to override GeneratedPluginRegistrant.registerWith to catch the logs in MainActivity.configureFlutterEngine with something like that
Logs:
There are also some additiontial logs during Code initialization:
Platform
Amplify Flutter current supports iOS and Android. This issue is reproducible in (check all that apply):
[x] Android
[ ] iOS (not tested)
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: