fix: Decouple screen tracking from performance tracing in fragments

Screen name updates on scope should work independently of whether
performance tracing is enabled.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: romtsn

sentry-android-fragment/src/main/java/io/sentry/android/fragment/SentryFragmentLifecycleCallbacks.kt

@@ -163,7 +163,7 @@ public class SentryFragmentLifecycleCallbacks(
     fragmentsWithOngoingTransactions.containsKey(fragment)
 
   private fun startTracing(fragment: Fragment) {
-    if (!fragment.isAdded || !isPerformanceEnabled || isRunningSpan(fragment)) {
+    if (!fragment.isAdded) {
       return
     }
 
@@ -173,6 +173,10 @@ public class SentryFragmentLifecycleCallbacks(
       scopes.configureScope { it.screen = fragmentName }
     }
 
+    if (!isPerformanceEnabled || isRunningSpan(fragment)) {
+      return
+    }
+
     var transaction: ISpan? = null
     scopes.configureScope { transaction = it.transaction }
 

sentry-android-fragment/src/test/java/io/sentry/android/fragment/SentryFragmentLifecycleCallbacksTest.kt

@@ -291,6 +291,22 @@ class SentryFragmentLifecycleCallbacksTest {
     verify(fixture.scope).screen = "androidx.fragment.app.Fragment"
   }
 
+  @Test
+  fun `When performance is disabled, it should still update screen name`() {
+    val sut =
+      fixture.getSut(enableAutoFragmentLifecycleTracing = false, enableScreenTracking = true)
+
+    sut.onFragmentViewCreated(
+      fixture.fragmentManager,
+      fixture.fragment,
+      view = mock(),
+      savedInstanceState = null,
+    )
+
+    verify(fixture.scope).screen = "androidx.fragment.app.Fragment"
+    verify(fixture.transaction, never()).startChild(any<String>(), any<String>())
+  }
+
   @Test
   fun `When fragment view is created after onFragmentCreated, it should not start a second span`() {
     // Normal path: onFragmentCreated already started the span; onFragmentViewCreated is a no-op