-
Notifications
You must be signed in to change notification settings - Fork 28
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
Crashes on OS 13 Samsung Galaxy #618
Comments
Hey @ber4444 , I'm not sure I follow, how is the fact that you're getting these exceptions connected to the OTel instrumentation? They seem to be caused by actual network issues happening with your app. The |
It's definitely an exception handling issue on our end, just saying that pinpointing the source is not easy, perhaps you could you provide a helpful stacktrace as you see these IOExceptions come through. |
@ber4444 Just checking the obvious -- are you actually configuring a hostname of In any case, I think that both What kind of additional helpful information are you looking for? |
Yes, that is X'd out to hide the actual host name. I am looking for the REST API path to know which call is missing proper exception handling, since we have a numbers of API's on the same domain (the second exception isn't even descriptive of the domain btw). We actually fixed it already by hunting through the codebase but in a much larger project it would have been a massive pain. |
Following are the stack traces from Crashlytics, they show Open Telemetry which you use under the hood (we use your android sdk):
and
It would be good if we had a way to swallow these exceptions as they run through Open Telemetry. It is hard to know where they originate from.
The text was updated successfully, but these errors were encountered: