Markus Hintersteiner
Markus Hintersteiner
@bitsandfoxes is this something you want to take a look at?
In a first iteration we could just ask the user for the manifest path, which contains the main activity.
Let's re-priortize this once we have more stats and see how often the main-intent can not be found.
We definitely can look into the new-ish behavior when multiple activities are on the stack and a crash just closes the topmost one, or in other words the app is...
The SDK itself does not attach a logcat.log file, so this seems to stem from the symbol collector attaching this manually and not providing a proper mime-type. Moving issue over...
Could make sense to add it to our [os context protocol defined here](https://develop.sentry.dev/sdk/event-payloads/contexts/#os-context).
@AndroidDeveloperLB The `ApplicationStartInfo` can be received by registering a `ActivityManager.addApplicationStartInfoCompletionListener` hook, [see the docs](https://developer.android.com/reference/android/app/ActivityManager#addApplicationStartInfoCompletionListener(java.util.concurrent.Executor,%20java.util.function.Consumer%3Candroid.app.ApplicationStartInfo%3E)) for more details.
@AndroidDeveloperLB I think what you're looking for is `Activity.getReferrer`([link](https://developer.android.com/reference/android/app/Activity.html#getReferrer())). In which situations would this be useful for you?
Maybe there's a way to have one repository per SDK / maven artifact to lower the chance of conflicts.
Let's print a `warning` in case the release couldn't be normalized.