fix: Disable native interaction breadcrumb and tracing when targeting Android #2393
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #2380
The issue and provided logs detail that during startup the application crashes with a
StackOverflowErrorand the following callstackSo it recurses in
onWindowFocusChangedwithio.sentry.android.core.internal.gestures.WindowCallbackAdapter.onWindowFocusChangedmaybe being my red herring right now.The closes I got tho a root cause is this:
UserInteractionIntegrationgets enabled (enabled by default and not explicitely disabled by the Unity SDK)WindowCallbackwrapping is installed: The integration wraps the Activity'sWindow.CallbackwithSentryWindowCallbackInputHooksalso wrapWindow.Callback. Then, whenonWindowFocusChanged()is called we haveDecorView→ Oculus:InputHooks→ Sentry:WindowCallback→ back toInputHooks→ infinite recursion →StackOverflowErrorThe neat part is that we don't actually get any breadcrumbs out of this in our Unity game. So we can safely out-out of these integrations without losing anything.
I'll have to try to reproduce this on the actual Quest.