UnityPlayerActivity Merge Problem After Upgrading to Unity 5.2

[ironfiftynine]

I upgraded to Unity 5.2 and I was experiencing a manifest merge problem.

stderr[
Error: [Temp\StagingArea\AndroidManifest-main.xml:4, C:\Users\Felix\Documents\Work Files\IncRPG\IncRPG Repo v2\IncRPG2\Temp\StagingArea\android-libraries\ResourcesLibrary\AndroidManifest.xml:49] Trying to merge incompatible /manifest/application/activity[@name=com.unity3d.player.UnityPlayerActivity] element:
<activity
– @android:label=" @anon_76954444 /app_name"
– @android:name=“com.unity3d.player.UnityPlayerActivity”>
–
<activity
++ @android:configChanges=“fontScale|keyboard|keyboardHidden|locale|mnc|mcc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|uiMode|touchscreen”
++ @android:label=" @anon_76954444 /app_name"
++ @android:name=“com.unity3d.player.UnityPlayerActivity”>
]

I checked my Manifest files and I have only one entry of UnityPlayerActivity.

When I removed this line, everything seems to be working properly. I just want to ask, if there were changes on how the Manifest file is constructed in Unity 5.2? Is it automatically adding the UnityPlayerActivity upon build? Thank you very much.

[liortal]

Do you have only one manifest file in your project? What does it look like ? can you post it ?

[ironfiftynine]

Here are the manifest files that I found as far as I’ve searched.

<?xml version="1.0" encoding="UTF-8"?>

The other has almost no content at all.

<?xml version="1.0" encoding="utf-8"?>

Hope this helps.

[liortal]

I think that Unity has its own Android project template (with its own manifest). When you add your own manifest, it gets merged with the default one.

According to the error message, it’s having trouble merging the activity element with name = “UnityPlayerActivity”. If you are providing your own custom activity (derived from UnityPlayerActivity) i don’t think you should declare this again in the manifest.

Not 100% sure on this one, but @bitter or @Yury-Habets may be able to confirm that

[ironfiftynine]

I see. I think one or more of my imported unity packages have custom activity as you described. I’m just surprised since I don’t get these errors back in the previous versions of Unity. Thank you for your response.

[liortal]

@ironfiftynine

I see. I think one or more of my imported unity packages have custom activity as you described. I’m just surprised since I don’t get these errors back in the previous versions of Unity. Thank you for your response.

Having an activity is not an issue, the problem is that merging these activities together fails… I guess the same activity is defined more than once.

[ironfiftynine]

Can I clarify that? Do you mean that the activity is added to the manifest file just by having it extended in the java classes used by the project?

[liortal]

I meant: you should declare all activities in your AndroidManifest.xml so you could launch them and show them (Android requires that).

There is no problem with declaring new activities in the manifest - every plugin can define its own set of activities to display to the user.

The issue here, is that the manifest merging fails, since there seems to be 2 of the same activities defined somewhere.

[ironfiftynine]

Ok thanks for the clarification My apologies I’m not much acquainted with the Manifest functionality. I wonder if I missed a manifest file where the duplicate activities were defined since I seem to find all the manifest files present in the project. I just searched for AndroidManifest.xml.

[liortal]

If it is possible, you could share the project (in private) with me and i can spend a few minutes looking at it. I just did that with another forum member

Let me know if you’d like me to help out

[ironfiftynine]

Ok. Will let you know. Thank you very much.