Fix: don't crash app when applicationContext is not available

[buenaflor]

📜 Description

lateinit crashes the application if not set for example when using the Phoenix library

When calling ProcessPhoenix.triggerRebirth(context) the app is actually restarted twice and only one the second time the content providers are loaded.

💡 Motivation and Context

Fixes #212

💚 How did you test it?

Manual, SentryContextProviderTest

📝 Checklist

You have to check all boxes before merging:

• I reviewed the submitted code.
• I added tests to verify the changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• Review from the native team if needed.
• No breaking change or entry added to the changelog.

🔮 Next steps

[romtsn]

tbh, I am a bit hesitant with this approach, because if someone removes our SentryContextProvider for whatever reason (as mentioned here for example), the SDK init will silently fail and the users wont be aware of that. Perhaps there's a better way to handle ProcessPhoenix specifically?

[romtsn]

is the problem that ContentProviders are not loaded at all, or that context or context.applicationContext is null?

[buenaflor]

I've set up some debug logs and the application init is triggered twice and during the the content provider is not loaded before so applicationContext crashes due to lateinit but on the second load it works fine because the content provider has already set the context:

Rebirth triggered now (click button that runs rebirth)
Try init sentry android: app context null (app tries to restart process, content provider is not triggered before)
Content provider loaded (now content provider is triggered)
Try init sentry android: app context sample.kmp.app.android.SentryApplication@d0c4ab0 (now we have access to app context)

[romtsn]

ok, I see, I guess there's no many ways around it anyway. After we implement logging that should help also 👍