Update sentry-samples/sentry-samples-android/sdkperf/README.md

romtsn · web-flow · commit ac613d64a21e · 2025-07-30T15:39:26.000+02:00
diff --git a/sentry-samples/sentry-samples-android/sdkperf/README.md b/sentry-samples/sentry-samples-android/sdkperf/README.md
@@ -75,4 +75,4 @@ Observe (Logcat or Perfetto) that the faulty behaviours are still reproducible.
 
 ### Solution
 
-We have addressed the issue in [link PR]() by not registering any of the offending integrations when the hosting app process is launched with non-foreground `importance`. We still keep observing the App Lifecycle to ensure we register the integrations when the App has been brought to foreground.
+We have addressed the issue in [#4579](https://github.com/getsentry/sentry-java/pull/4579) by not registering any of the offending integrations when the hosting app process is launched with non-foreground `importance`. We still keep observing the App Lifecycle to ensure we register the integrations when the App has been brought to foreground.

Original file line number	Diff line number	Diff line change
`@@ -75,4 +75,4 @@ Observe (Logcat or Perfetto) that the faulty behaviours are still reproducible.`
`75`	`75`
`76`	`76`	`### Solution`
`77`	`77`
`78`		-We have addressed the issue in [link PR]() by not registering any of the offending integrations when the hosting app process is launched with non-foreground `importance`. We still keep observing the App Lifecycle to ensure we register the integrations when the App has been brought to foreground.
	`78`	+We have addressed the issue in [#4579](https://github.com/getsentry/sentry-java/pull/4579) by not registering any of the offending integrations when the hosting app process is launched with non-foreground `importance`. We still keep observing the App Lifecycle to ensure we register the integrations when the App has been brought to foreground.