The question I have is:
is what I am seeing expected behaviour of the plugin example app?
I have loaded up the example app that comes with the plugin.
And I have got the 3 ways of receiving a message to work. That is the app in foreground, in background and terminated.
However if I mix the sequence of events I can get a crash.
So if I start off with the app in the background and send a message, all works fine.
I then leave the app in foreground and send a message. The message turns up correctly and I get the popup dialogue. But when I hit the show button, the app crashes.
I have not seen any reference to this anywhere, so I'm wondering whether I am doing something wrong or whether I should expect this behaviour from the example app.
The crash message says to report an issue on github which I have done, but I thought it wise to also put up a stackoverflow question as well just in case this is a well-known problem. Although I have looked around and not found any reference to this problem. The main things I have found are people not being able to receive messages at all.
The error reported is as follows:
+6 ms] I/flutter (16790): The following assertion was thrown building Navigator-[GlobalObjectKey<NavigatorState>
[ ] I/flutter (16790): _WidgetsAppState#5ce51](dirty, state: NavigatorState#ad3be(tickers: tracking 2 tickers)):
[ ] I/flutter (16790): 'package:flutter/src/widgets/navigator.dart': Failed assertion: line 1846 pos 12: '!_debugLocked':
[ ] I/flutter (16790): is not true.
[ +1 ms] I/flutter (16790):
[ ] I/flutter (16790): Either the assertion indicates an error in the framework itself, or we should provide substantially
[ ] I/flutter (16790): more information in this error message to help you determine and fix the underlying cause.
[ ] I/flutter (16790): In either case, please report this assertion by filing a bug on GitHub:
[
Has anyone else experimented with the firebase messaging example app and not seen this problem.