fix(logs): Add missing App Start logs when the span is dropped (#3861)

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## Unreleased
+
+### Fix
+
+- Add missing logs to dropped App Start spans ([#3861](https://github.com/getsentry/sentry-react-native/pull/3861))
+
 ## 5.23.0
 
 ### Features

src/js/tracing/reactnativetracing.ts

@@ -422,11 +422,18 @@ export class ReactNativeTracing implements Integration {
 
  const appStart = await NATIVE.fetchNativeAppStart();
 
- if (!appStart || appStart.didFetchAppStart) {
+ if (!appStart) {
+ logger.warn('[ReactNativeTracing] Not instrumenting App Start because native returned null.');
+ return;
+ }
+
+ if (appStart.didFetchAppStart) {
+ logger.warn('[ReactNativeTracing] Not instrumenting App Start because this start was already reported.');
  return;
  }
 
  if (!this.useAppStartWithProfiler) {
+ logger.warn('[ReactNativeTracing] `Sentry.wrap` not detected, using JS context init as app start end.');
  this._appStartFinishTimestamp = getTimeOriginMilliseconds() / 1000;
  }
 
@@ -450,14 +457,15 @@ export class ReactNativeTracing implements Integration {
  private _addAppStartData(transaction: IdleTransaction, appStart: NativeAppStartResponse): void {
  const appStartDurationMilliseconds = this._getAppStartDurationMilliseconds(appStart);
  if (!appStartDurationMilliseconds) {
- logger.warn('App start was never finished.');
+ logger.warn('[ReactNativeTracing] App start end has not been recorded, not adding app start span.');
  return;
  }
 
  // we filter out app start more than 60s.
  // this could be due to many different reasons.
  // we've seen app starts with hours, days and even months.
  if (appStartDurationMilliseconds >= ReactNativeTracing._maxAppStart) {
+ logger.warn('[ReactNativeTracing] App start duration is over a minute long, not adding app start span.');
  return;
  }