PlatformException(channel-error, Unable to establish connection on channel., null, null) when starting Firebase.initializeApp from iOS background task
markalroberts opened this issue · comments
- I have read the README
- I have done the setup for Android
- I have done the setup for iOS
- I have ran the sample app and it does not work there
Version
| Technology | Version |
|---|---|
| Workmanager version | 0.52 |
| Xcode version | 14.1 |
| Swift version | 5.7.1 |
| iOS deployment target | 16.x |
Describe the error
I am trying to use WorkManager for a regular 15 minute background tasks to update the BadgeIcon number and show some local notifications. This works fine on Android. On iOS, when I simulate background refresh, I get this error at the point that Firebase.initializeApp is called at the start of Workmanager().executeTask- however it works fine when it's called in main.dart.
PlatformException(channel-error, Unable to establish connection on channel., null, null)
I have tried to find out what could be causing this and all searching points to a mismatch in versions of Firebase or dependant libraries. I have gone through the Flutter clean and update process but it has not helped.
Output of flutter doctor -v
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.6, on macOS 12.7 21G816 darwin-x64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.78.2)
[✓] VS Code (version 1.78.2)
[✓] Connected device (3 available)
[✓] Network resources
• No issues found!
Any update on this?
I recommend using firebase REST API for now
I'm running into this issue as well.
I've had the same problem. But it was my mistake - I've used a not initialized firebase instance within the isolate ...
I've had the same problem. But it was my mistake - I've used a not initialized firebase instance within the isolate ...
When I initially made that mistake, it gave me a different error from this one. Definitely not the problem here.