I am building a Cordova app to publish on the playstore and trying to sign it. The process I am following is

> cordova build android --release --buildConfig

ANDROID_HOME=/Users/dev002/Library/Android/sdk (recommended setting)
ANDROID_SDK_ROOT=/Users/dev002/Library/Android/sdk (DEPRECATED)
Using Android SDK: /Users/dev002/Library/Android/sdk

BUILD SUCCESSFUL in 1s
1 actionable task: 1 up-to-date
Consider enabling configuration cache to speed up this build: https://docs.gradle.org/9.3.1/userguide/configuration_cache_enabling.html
Subproject Path: CordovaLib
Subproject Path: app
(node:58130) [DEP0176] DeprecationWarning: fs.F_OK is deprecated, use fs.constants.F_OK instead
(Use `node --trace-deprecation ...` to show where the warning was created)

> Task :CordovaLib:compileReleaseJavaWithJavac
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

> Task :app:compileReleaseJavaWithJavac
Note: /Users/yotdev002/dev/youreontime-mobile-cordova-3/cordova/platforms/android/app/src/main/java/org/apache/cordova/statusbar/StatusBar.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

[Incubating] Problems report is available at: file:///Users/dev002/dev/mobile-cordova-3/cordova/platforms/android/build/reports/problems/problems-report.html

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD SUCCESSFUL in 4s
61 actionable tasks: 58 executed, 3 up-to-date
Built the following bundle(s):
        /Users/dev002/dev/mobile-cordova-3/cordova/platforms/android/app/build/outputs/bundle/release/app-release.aab

My build.json file is

{
    "android": {
        "debug": {
            "keystore": "sign-key-1.jks",
            "storePassword": "xxx",
            "alias": "key0",
            "password": "xxx",
            "keystoreType": "jks",
            "packageType": "apk",
            "v1SigningEnabled": true,
            "v2SigningEnabled": true
        },
        "release": {
            "keystore": "sign-key-1.jks",
            "storePassword": "xxx",
            "alias": "key0",
            "password": "xxx",
            "keystoreType": "jks",
            "packageType": "bundle",
            "v1SigningEnabled": true,
            "v2SigningEnabled": true
        }
    }
}

However, whey I check the file at the end it is not signed. There is no errors, all output is above. What can I do to find out the reason?

> jarsigner -verify app-release.aab

no manifest
jar is unsigned