-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Upload crashes using a background URLSession #271
Comments
Hmm, we are using sentry-cocoa/Sources/Sentry/SentryClient.m Lines 75 to 76 in 8e4791a
|
That would be part of the required change. Background session also don't support completion handlers or data tasks. It would need to be changed to use the URLSessionDelegate methods and upload/download tasks. Using delegate methods would be a bit of work since it's already using completion blocks but switching to upload tasks should be easy since you're already writing a file to disk which is required for background uploads. https://developer.apple.com/documentation/foundation/url_loading_system/downloading_files_in_the_background |
This issue could be fixed with fixing #316 |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
This is a duplicate of #316. |
Platform:
Swift:
sentry-cocoa installed with:
Version of sentry-cocoa:
4.1.0
I have following issue:
If the app is stuck in a state where it crashes on launch, the crashes are never sent to sentry. These types of crashes do appear on Crashlytics.
Source: Crashlytics.h
Steps to reproduce:
Actual result:
Crash logs never show up on sentry until the bug is fixed and deployed to the app that is crashing
Expected result:
Sentry should create the network request to upload the crash by using a background
URLSession
. This would allow the system to handle uploading the crash even if the app is unable to run.The text was updated successfully, but these errors were encountered: