Closed kroikie closed 4 years ago
@andreashaese
The issue at https://github.com/flutter/flutter/issues/24341 has been closed and moved here. Future collaboration on this issue will be done here.
Hi @andreashaese
If you are still experiencing this issue
with the latest version of Flutter and FlutterFire plugin
can you please provide your updated flutter doctor -v
and your and your flutter run --verbose
/flutter build --verbose
?
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you
I'm not sure this is still an issue, but we should leave it open till we are sure.
I am facing this issue , I don't know how to fix it. If anyone found the fix can you please post it
importing dart.io seemed to solve this problem , I read somewhere that lower level exceptions can be caught by importing 'dart.io' and it worked.
@kroikie can you confirm @zinodaks workaround?
Hey @kroikie. We need more information to resolve this issue but there hasn't been an update in 7 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@kroikie if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.
The app crashes when trying to call a Cloud Function while the (iOS simulator) device is disconnected from the internet.
Steps to Reproduce
This
onCall
cloud functionis called in my app as follows:
I'm using the
cloud_functions
plugin. The app is run on the iOS simulator. When connected to the internet, the logs show the expected result:When the device is offline, the expected result would be that an exception is caught in the
catch (e)
statement above. Instead, the app crashes.Logs
flutter run --verbose
:flutter analyze
does not produce output relevant to this issue.flutter doctor -v
:Crash log: