-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Custom release and dist not used for uncaught errors #1
Comments
@kajic i see in my other projects that i do this:
There is a big difference because by doing so |
@farfromrefug Thanks for the suggestion! Unfortunately, the issue persists with |
@kajic ios or android ? |
@farfromrefug On iOS. |
@kajic could you try on android? You might have found an issue with the ios implementation. Want to. make sure you have the same behavior as me on android |
Which platform(s) does your issue occur on?
Please, provide the following version numbers that your issue occurs with:
Please, tell us how to recreate the issue in as much detail as possible.
Initialize the plugin like so:
Then cause the application to crash, and let the plugin catch and report the exception on its own (rather than try/catching it yourself manually).
The exception will get reported to Sentry, but you'll notice that your custom release and dist names were not used.
The text was updated successfully, but these errors were encountered: