Problem

Most SDKs submit crash events in the background to not slow down the app start. When a crash happens immediately after SDK init it will never be sent to Sentry. Such a crash is called a start-up crash.

Solution

When the app crashes shortly (x seconds) after SDK is initialized, the SDK writes a marker file to the disk indicating the app crashes shortly after the SDK init.
The SDK init function doesn't return until the start-up crash is sent to Sentry or until a configurable timeout is reached.
If the timeout is reached the init function should return and the crash submission should continue in the background.

• Develop docs: feat: Start-up crashes develop#730
• Put this into the features list https://docs.sentry.io/platforms/apple/guides/ios/

More details:

• Startup Crash: Only block Init to flush events if the app crashed on the last run sentry-dotnet#1164
• Send crash reports if the app keeps crashing sentry-cocoa#316
• Report Startup Crashes sentry-java#2277

https://sentry.zendesk.com/agent/tickets/62388