Search Unity

  1. Megacity Metro Demo now available. Download now.
    Dismiss Notice
  2. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Upload failed. You uploaded an APK that was signed in debug mode

Discussion in 'Android' started by Littlenorwegian, Jul 1, 2013.

  1. Littlenorwegian

    Littlenorwegian

    Joined:
    Oct 19, 2012
    Posts:
    143
    So, I've been making this android game. Tested it loads of times on my own device(s) and now I am trying to upload it to google play.

    Problem: I get this message when I upload it.
    "Upload failed You uploaded an APK that was signed in debug mode."

    I was wondering what I should do? Looking online I am not finding things that are very helpful, so please. I beg of you. Tell me what to do.
     
  2. Littlenorwegian

    Littlenorwegian

    Joined:
    Oct 19, 2012
    Posts:
    143
  3. kapil231ice

    kapil231ice

    Joined:
    Oct 6, 2017
    Posts:
    1
    Yes it worked for me dear,Many Thanks
     
  4. ematsuno

    ematsuno

    Joined:
    Oct 13, 2015
    Posts:
    27
    I'm not able to submit my APK n to the play store in order to proceed with IAP development. Getting error: "You uploaded an APK that was signed in debug mode. You need to sign your APK in release mode".

    The solution is to build a release mode version with signed release


    Setting up non debug

    1) I've unchecked the development build box:

    File-> Build Settings

    uncheck the development build box

    2) I went to my visual studio project settings and had it compile in release mode

    Signing the APK in release mode
    Click File -> Build Settings ->Player Settings

    System displays player settings in inspector

    1) Select Create new key Store

    a. Enter keystore password

    b. Confirm keystore password

    2) Select Create New key from Key/Alias Dropdown
    alias: Test

    Password: helloworld

    Confirm: helloworld

    First and last name: john doe

    Organizational unit: development
    Organization: MyOrganization
    City: MyCity
    State: CA
    Country: US

    Hit create key



    I then go back to the Build settings interface and hit buld.

    minutes later, I try to submit and it gives me the same error.

    What am I missing?
     
    MohnishR likes this.
  5. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    835
    Once the key is created you have to select it (it's not selected by default). In the same place (publishing settings) make sure Key Alias is set to "Test" instead of "Unsigned (debug)" and also enter the key password in the password field (in your example it should be helloworld).
     
    ChristmasSpiritman likes this.
  6. JParish2590

    JParish2590

    Joined:
    Jan 8, 2014
    Posts:
    32
    i have my key selected and keystore all created... development build is not on... i still get the same error as the person above... is this a bug?
     
  7. JuliusM

    JuliusM

    Unity Technologies

    Joined:
    Apr 17, 2013
    Posts:
    835
    Make sure you have your keysore and key selected as well as both passwords are entered. When building make sure you don't get any errors and that the application is build successfully. This should work and we are not aware of any issues related to this.
     
  8. akeplinger

    akeplinger

    Joined:
    Oct 26, 2008
    Posts:
    57
    I'm seeing the same issue. I was able to submit an apk to the google store using 2019.2.x. I updated to 2019.3 and now I'm seeing this message. The app that is already in the Google store uses the current certificate so it doesn't seem likely that the certificate is the problem. I had turned on the "Debug" setting C++ compiler configuration, but that has been returned to "Release". Also the main build settings does not have "Development Build" checked. I don't know where else "Debug" could be defined.
    A little stuck doing a simple process.
     
  9. akeplinger

    akeplinger

    Joined:
    Oct 26, 2008
    Posts:
    57
    Addendum: Android manifest included
    Code (CSharp):
    1.  android:debuggable="true"
    I had not been manually editing the Manifest, so I bet it snuck in when I temporarily changed the app to debug and didn't get removed afterward.