[Solved] Build FAILED: "app: SignReleaseBundle"

I'm at a complete loss with this.

My app continually fails to build when using the key generated by Android Studio (.jks) with the following exception in the error log.

It builds successfully if I build an unsigned app, or if I use an old .keystore key generated by the (presumably deprecated) Keystore Generator Tool. However, Google Play does not accept an app bundle signed using this old tool.

Fusion doesn't even seem to recognise the .jks file when you navigate to the folder containing this key, I select it anyway, but the build always fails.

I'll just post the most relevant part of the error log. If the full log is required for assistance I'm happy to provide it. Any help with this would be greatly appreciated

Quote

> Task :app:extractReleaseNativeSymbolTables
> Task :app:mergeDexRelease
> Task :app:buildReleasePreBundle
> Task :app:compileReleaseArtProfile
> Task :app:packageReleaseBundle
> Task :app:signReleaseBundle FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:signReleaseBundle'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.FinalizeBundleTask$BundleToolRunnable
> Failed to read key Jalopy from store "E:\Projects\Keystore\keystorefilezz\JalopyKeyz.jks": Integrity check failed: java.security.NoSuchAlgorithmException: Algorithm HmacPBESHA256 not available

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at Please login to see this link.

BUILD FAILED in 53s
37 actionable tasks: 37 executed

Display More

UPDATE:

Ok, I've managed to figure out what the issue was.

The problem was that my JDK path was pointing to another Java installation I had on my computer, and NOT the one that came with Android Studio (usually in location c:\Program Files\Android\Android Studio\jbr)

It now builds both .apk and .aab using the.jks keystore file without issues (and faster)

The previous JDK installation I pointed to was in a custom location I used when following a Android Exporter setup tutorial in an article on Steam, ironically with the intent purpose of being able to build apps WITHOUT having to download the behemoth that is Android Studio & have my hard drive clogged up with a slow & buggy IDE, and every API ever - just in case you wanted to run your fusion app on somebody's watch, toaster or doorbell

Anyway, what I'm saying is don't follow that Steam tutorial if you want to successfully build release mode .aab files for publishing, just use the Android Studio paths.