You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we integrated Sentry in our iOS project and went with the default implementation as mentioned in the Manual setup docs.
The issue that we are facing is that Firebase crashlytics logging some crashes which are due Network and I/O Tracking done by the Sentry. Here's the attached Screenshots of related crash on Crashlytics.
Sentry Network Tracker crashes:
Sentry File I/O Tracker crashes:
After disabling the these two types of tracking as mentioned here. These crashes stopped appearing in the Crashlytics.
Expected Result
These crashes should not appear in any kind of tracking.
Actual Result
Network Tracking and I/O File Tracking causing crashes
Sentry Network Tracker crashes:
Sentry File I/O Tracker crashes:
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered:
Platform
iOS
Environment
Production
Installed
Swift Package Manager
Version
8.44.0
Xcode Version
16
Did it work on previous versions?
No response
Steps to Reproduce
Recently we integrated Sentry in our iOS project and went with the default implementation as mentioned in the Manual setup docs.
The issue that we are facing is that Firebase crashlytics logging some crashes which are due Network and I/O Tracking done by the Sentry. Here's the attached Screenshots of related crash on Crashlytics.
Sentry Network Tracker crashes:

Sentry File I/O Tracker crashes:

After disabling the these two types of tracking as mentioned here. These crashes stopped appearing in the Crashlytics.
Expected Result
These crashes should not appear in any kind of tracking.
Actual Result
Network Tracking and I/O File Tracking causing crashes
Sentry Network Tracker crashes:

Sentry File I/O Tracker crashes:

Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: