-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[Firebase-Messaging] Error 105 received from application: Isolate must be runnable when background notification is enabled #2468
Comments
Hi @navigui |
So this is a brand new project with only firebase messaging package My Application.kt file
my AndroidManifest.xml
my app/build.gradle
my pubspec.yml
my main.dart
my flutter run --verboselogs
and then the app crashesthis is a very important feature in my app. Your help will be ver valuable |
In My Project, this happens because of this line, When I remove that line everything works normally, But my app requires background message handler as well. |
Closing in favour of trying the latest messaging version which has since this issue was created been heavily reworked to improve it along with detailed documentation: https://firebase.flutter.dev/docs/messaging/overview If you still have a problem please raise a new GitHub issue with up to date information and code snippets if possible. Thanks. |
Describe the bug
Error 105 received from application: Isolate must be runnable
When using Background notification
In Vs code Call Stack, a new main() instance is added per hot reload, the application crashes after 3 hot-reloads
To Reproduce
Implement the package even with a vanilla project reproduce the issue when background notification is enables
Flutter doctor
[✓] Flutter (Channel beta, v1.17.0-3.2.pre, on Mac OS X 10.15.4 19E287, locale fr)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] VS Code (version 1.44.2)
[✓] Connected device (3 available)
The text was updated successfully, but these errors were encountered: