`Facebook.Unity.Settings' has already been imported error

HaakonL · Sep 10, 2017

Cloud builds are failing for us, using 2017.1.p5, Facebook SDK 7.1.10 and build target is iOS.

An assembly with the same name `Facebook.Unity.Gameroom' has already been imported. Consider removing one of the references or sign the assembly

unity-tuesday · Sep 12, 2017

Thanks, everyone, for sharing this issue that you're encountering, and for also recommending fixes and workarounds that worked for you! I'm sorry that you haven't seen one of us in this thread when you were expecting to, though we have been aware of and tracking this particular problem.

While this was an issue that first appeared a few months ago, it looked to be resolved after updating the Facebook SDK version on our end. Since then, we haven't been able to reproduce this issue, though there is clearly still an impact to you folks on here.

What would help us investigate this for those still running into the problem would be a minimal example project showing the behavior, and letting us know the steps performed to integrate the SDK. Please feel free to send this data my way if you can, as we definitely would like to see everyone up and running again!

kwikdev · Sep 17, 2017

Here are steps to reproduce the core error in Unity. You shouldn't need an example project.

1. Install Unity 5.6 (I used 5.6.3p3 on Mac) with the Facebook and Windows build options
2. Go to Build Settings -> Facebook -> Player Settings -> Publishing Settings
3. Change the Facebook SDK Setting to 7.10.1

At this point, you should see the error in the Console,

"Extension Library/FacebookSDK/Facebook.Unity.Gameroom.dll was not registered, that means it relies on default UnityExtensions settings, please register extension and apply necessary settings for it in the callback."

This error won't occur with 7.9.4 or 7.9.1 settings.

The other observation is that the Unity/PlaybackEngines/Facebook/SDK directory contains old 7.9.1 dll files. Also, that Unity gives directions to change the Player Settings mentioned above, which then produces the error.

FWIW, I haven't solved the issue myself yet, but will be attempting fixes based on this thread.

Vladimitrius · Sep 21, 2017

I confirm the same issue using 2017.1.1f1

ilmario · Sep 27, 2017

I'm also having the issue on the latest patch release, Unity 2017.1.1p3

dannyd · Sep 28, 2017

If you're going to report an error here related to the Facebook SDK you need to be specific about which error you're seeing. This thread was specifically referencing the 'Facebook.Unity.Settings' errors, and several others have been reported here which may look similar but are potentially unrelated (please start a new thread for those).

So lets look closer at this "An assembly with the same name 'Facebook.Unity.Settings' has already been imported." error. This only seems to happen when you are including a copy of the Facebook SDK in your project directly. This use case should work fine, however I want to point out a couple of things specifically.

As has been referred to in this thread already, there is a "facebookSdkVersion" stored in your ProjectSettings (you can inspect manually at ProjectSettings/ProjectSettings.asset). If you're using the built in Facebook SDK it will have some version number there (ex: "facebookSdkVersion: 7.9.4"). However, if you include a copy of the Facebook SDK in your Assets/ directory and save the project you will notice something like "facebookSdkVersion: pluginIncompatible" (meaning Unity will now try to use the Facebook SDK in your Assets/).

For cases where this error shows up in Unity Cloud Build, if you look closely at the build logs that error is only printed out during the first launch of Unity, before the actual player is built. Unity detects that you have the Facebook SDK included in your project and automatically fixes up the ProjectSettings to accomodate (i.e sets "facebookSdkVersion: pluginIncompatible"). During the actual build phase (i.e. after the "Building Unity player" message in the logs), it should be using the correct Facebook SDK. That implies that the most likely cause of this error in Unity Cloud Build is that you didn't commit your ProjectSettings changes along with your project (or didn't save your project before pushing the Facebook SDK to your repo).

This also means that error should not cause your build to fail. If you have a failed build with that error message in it, that error most likely was not the cause of the actual failure (although I can see how it is very misleading). In general, you will need to look at the full log to determine the cause of the failure. Our highlighting of errors/warnings is very basic so sometimes the actual cause may take a bit of reading back through the log to find. If you'd like me to inspect your build logs more closely, please send me a PM with a link to your build log.

@SniperED007 - your build failures are not related to the facebook sdk errors (looks to me like you need to switch to xcode 8 or higher in your target config):

[xcode] error: Invalid bitcode version (Producer: '800.0.42.1_0' Reader: '703.0.31_0')
[xcode] clang: error: linker command failed with exit code 1 (use -v to see invocation)
Click to expand...

@HaakonL - those "Facebook.Unity.Gameroom" errors look like a legitimate cause of the failure, but looks like you've built successfully since - I'm assuming you just remove the Facebook SDK from your project, or updated to a newer version?

@kwikdev - that looks like a different error unrelated to Unity Cloud Build. Have you reported it through the editor? Possibly also related to https://issuetracker.unity3d.com/is...llation-standalone-build-finishes-with-errors

@Vladimitrius and @ilmario - I didn't find any projects in UCB for you. Send me a PM if you need help there.

SniperED007 · Oct 1, 2017

@dannyd I tried switching to Xcode 9. But if I do an iOS build I still get this error:

[Unity] Initialize engine version: 2017.1.1p1 (007fc09e806c)
[Unity] UnityEngine.Debug:LogWarning(Object)
[Unity] UnityEngine.Debug:LogWarning(Object)
[Unity] UnityEngine.Debug:LogWarning(Object)
[Unity] UnityEngine.Debug:LogWarning(Object)
[Unity] WARNING: 270625200 format is not supported, decompressing texture
[Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-firstpass.dll
[Unity] Compilation failed: 1 error(s), 0 warnings
[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
[Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[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
[Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[Unity] Compilation failed: 1 error(s), 0 warnings
Unhandled Exception: System.NullReferenceException: DownloadHandler has already been destroyed
[usbmuxd] Error:
[Unity] Initialize engine version: 2017.1.1p1 (007fc09e806c)

ilmario · Oct 2, 2017

dannyd said: ↑

If you're going to report an error here related to the Facebook SDK you need to be specific about which error you're seeing.
...
@Vladimitrius and @ilmario - I didn't find any projects in UCB for you. Send me a PM if you need help there.
Click to expand...

Sorry for not being clear. I'm not using Cloud build, and I havent added Facebook SDK manually either.

I was using the inbuilt version with the newer SDK : 7.10.1, but downgraded to 7.9.4, which seemed to have fixed the error I was seeing. I will keep it downgraded until it works reliable in Unity.

I though that this error was related to weird Facebook Gameroom-issues, such as Standalone resolution settings not being respected on game start. The first scene (which last only a few seconds, preloading the next one), is shown up tiny, like 1/30 of the screen in left upper corner. The next scene works almost ok in normal screen size, except the input is weirdly connected to the tiny screen area of the previous screen. The input problem fixes itself if the gameroom window is manually resized in any way during the preloading scene or the next one. Probably I need to trigger this resizing somehow in a script.

This seems to occur regardless of Standalone resolution / full screen settings, and it happens only in Gameroom, not other Mac/Win builds. This particular problem might also be connected to the Adventure Creator asset.

However, this issue also persists regardless of the error related to the Facebook SDK, so it's not connected.

HashbangGames · Oct 3, 2017

I found a new solution for this problem. Unity is supposed to automatically disable this namespace when you install the Facebook SDK manually. However it is failing to disable it.

1> Import latest FacebookSDK
2> Click on FacebookSDK --> Plugins -->Settings-->Facebook.Unity.Settings in the project
3> Uncheck Any Platform, then unselect all from Exclude ( this is what I did, not sure if it is relevant )
4> Let it recompile ( you will get errors )
5> Delete the FacebookSDK from your project
6> Re-Install FacebookSDK & Restart Unity

This worked for me, I now have no errors and the FacebookSDK works fine because Unity Detected the FacebookSDK and disabled the Namespace Facebook.Unity.Settings

Please post if this solution worked for you, I don't know 100% that this solution works every time, it just worked for me after fudging with it for about 10 minutes.

htdreams · Oct 26, 2017

I was lost for several days without any clue on how to resolver this issue... thanks #blumersolutions, your "recipe" worked flawlesly for me :-D

lukos · Nov 29, 2017

I have reported this bug with very easy steps to replicate. Hope Unity guys can action this quick https://fogbugz.unity3d.com/default.asp?972435_qt4o59q5mefg3o30

lukos · Dec 4, 2017

@dannyd We really need this issue sorted, or at least info on a workaround.
Please push engineers to look into this. Its very easy to replicate with the steps from my report https://fogbugz.unity3d.com/default.asp?972435_qt4o59q5mefg3o30

Claytonious · Dec 5, 2017

SniperED007 said: ↑

Pretty shocking the support level from Unity on this issue.
Click to expand...

Has anybody on this thread actually reported a bug with the bug reporter?

rankornfeld · Dec 7, 2017

I just gave up on cloud build because of this issue and other issues that were sometimes appearing out of nowhere..

I think cloud build is a great idea, but has a lot of problems.

Moved to local iOS builds, everything is working great

SniperED007 · Dec 11, 2017

Turns out the error ALWAYS happens in the iOS cloud build no matter what you do if you have Facebook SDK installed, however, the build doesn't actually fail because of the error, it just looks that way because it's the error right at the top.
I got my build to finally work after updating a 3rd party plugin I use that was causing some other error.

levi9687 · Dec 26, 2017

blumersolutions said: ↑

I've found a workaround..

Close Unity Editor

Remove the Facebook folder in C:\Program Files\Unity\Editor\Data\PlaybackEngines

Remove the FacebookSDK folder in your project's Library folder

Import FacebookSDK

Profit?

Click to expand...

i thought this would work for me also but still no luck I cant find the original dll the error refers to. so annoying

teexiii · Jan 5, 2018

blumersolutions said: ↑

I've found a workaround..

Close Unity Editor

Remove the Facebook folder in C:\Program Files\Unity\Editor\Data\PlaybackEngines

Remove the FacebookSDK folder in your project's Library folder

Import FacebookSDK

Profit?

Click to expand...

This should work!

lukos · Jan 31, 2018

@dannyd This issue still persists on 2017.3.0.f3 We really need this fixed. Noone seems to care about it. i have submitted the bug report that wasn't even reviewed. Exact steps to reproduce are here

https://fogbugz.unity3d.com/default.asp?972435_qt4o59q5mefg3o30

pixelsplit · Feb 2, 2018

A better fix than removing facebook folders is opening the ProjectSettings.asset with your prefered editor and replacing facebookSdkVersion: x with facebookSdkVersion: plugin

Jonathanlive · Feb 2, 2018

@PaulECoyote Nice!!!

then I saved while Unity editor was closed
facebookSdkVersion: plugin

I did the samething above and this works for me!!!
Many thanks bro

My unity version is: 2017.3.0f3
My facebook plugin version is: 7.11.0.0

PaulECoyote said: ↑

Yep - made the same change using text editor in ./ProjectSettings/ProjectSettings.asset

Funny thing is that is was set to
facebookSdkVersion: 7.10

then I saved while Unity editor was closed
facebookSdkVersion: plugin

But inspecting the file again it has gone back to
facebookSdkVersion: 7.9.4

... since a build.

Going in to the settings I get a little info area telling me to go in to player settings and set it to 7.10.1
I think that's what I did when I got in to this mess in the first place.

Also my app id and upload token also disappeared after making that "facebookSdkVersion: plugin" change.

So as I've got the thing building and deploying again I'm going to leave it as-is for the moment.

I didn't see a "plugin" option in the drop-down menu so I suspect when it encounters "plugin" it just resets down to that default 7.9.4 and clears the other settings. Absolutely no proof on that though.
Click to expand...

lukos · Feb 21, 2018

@zkw This wont work for cloud build mine is set as plugin and still same issue

spacepluk · Feb 23, 2018

This is now working for me on UCB without any workarounds. I'm building for Android and iOS with Unity 2017.3.1f1 and Facebook SDK 7.10.0 (later versions of FBSDK fail to link on iOS).

I still see this errors in the log, but the builds finish successfully and they work:

...
4707: [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
4708: [Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
4709: [Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
...

I had to clean up the library cache before it started building successfully.

topXight · May 25, 2018

We started to see this error after updating Facebook Unity SDK to 7.12.

Compilation failed: 1 error(s), 0 warnings
29: [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
30: [Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
31: [Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
32: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp.dll

Unlike previous posts for us the UCB just fails to build past this error.

Is there an official response from Unity on how to resolve this? We have tried all of the remedies listed above and nothing seems to work for us.

Claytonious · May 29, 2018

pfleetwood22 said: ↑

fixed this problem by changing the ProjectSettings.asset file value for "facebookSdkVersion" to "plugin"
Click to expand...

I regularly have to do this on every new project that used the downloaded Facebook SDK from https://developers.facebook.com/docs/unity (which we use for Facebook features on Android and iOS targets).

topXight · Jun 1, 2018

@Claytonious Thank for for pointing this. I did try this solution but it gave me a parse error on UCB. So I am not sure this works anymore (Unity 2014.7.x or above). Anyway with the gradle builds this error is getting ignored. And the binaries work fine. So I am going to ignore until something stops working.

And just as FYI I also noticed in the log that the compatible SDK versions for Unity 2017.4.1f1 are 7.9.x and 7.10.x. So I also downgraded FB SDK to 7.10.x.

Deleted User · Jun 15, 2018

Changing the facebook value of ProjectSettings to plugin isn't working for me. Even though it says plugin Unity is still always re-adding facebook related .dll files to the library folder.

kwikdev · Jun 16, 2018

I see what @manoke sees, with these repro steps:

1. Create empty project in Unity 2017.4.5f1 or 2018
2. Build on Unity Cloud Build for Android successfully
2. Add FacebookSDK 7.12
3. Build fails with errors...

[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
[Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[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
[Unity] Library/FacebookSDK/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)
[Unity] Assets/FacebookSDK/Plugins/Settings/Facebook.Unity.Settings.dll (Location of the symbol related to previous error)

Is there a known patch-fix to get Android up and running? The above haven't worked in Unity 2017.4.5 or 2018.

Spaniel · Jul 26, 2018

tridentcanadainc said: ↑

Great tip, worked for us.
Unity 5.6.1.f1, FB SDK 7.10.0
Click to expand...

Worked for us as well: changing the version in ProjectSettings.asset to "plugin"

NanoMath · Aug 8, 2018

so which Unity version should I use to work with Facebook SDK ? which Facebook SDK one ? I've fixed error by removing Facebook library and PlaybackEngine but Unity 2017.4.2.f2 (64bit) cannot build Android app correctly.

Unity support team hope you will help and close this issue for all other developers let's see, the time will show us !

Speedrun-Labs · Aug 15, 2018

both solutions mentioned above seemed to work for me on Unity Cloud Build....

1 go to /ProjectSettings/ProjectSettings.asset
2 set "facebookSdkVersion: plugin" or "facebookSdkVersion: 7.13.0" (or current version)

apparently Unity has some Facebook dll files locally, and Unity Cloud Build has some in their "Library" folder as well

Unity should fix this issue, goddamnit! >: (

renman3000 · Aug 30, 2018

Wow. Still a bug.

renman3000 · Sep 5, 2018

I just deleted said file and it appears to have worked.
I was hesitant as it claimed 2 existed, but only 1 was shown in the search.

Anyhoo, hopefully that is it!

hamza37 · Sep 19, 2018

I know this is late .........unity add facebook sdk by default which can be found in Library folder of the project.Delete Facebook folder from Library folder and error will be gone.This worked for me.

Ki4Chan · Oct 4, 2018

I am getting Facebook.Unity.Setting has already been imported.

First I tried to delete the one which is present in "Library", but after that, I get "Facebook.Unity.Setting" is missing error, though the other "Facebook.Unity.Setting" was already there.

After that, I tried to delete the one imported while importing Facebook SDK but after deleting this one, I can not access "Facebook > Edit Settings".

EDIT: Closing and then reopening Unity resolved this problem for me.

spacepluk · Oct 4, 2018

I'm working on a new project and I'm still having this problem on Cloud Build with the latest Facebook SDK (7.13 at the moment). I tried setting the version to "plugin" in ProjectSettings but that didn't help.

Reverting to 7.10 and a clean build "fixed" it again, but I'm not happy about using a version of the SDK that's a year old.

yunknuy · Feb 2, 2019

blumersolutions said: ↑

Same here. This is really annoying. Is there any workaround for this? Do I need to reinstall Unity without game room?!
Click to expand...

Thank you so much !

Jeremy-Lv · Mar 16, 2019

Spaniel said: ↑

Worked for us as well: changing the version in ProjectSettings.asset to "plugin"
Click to expand...

How to Change ?? Only Change the version num ?? such as "facebookSdkVersion: 7.15.1" or "facebookSdkVersion: plugin" ? ,but it both not worked for me....

alexman · Apr 8, 2019

I am using 2018.2.20 and using cloud build, encountered this problem, fixed it by changing the projectsettings.asset config file manually, change the facebookSdkVersion from 7.9.6 to plugin, worked

Thaina · Jun 17, 2019

Happen to caught this issue with 2019.2.0b5

marauderkr · Aug 6, 2019

We got the same problem with 2019.2.0f1 and cloud build.

Local builds work without any problems using Facebook SDK 7.13.
But Cloud Build throws errors and fails:

Code (CSharp):

[Unity] [API Updater] Update finished with error in 30336 ms (0/31 assemblie(s) updated).

17: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Unity.2D.Tilemap.Editor.dll

18: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity.Settings' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.Settings.dll') or sign them to enable side-by-side.

19: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.dll') or sign them to enable side-by-side.

and ending with:

Code (CSharp):

Fatal Error! It looks like another Unity instance is running with this project open.

63: [Unity] DisplayProgressbar: Unity license

64: [Unity] Fatal Error! It looks like another Unity instance is running with this project open.

65: publishing finished successfully.

66: error: attach failed: Error 1

67: Finished: FAILURE

setting ProjectSettings.asset line "facebookSdkVersion" to "plugin" or "7.13.0" as well as using CLEAN BUILD in cloudbuild did NOT help.

grimjim · Aug 6, 2019

marauderkr said: ↑

We got the same problem with 2019.2.0f1 and cloud build.

Local builds work without any problems using Facebook SDK 7.13.
But Cloud Build throws errors and fails:

Code (CSharp):

[Unity] [API Updater] Update finished with error in 30336 ms (0/31 assemblie(s) updated).

17: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Unity.2D.Tilemap.Editor.dll

18: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity.Settings' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.Settings.dll') or sign them to enable side-by-side.

19: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.dll') or sign them to enable side-by-side.

and ending with:

Code (CSharp):

Fatal Error! It looks like another Unity instance is running with this project open.

63: [Unity] DisplayProgressbar: Unity license

64: [Unity] Fatal Error! It looks like another Unity instance is running with this project open.

65: publishing finished successfully.

66: error: attach failed: Error 1

67: Finished: FAILURE

setting ProjectSettings.asset line "facebookSdkVersion" to "plugin" or "7.13.0" as well as using CLEAN BUILD in cloudbuild did NOT help.
Click to expand...

Same here with 7.15 and 7.17

Regarding the "Fatal Error! It looks like another Unity instance is running with this project open." I would start a clean build that fixes that.

Code (CSharp):

[Unity] [API Updater] Update finished with error in 30336 ms (0/31 assemblie(s) updated).

17: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Unity.2D.Tilemap.Editor.dll

18: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity.Settings' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.Settings.dll') or sign them to enable side-by-side.

19: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.dll') or sign them to enable side-by-side.

This is not the real issue I think its probably something like this.

17276: [Unity] Assembly 'Assets/FacebookSDK/Plugins/Facebook.Unity.dll' will not be loaded due to errors:

17277: [Unity] Unable to resolve reference 'UnityEngine.UI'. Is the assembly missing or incompatible with the current platform?

Check your full log.
I think its the facebook SDK I'm going to try now a new project just with the latest SDK in it and run it through cloud build

The issue is already being discussed here https://forum.unity.com/threads/ui.673504/

chadq · Aug 13, 2019

marauderkr said: ↑

We got the same problem with 2019.2.0f1 and cloud build.

Local builds work without any problems using Facebook SDK 7.13.
But Cloud Build throws errors and fails:

Code (CSharp):

[Unity] [API Updater] Update finished with error in 30336 ms (0/31 assemblie(s) updated).

17: [Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Unity.2D.Tilemap.Editor.dll

18: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity.Settings' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.Settings.dll') or sign them to enable side-by-side.

19: [Unity] error CS1704: An assembly with the same simple name 'Facebook.Unity' has already been imported. Try removing one of the references (e.g. '/UNITY_PATH/Unity/Unity-2019_2_0f1/PlaybackEngines/Facebook/SDK/7.9.4/Facebook.Unity.dll') or sign them to enable side-by-side.

and ending with:

Code (CSharp):

Fatal Error! It looks like another Unity instance is running with this project open.

63: [Unity] DisplayProgressbar: Unity license

64: [Unity] Fatal Error! It looks like another Unity instance is running with this project open.

65: publishing finished successfully.

66: error: attach failed: Error 1

67: Finished: FAILURE

setting ProjectSettings.asset line "facebookSdkVersion" to "plugin" or "7.13.0" as well as using CLEAN BUILD in cloudbuild did NOT help.
Click to expand...

I'm having the same issue with my project after a 2019.2 update, even after a clean build and update to Facebook SDK 7.17.2. Has anyone else had any luck with this?

studentutu · Aug 13, 2019

Same issue with Cloud build on IOS and Android! Unity 2019.2.0f1 with Facebook SDK 7.17.1/7.17.2!

studentutu · Aug 13, 2019

studentutu said: ↑

Same issue with Cloud build on IOS and Android! Unity 2019.2.0f1 with Facebook SDK 7.17.1/7.17.2!
Click to expand...

dannyd said: ↑

If you're going to report an error here related to the Facebook SDK you need to be specific about which error you're seeing. This thread was specifically referencing the 'Facebook.Unity.Settings' errors, and several others have been reported here which may look similar but are potentially unrelated (please start a new thread for those).

So lets look closer at this "An assembly with the same name 'Facebook.Unity.Settings' has already been imported." error. This only seems to happen when you are including a copy of the Facebook SDK in your project directly. This use case should work fine, however I want to point out a couple of things specifically.

As has been referred to in this thread already, there is a "facebookSdkVersion" stored in your ProjectSettings (you can inspect manually at ProjectSettings/ProjectSettings.asset). If you're using the built in Facebook SDK it will have some version number there (ex: "facebookSdkVersion: 7.9.4"). However, if you include a copy of the Facebook SDK in your Assets/ directory and save the project you will notice something like "facebookSdkVersion: pluginIncompatible" (meaning Unity will now try to use the Facebook SDK in your Assets/).

For cases where this error shows up in Unity Cloud Build, if you look closely at the build logs that error is only printed out during the first launch of Unity, before the actual player is built. Unity detects that you have the Facebook SDK included in your project and automatically fixes up the ProjectSettings to accomodate (i.e sets "facebookSdkVersion: pluginIncompatible"). During the actual build phase (i.e. after the "Building Unity player" message in the logs), it should be using the correct Facebook SDK. That implies that the most likely cause of this error in Unity Cloud Build is that you didn't commit your ProjectSettings changes along with your project (or didn't save your project before pushing the Facebook SDK to your repo).

This also means that error should not cause your build to fail. If you have a failed build with that error message in it, that error most likely was not the cause of the actual failure (although I can see how it is very misleading). In general, you will need to look at the full log to determine the cause of the failure. Our highlighting of errors/warnings is very basic so sometimes the actual cause may take a bit of reading back through the log to find. If you'd like me to inspect your build logs more closely, please send me a PM with a link to your build log.

@SniperED007 - your build failures are not related to the facebook sdk errors (looks to me like you need to switch to xcode 8 or higher in your target config):
ArgumentException: The Assembly Facebook.Unity.Settings is referenced by Facebook.Unity ('Assets/FacebookSDK/Plugins/Facebook.Unity.dll'). But the dll is not allowed to be included or could not be found.
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
Cloud build fails on IOS and Android! Unity 2019.2.0f1 with Facebook SDK 7.17.1/7.17.2!
You can just remove the Facebook target from 2019.2! Or do the same as in previous versions of unity - why do you include this target by default?

@HaakonL - those "Facebook.Unity.Gameroom" errors look like a legitimate cause of the failure, but looks like you've built successfully since - I'm assuming you just remove the Facebook SDK from your project, or updated to a newer version?

@kwikdev - that looks like a different error unrelated to Unity Cloud Build. Have you reported it through the editor? Possibly also related to https://issuetracker.unity3d.com/is...llation-standalone-build-finishes-with-errors

@Vladimitrius and @ilmario - I didn't find any projects in UCB for you. Send me a PM if you need help there.
Click to expand...

michael_looply · Aug 13, 2019

For others facing this issue:

Code (CSharp):

17276: [Unity] Assembly 'Assets/FacebookSDK/Plugins/Facebook.Unity.dll' will not be loaded due to errors:

17277: [Unity] Unable to resolve reference 'UnityEngine.UI'. Is the assembly missing or incompatible with the current platform?

Can be circumvented by turning off reference validation in DLL import settings.

There's another issue with Cloud Build compiling against both the 7.9.4 SDK and any SDK in the Assets directory that I've outlined here: https://forum.unity.com/threads/del...support-unity-2019-2-0f1.727052/#post-4852568

Building locally is still possible as long as the Facebook Playback Engine is not installed for your local instance of the 2019.2.0f1 editor.

Alexhator · Aug 24, 2019

tridentcanadainc said: ↑

Great tip, worked for us.
Unity 5.6.1.f1, FB SDK 7.10.0
Click to expand...

Sorry, but... what should I do? I am a bit new on this. Please, explain a little more.

Search Unity

Unity ID

Useful Searches

`Facebook.Unity.Settings' has already been imported error

Unity Technologies

Unity Technologies

Guest