-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
Review offline support #3739
Comments
@bruno-garcia, did the user tell you the platforms are affected? (I assume any of them) |
Happens on Android/iOS, but offline caching happens in C# so I imagine testing this on Windows/macOS should yield the same result and easier on the devloop |
Confirmed this is known to happen on iOS. Android doesn't have enough usage yet to be sure. |
While chatting with the customer, an idea to keep track of the count of errors Sentry is capturing, from outside Sentry itself: // Some field to keep the counter:
int _eventCounter = 0;
// in the Init code of Sentry:
options.SetBeforeSend((evt, hint) => {
Interlocked.Increment(ref _eventCounter);
});
// At the point where we'd like to report this to our backed:
async Task ReportData() {
// Reset the counter to 0
var lastCountValue = Interlocked.Exchange(ref _eventCounter, 0);
// Send the current count to our backend so we can check against their reports, and againt what's in Sentry
await _apiService.PostAddErrorCount(CurrentUser, lastCountValue); |
I tried using Android but couldn't reproduce this. I'll try using iOS with the error count you mentioned above. Is it possible that it'd related to NativeAOT? |
A customer who has a MAUI app that goes offline for extended amount of time has reported that events are getting lost.
No client reports indicate data being dropped.
I expected at least:
sentry-dotnet/src/Sentry/Internal/Http/CachingTransport.cs
Line 366 in cb67d21
Reading the code it seems like we don't delete files if the failure reason is network connectivity:
sentry-dotnet/src/Sentry/Internal/Http/CachingTransport.cs
Lines 349 to 357 in cb67d21
But I believe we should run some tests:
The text was updated successfully, but these errors were encountered: