-
Notifications
You must be signed in to change notification settings - Fork 69
Description
Title
Adjust SDK 5.4.5 forces UnityPlayerActivity in AndroidManifest, but Unity now uses UnityPlayerGameActivity by default
Description
Hi Adjust team,
When integrating Adjust SDK 5.4.5 into a Unity project, I noticed that the SDK automatically modifies the AndroidManifest.xml and injects the following activity declaration:
<activity
android:name="com.unity3d.player.UnityPlayerActivity"
android:label="@string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<meta-data android:name="unityplayer.UnityActivity" android:value="true" />
</activity>However, modern Unity versions no longer use UnityPlayerActivity.
Instead, they use UnityPlayerGameActivity as the default main activity.
What I found so far
-
Adjust provides a prefab field called "Custom Android Activity Name", but:
- It only takes effect when AndroidUriSchemes are configured.
- It only works if
Plugins/Android/AndroidManifest.xmlalready exists — but by default Unity projects do not include an AndroidManifest inside Plugins.
-
As a result, Adjust still forces
UnityPlayerActivityinto the final manifest, even though Unity no longer uses it.
My questions
-
Does Adjust officially support
UnityPlayerGameActivity? -
If Adjust is supposed to work with
UnityPlayerGameActivity, what is the correct setup?- How can we prevent the SDK from injecting
UnityPlayerActivity? - Is there a recommended manifest entry or override configuration?
- How can we prevent the SDK from injecting
Right now, Adjust seems to enforce an outdated activity class and ignores Unity’s current default activity, causing integration issues.
Thanks in advance, and looking forward to your clarification!