[FIXED] UCB Team - Android Builds with the Facebook SDK are failing 17th March

When and where was this fixed? We're having this problem in 5.5.2p2 as of today.

 

Hi, @SophiaC.

We use Jenkins to build our game, and are running into the same issue. Can you elaborate on how you solved the problem for Unity Cloud Build?

 

Can you elaborate further than just Gradle and the Android Keystore? I'm happy to muck around in shell scripts and Unity Editor code to fix the problem, but it's very opaque and since it doesn't happen when building through the editor itself (only via the command line), it's very tough for me to fix it without more information.

 

The weird part (to me, at least) is that I have a debug.keystore file on my build machine under %HOMEPATH%\.android (Windows box).

Building inside the editor itself happens just fine using the exact same method call I use when building via batch mode, but building on the command line using batch mode fails.

Update: Looks like I fixed it. This obviously isn't really a problem for Cloud Build, but if anyone is having this issue with Jenkins, it might be because Jenkins strips your environment before builds. The Facebook Unity plugin explicitly checks for the HOMEPATH and HOMEDRIVE environment variables when trying to find the debug keystore. However, since Jenkins has stripped those variables before its run, the plugin fails to find the file and aborts the build.

The solution, in this case, was to use the EnvInject Jenkins plugin to re-inject the variables before the build. Just make sure that when you do, you escape the backslash (if you're using Windows as your Jenkins slave) for the path. For example, your EnvInject configuration might look like this:

HOMEDRIVE=C:
HOMEPATH=\\Users\\YourUsername

 

I am having this in 2017.3

 

Having that as well now after switching to 2017.3

 

Still having it. Did someone find the solution?

 

I just added the debug.keystore file to this path: "C:\Users\<user>\.android" and the error went away.

Attached the file inside a zip file in case someone needs it.

 

I am having this same error Unity 2017.3 Where is the debug.keystore file kept? I can't find it. Any help is appreciated.

 

drag the above file provided into the .android folder. this solved the issue for me.
i am not sure how you access the android folder on windows but on mac just type

open ~/.android/ into the terminal and it should take you to the folder.

 

Dude you are AWESOME!!!

 

I have same error. But build grandle not fix. I use unity 2017.3 , FB SDK 7.13.0 , Admob v3.13.1.
Output log:

Your Android setup is not correct. See Settings in Facebook menu.
UnityEngine.Debug:LogError(Object)
Facebook.Unity.Editor.XCodePostProcess:OnPostProcessBuild(BuildTarget, String)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

Error building Player: Your Android setup is not correct. See Settings in Facebook menu.

Build completed with a result of 'Failed'

UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

UnityEditor.BuildPlayerWindow+BuildMethodException: 2 errors
at UnityEditor.BuildPlayerWindow+DefaultBuildMethods.BuildPlayer (BuildPlayerOptions options) [0x0020e] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:181
at UnityEditor.BuildPlayerWindow.CallBuildMethods (Boolean askForBuildLocation, BuildOptions defaultBuildOptions) [0x00065] in C:\buildslave\unity\build\Editor\Mono\BuildPlayerWindowBuildMethods.cs:88
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

@SophiaC I am having this issue in Unity 2018.2.0f2. What should I do now?

 

@Mewada-Neil
me too

 

i have this follow error please anybody have a solution . i use unity 2018.1 and facebook sdk 7.13.0

Your Android setup is not correct. See Settings in the Facebook menu.
UnityEngine.Debug:LogError(Object)
Facebook.Unity.Editor.XCodePostProcess:OnPostProcessBuild(BuildTarget, String)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Having the same problem. Unity 2017.2.0f2 and originally with 7.10.1, but I have tried updating to 7.13.0 with same result.


In the facebook settings window, it says:
"Your android debug keystore file is missing. You can create new one by creating and building empty Android project in Eclipse."

I have done a lot of different things to be absolutely sure that I have the debug.keystore. It even said that the password was wrong of file had been tampered with at some point. So it can find it, but the error message might be wrong?

 

Having the same problem. Unity 2018.3, any fix?

 

Same issue with 2018.3.6f1

 

I have the same problem

Your Android setup is not correct. See Settings in Facebook menu.
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

My game is compiled, but it does not open, it tells me that the application has been closed and that it continues to fail.

Can someone help me?

Thank you

 

2018.3.6f1 still happen

 

me too

 

This is happeneing to me too. 2018.3

 

This is happeneing to me too. 2018.3, but 2018.2.6.f1 is not. I am using Facebook SDK 7.15.1.

 

For my case (window), base on Peter77's suggest (link), there is a "'keytool' is not recognized as an internal or external command" error in my debug.log. So i added the java keytool to my PATH and restart window. Problem gone

 

2019.1.1 still happen ...

 

If you integrating FacebookSDK you need to go to Edit -> Preferences -> External Tools -> unclick Android SDK checkbox -> click browse button -> press select folder -> Android Dependencies will be downloaded -> click Android SDK checkbox ->Ready!

 

I ran into the same issue and the solution for me was to install openssl (on Windows) and add it to the PATH environment variable. Make sure you also have some Java SDK correctly installed too. Both keytool and openssl should be available in the command window under any path if correctly done.

 

Our team ran into the same error today.

 

Same here

 

In my case, I had to add a full path to debug.keystore file (with file name included) this was not documented in fb integration guide

 

This worked for me. Thanks!!!!

 

Hi
I have this issue, where did you fix it?
How we can fix it in our system?

 

1. Donwload the openssl in google archive (link)
2. Unzip the openssl in local disk c\:
3. Add the openssl, JDK path(C:\Program Files\Java\jdk1.8.0_131\bin), lib(C:\Program Files\Java\jdk1.8.0_131\lib) path in your system variable "path".
4. be sure that you have create android debug.keystore in unity
5. restart your computer

your are going to note that in facebook settings the Debug keystore hash has been generated. now you can build your game

 

Still happening on for cloud builds on 2019.4.28f1 - Using debug.keystore or a full path doesn't work

 

I have the same problem
unity version 2019.4.34, any news on this?

 

No, because i found a work-around.

Go on unity preferences, unckeck default android sdk/ndk urls.
Create and destroy a new script.
Go on unity preferences, check default android sdk/ndk urls.
Create and destroy a new script.

And for magic it work again!!!

 

Open Editor Log, it will give you more detail about this issue. For me it was:

Code (JavaScript):

1. Android PostProcess task "Moving output package(s)" took 3.393 ms
2. Inh4eCIgCg==
3. 'keytool' is not recognized as an internal or external command,
4. operable program or batch file.
5. Your Android setup is not correct. See Settings in Facebook menu.

 

After at least 10 hours i accidentally discovered that you HAVE TO PRESS ENTER after you type in the missing keystore path in Facebook settings.
That's funny. But no one laughs.

 

Sorry for a silly question... where are these Facebook settings where one can type in a missing keystore path? We're struggling with "Your Android setup is not correct. See Settings in Facebook menu." when trying to build on Gitlab and we're not quite sure what that means.

 

If I remember correct this most likely a wrong java sdk path when you uninstall the old unity but the path are still remember in every version of unity and not auto overridden

 

This is worked for me with this environment; MacOs - Facebook SKD 14.1.0 - Unity 2021.1.9f1
Appreciate.

 

This was the solution for me.

It can be confusing because the path format is not the same as the one used in Unity's Android settings.

 

For me checking on and off the Android SDK location and restarting Unity fixes the issue.