sentry-java

sentry-java copied to clipboard

Problem Statement

When a user wants to set filters like beforeSend etc. they have to disable auto init and use manual init instead. There might be more options / callbacks that could be supplied this way and thus make manual init unnecessary for most use cases.

Solution Brainstorm

Maybe we can add an option for specify the name of a class which is then instantiated by the SDK e.g. using reflection.

Could also just improve docs and mention that auto init has to be replaced with manual init for certain features.

Are there any downsides to manual init? For instance, could startup crashes be missed due to a perhaps slightly later initialisation?

Maybe an option would be to use AndroidManifest metadata to declare which callbacks should be registered for these before* methods? Also add a lint rule that checks if declared callbacks exist and implement the right interface and that might be a pretty solid solution i think. (similar method to androidx-startup lib)