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
fix: Return SentryNoOpSpan when starting a child on a finished transaction (#2239)
* fix: Starting a new span on a finished span results in a SentryNoOpSpan
Closes#1624
* Add a test
* Changelog
* Fix test
* Fix test
* Move changelog
(this is such an annoying manual thing to keep fixing)
* Whoops
* Fix tests (why does this work locally?)
* Clean up
* Use self.tracer.isFinished
* Add testStartGrandChildOnFinishedSpan
* Move logic to SentryTracer
Copy file name to clipboardExpand all lines: Tests/SentryTests/Integrations/SentryBaseIntegrationTests.swift
-7Lines changed: 0 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -48,11 +48,4 @@ class SentryBaseIntegrationTests: XCTestCase {
48
48
XCTAssertFalse(result)
49
49
XCTAssertEqual(["Sentry - debug:: Not going to enable SentryTests.MyTestIntegration because enableAutoSessionTracking is disabled."], logOutput.loggedMessages)
XCTAssertTrue(logOutput.loggedMessages.contains("Sentry - warning:: Starting a child on a finished span is not supported; it won\'t be sent to Sentry."))
XCTAssertTrue(logOutput.loggedMessages.contains("Sentry - warning:: Starting a child on a finished span is not supported; it won\'t be sent to Sentry."))
0 commit comments