You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When exporting the project as APK+OBB the ScriptableSentryOptions we keep in /Resources/Sentry ends up in the OBB. That OBB might not be available just yet when the SDK tries to self-initialize.
We need to find a way to keep the options available in the actual APK - i.e. by holding a reference to it.
Ideas that come to mind: We have a SentryMonoBehaviour. But we instantiate that not via prefab but we generate a new GO and add it as a component.
Can we modify the first scene and add & save?
An idea @munkiki7 came up with: We could check whether APK + OBB is selected during the build and copy the options from the scriptable object to the main bundle i.e. the androidmanifest.xml?
When exporting the project as APK+OBB the
ScriptableSentryOptions
we keep in/Resources/Sentry
ends up in the OBB. That OBB might not be available just yet when the SDK tries to self-initialize.We need to find a way to keep the options available in the actual APK - i.e. by holding a reference to it.
Ideas that come to mind: We have a
SentryMonoBehaviour
. But we instantiate that not via prefab but we generate a new GO and add it as a component.Can we modify the first scene and add & save?
┆Issue is synchronized with this Jira Improvement by Unito
The text was updated successfully, but these errors were encountered: