How do I export a signed app bundle?

0 favourites
  • 3 posts
From the Asset Store
Easily integrate Telegram Mini Apps SDK into your Construct 3 projects for building interactive apps and games.
  • I've been following the instructions in the tutorials and what I can find on the internet, but try as I might, every time I go to export this app bundle (or really any of the signed options), the process fails. It tells me to check the log to see what needs fixed, and the only thing in the log is "Error" which is suuuuper helpful.

    My process is the following:

    - I go to file, export, Android (Cordova).

    - I click OK when it tells me about the issue with project version.

    - Minimum Version is set to 5.1+ (Lollipop). It's not an incredibly intensive game by any stretch, so it should run on anything.

    - Android build I have tried legit every one of the signed builds. Unsigned all work fine, but I can't upload into Google unsigned. I need a Signed Android App Bundle, specifically, so I choose that.

    - URL Whitelist I don't edit.

    - Android version remains on 1000000 or however many zeroes are on the end of that.

    - I have the hide status bar, require vibrate permission, and require external storage write permissions selected.

    - I upload my keystore.jks file that was generated for me from Construct 3.

    - Key Alias is set

    - Keystore Password was the one I assigned to the keystore attached.

    - I've tried with and without the optional Key Password.

    I click Next, and it does the internal Construct stuff, and sends the build off. Every time, the error returns is the following:

    Any help that you can provide would be greatly appreciated.

    -P

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • More digging has found that looking at the Dev Console may provide me with a better look at the error, and it did! I'm getting the following:

    "Error: Please specify the keystore."

    Which is odd because I am specifying the keystore? I don't know, this part is all foreign to me.

  • In the meantime, I have now exported the project files, open them up in Android Studio, and export them there. It works flawlessly once you have the right builds set up. I think from doing that, I understand what I'm missing here -- it seems to be related to when I set up the Key for the individual product. It's looking for that established key, not a new one I can type on the fly, and I'm betting that's what is causing the issue in Construct 3.

    Either way, I might test it on the next build, but for now, having Android Studio has worked in the interim.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)