Search Unity

  1. The 2022.1 beta is now available for testing. To find out what's new, have a look at our 2022.1 beta blog post.
    Dismiss Notice

APK Signing Failed! Unable to determine signature algorithm.

Discussion in 'Developer Preview Archive' started by Fuzzy, Jan 22, 2012.

  1. Fuzzy

    Fuzzy

    Joined:
    Feb 11, 2011
    Posts:
    266
    Hi,
    I wanted to compile an android project (in 3.5.0b6) started in unity 3.4 and updated to 3.5.0b6, but it fails at signing the APK so i can't upload an updated version to the android market.
    It worked well in 3.4.

    Code (csharp):
    1. Error building Player: UnityException: APK Signing Failed!
    2. Unable to determine signature algorithm.  See the Console for details.
    Error in file: at line -1


    theres also a message about data entered in the Key for the game in the console followed by:
    Code (csharp):
    1. UnityEngine.Debug:LogError(Object)
    2. PostProcessAndroidPlayer:GetSigAlgo()
    3. PostProcessAndroidPlayer:SignAndroidPackage(String)
    4. PostProcessAndroidPlayer:PostProcess(BuildTarget, String, String, String, String, String, String, BuildOptions)
    5. UnityEditor.HostView:OnGUI()
    Error in file: .../Runtime/ExportGenerated/Editor/UnityEngineDebug.cpp at line 39


    it also throws another error message first:
    Code (csharp):
    1. !IsDirectoryCreated(targetFolder)
    2. UnityEditor.HostView:OnGUI()
    Error in file: .../Editor/Src/BuildPipeline/BuildTargetPlatformSpecific.cpp at line 413


    Is anyone else experiencing this problem too and is there a workaround/solution? Or do i have to wait until the unity team fixed it and releases an update?
    I'm using unity pro with android pro on win 7 32bit and 64bit. (in case it matters)
     
    Last edited: Jan 22, 2012
  2. TegTap

    TegTap

    Joined:
    Sep 27, 2011
    Posts:
    21
    I'm getting this error:

    !IsDirectoryCreated(targetFolder)
    UnityEditor.HostView:OnGUI()

    Error in file: .../Editor/Src/BuildPipeline/BuildTargetPlatformSpecific.cpp at line 413

    but none of the other ones. The above error has not prevented me from publishing in the Android Market, but I'd still like to know what the error means.
     
  3. Fuzzy

    Fuzzy

    Joined:
    Feb 11, 2011
    Posts:
    266
    Downloaded installed 3.5.0f1 and still experience this problem.

    No one else having this problem? And there's no known solution to it?
     
  4. Ken Tso

    Ken Tso

    Joined:
    Jan 27, 2012
    Posts:
    1
    I am facing the same problem as Fuzzy does."APK Signing Failed! Unable to determine signature algorithm."
    I spent a day on this matter but got no luck.
    My project works fine ( can be exported , signed and uploaded to android market ) in Unity 3.4. But fail to export in Unity 3.5.0f1.
     
  5. Aiursrage2k

    Aiursrage2k

    Joined:
    Nov 1, 2009
    Posts:
    4,835
    I had the same problem and it seems like it keeps loosing the password for the keygen, othertimes I just close the editor reopen it and it seems to solve it most of the time.
     
  6. Fuzzy

    Fuzzy

    Joined:
    Feb 11, 2011
    Posts:
    266
    Re-opening the editor did not work for me, at lest the maybe 10 times i've tried it.

    So is there still no solution around? And is this really such a rare problem as it seems, since there are barely any repsonses about others having the same problem here.
     
  7. spacefrog

    spacefrog

    Joined:
    Jun 14, 2009
    Posts:
    654
    I got the same problem, but only on Windows
    Doing the signing on OSX works flawlessly ... This might al come down to an incompatible Java Version installed or similar
     
  8. eriQue

    eriQue

    Unity Technologies

    Joined:
    May 25, 2010
    Posts:
    595
    We have located the cause of this problem, and it will be fixed before 3.5 is released 'for real'.

    Thanks.
     
  9. Fuzzy

    Fuzzy

    Joined:
    Feb 11, 2011
    Posts:
    266
    Awesome!
    I have to thank you! ;)
     
  10. wsteptoe

    wsteptoe

    Joined:
    May 26, 2011
    Posts:
    12
    I am still having this issue with the release version of 3.5.
     
  11. wsteptoe

    wsteptoe

    Joined:
    May 26, 2011
    Posts:
    12
    Hi Erique,

    I am still experiencing the issue of APK signing failing when I try to build and sign my app in 3.5 release.

    In a previous reply in this thread, you stated to have identified the problem and that it would be fixed in 3.5 release version.

    Perhaps it is my setup, but I have tried 3 different versions of JDK (both 32-bit and 64-bit). I'm not sure what else it could be. I have tried uninstalling and reinstalling Unity, and updated the Android SDK.

    This is a critical issue, as I can't release my apps to the Android Market at the moment.

    Would really appreciate for this to be looked into.
     
  12. wsteptoe

    wsteptoe

    Joined:
    May 26, 2011
    Posts:
    12
    bump for this critical issue
     
  13. bitter

    bitter

    Unity Technologies

    Joined:
    Jan 11, 2012
    Posts:
    530
    It might be that you have overridden the default java class path. In the signing script we more or less assume that current working directory is part of the class path.

    Could you please verify that the CLASSPATH environment variable hasn't been set on a system level to something that does not contain "."?
     
  14. wsteptoe

    wsteptoe

    Joined:
    May 26, 2011
    Posts:
    12
    Bingo that's it!

    My CLASSPATH environment variable had been set by another software (OpenNI in my case). For anyone else having this problem, rename or remove the CLASSPATH environment variable.

    Thanks a lot, issue resolved.
     
  15. Elecman

    Elecman

    Joined:
    May 5, 2011
    Posts:
    1,357
    Same problem here. I tried un-installing all java software (jre, jdk, etc), removed all registry entries, paths, etc. Then re-installed the jre and jdk. Same problem. Reset the classpath to just ".;", same problem. Set the classpath to ".;F:\JDK\bin", same problem. Removing the classpath environment variable entirely doesn't solve the problem either. All methods tried after a reboot.
    This is serious!
     
    Last edited: Mar 10, 2012
  16. elixir-bash

    elixir-bash

    Joined:
    Mar 27, 2012
    Posts:
    23
    hey guys , im facing the same prob. i have downloaded the Unity for Android 3.5 version and also have included Vuforia plugin to add some AR. I tried building the same app and while building im getting this error.

    I tried rebooting the system, reloading the Unity ,i even changed my t shirt ;).Nothing worked :(
    m kinda frustrated.any suggestions would help.Thank you !!
     
  17. Evil-Dog

    Evil-Dog

    Joined:
    Oct 4, 2011
    Posts:
    134
    Same errors here, I'm trying to fix this and I'm getting a variety of "APK Signing Failed! Unable to determine signature algorithm." or
    "jarsigner: unable to read password .... APK Signing Failed!" and others.

    This is quite unnacceptable. Anyone have more possible solutions to this?
    Thanks a bunch

    ps: that's in 3.5.0f5
     
  18. Eric-Laberge

    Eric-Laberge

    Joined:
    Jan 20, 2011
    Posts:
    26
    I had the same problem plaguing me for a while, and managed to fix it by upgrading OSX Unity from 3.5.0f1 to 3.5.0f5.
     
  19. Evil-Dog

    Evil-Dog

    Joined:
    Oct 4, 2011
    Posts:
    134
    I'm on PC, maybe I'll try reinstalling Unity, eh who knows
     
  20. Evil-Dog

    Evil-Dog

    Joined:
    Oct 4, 2011
    Posts:
    134
    I reinstalled Unity 3.4.0f5 (latest version) and it still doesn't work.
     
  21. Aiursrage2k

    Aiursrage2k

    Joined:
    Nov 1, 2009
    Posts:
    4,835
    Looks like this problem is back in the newest version of unity
     
  22. Evil-Dog

    Evil-Dog

    Joined:
    Oct 4, 2011
    Posts:
    134
    I fixed this issue by uninstalling everything java, the jdk, all the java envrionement variables and reinstalling jdk 6.x, hope it helps
     
  23. Brian-Sinasac

    Brian-Sinasac

    Joined:
    Sep 8, 2012
    Posts:
    97
    Having this issue too.
     
  24. Evil-Dog

    Evil-Dog

    Joined:
    Oct 4, 2011
    Posts:
    134
    Did you try what I said? In the last post? I also found that with my new computer, which is a 64bit, I had installed jdk 64bit but you need to install the 32bit version otherwise there are problems.
     
unityunity