From e0904ef6b8b510e9739820aa29379b074b26e237 Mon Sep 17 00:00:00 2001 From: Philipp Hofmann Date: Wed, 24 Apr 2024 17:39:22 +0200 Subject: [PATCH] fix: Remove wrong error log in CoreDataTracker (#3894) The SentryCoreDataTracker logged an error for fetch requests when no span was bound to the scope, which happens when no auto-generated transaction is running. This is fixed now by removing that log. Fixes GH-3586 --- CHANGELOG.md | 1 + Sources/Sentry/SentryCoreDataTracker.m | 3 --- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0cf255edf6e..2cd2870a716 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,7 @@ - Crash due to a background call to -[UIApplication applicationState] (#3855) - Save framework without UIKit/AppKit as Github Asset for releases (#3858) - Fix crash associated with runtime collision in global C function names (#3862) +- Remove wrong error log in SentryCoreDataTracker (#3894) ## 8.24.0 diff --git a/Sources/Sentry/SentryCoreDataTracker.m b/Sources/Sentry/SentryCoreDataTracker.m index 703ed436e26..11474ca3eac 100644 --- a/Sources/Sentry/SentryCoreDataTracker.m +++ b/Sources/Sentry/SentryCoreDataTracker.m @@ -48,9 +48,6 @@ - (NSArray *)managedObjectContext:(NSManagedObjectContext *)context SENTRY_LOG_DEBUG(@"SentryCoreDataTracker automatically started a new span with " @"description: %@, operation: %@", fetchSpan.description, fetchSpan.operation); - } else { - SENTRY_LOG_ERROR( - @"managedObjectContext:executeFetchRequest:error:originalImp: fetchSpan is nil."); } NSArray *result = original(request, error);