Skip to content
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

Exceptions not propagated back to message channels on iOS #75657

Closed
ammaratef45 opened this issue Feb 8, 2021 · 4 comments
Closed

Exceptions not propagated back to message channels on iOS #75657

ammaratef45 opened this issue Feb 8, 2021 · 4 comments
Labels
r: invalid Issue is closed as not valid

Comments

@ammaratef45
Copy link

When a native iOS code fails, if the call for the method channel with surrounded with a try catch block, it still crashes instead of allowing the flutter code to catch an exception

Is there a way to prevent that from happening?

@TahaTesser
Copy link
Member

Hi @ammaratef45
It seems you are asking for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

@TahaTesser TahaTesser added the r: invalid Issue is closed as not valid label Feb 9, 2021
@ammaratef45
Copy link
Author

@TahaTesser That is a feature request actually, I'm asking for flutter to throw allow catching an exception instead of killing the app

@TahaTesser
Copy link
Member

TahaTesser commented Feb 10, 2021

Hi @ammaratef45
It depends on where you using the method channel in your app. If you follow please Writing custom platform-specific code

If still, you can experience a crash, Can you please provide your flutter doctor -v and flutter run --verbose with crash logs, and a minimal complete reproducible code sample?
Thank you

@github-actions
Copy link

github-actions bot commented Aug 6, 2021

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
r: invalid Issue is closed as not valid
Projects
None yet
Development

No branches or pull requests

2 participants