Unalbe to merge androidManifest with Facebook sdk

Unity Engine
,
1

Hi,
everytime I try to build i get this Error:
Attribute activity#com.facebook.FacebookActivity@theme value=(@android:style/Theme.Translucent.NoTitleBar) from AndroidManifest.xml:32:13-72
is also present at AndroidManifest.xml:32:13-63 value=( @ /com_facebook_activity_theme).
Suggestion: add ‘tools:replace=“android:theme”’ to element at AndroidManifest-main.xml:29:9-32:75 to override.

I cannot see which manifest should i modify ?

2

The manifest file which you have to edit should be in Assets/Plugins/Android/AndroidManifest.xml. If your project does not have this file, then the default manifest provided by Unity is used. You can copy it from the Unity install directory Unity/PlaybackEngines/AndroidPlayer/Apk/AndroidManifest.xml, place it in Assets/Plugins/Android/AndroidManifest.xml in your project and do the suggested modifications.

3

Hello,
I’m getting this:

[Unity] Initialize engine version: 5.6.0f3 (497a0f351392)
2: [Unity] -----CompilerOutput:-stdout–exitcode: 1–compilationhadfailure: True–outfile: Temp/Assembly-CSharp-firstpass.dll
3: [Unity] Compilation failed: 1 error(s), 0 warnings
4: [Unity] error CS1704: An assembly with the same name Facebook.Unity.Settings' has already been imported. Consider removing one of the references or sign the assembly 5: [Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error) 6: [Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error) 7: [Unity] error CS1704: An assembly with the same name Facebook.Unity.Settings’ has already been imported. Consider removing one of the references or sign the assembly
8: [Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
9: [Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)

any clue?

Regards.

4

@Eidern after the build fails, you can navigate to this folder \Temp\StagingArea.
There, you will find all processed manifests (main manifest, manifests from libraries you’re using). It should be easier to track down which is the problematic manifest(s).

1 Like
5

Thanks, it appears that the build failed because of an older install of a plugin that coexisted with a new version instead of being removed :confused:
Thanks

1 Like