apache / apache/cordova-android
Failed to generate v1 signature
- Dominant language
- JavaScript
- Stars
- 3.8k
- Forks
- 1.6k
- Avg merge
- 16h 18m
- Merged PRs (30d)
- 11
Description
## Problem
There was a problem migrating from cordova-android 8.1 to cordova-android 11
The application is not signed by the Existing key. Signs with a new key, but the application has been published on GooglePlay for a long time, the option with a new key is not acceptable.
Removed all plugins. The problem persists.
```
* What went wrong:
Execution failed for task ':app:signReleaseBundle'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.FinalizeBundleTask$BundleToolRunnable
> Failed to generate v1 signature
```
All similar problems have been studied, it is advised to contact support. But I don't think it can be solved. There must be a solution
The problem is 99% similar to mine -> https://stackoverflow.com/questions/69911745/how-can-i-use-the-current-keystore-to-build-successfully-or-migrate-to-new-k
Contributor guide
Research direction
Start by reproducing the cordova-android 8.1-to-11 migration and inspect the :app:signReleaseBundle failure, focusing on the existing keystore and release-signing configuration. Done means a release bundle is generated and signed with the existing key rather than a new key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, javascript
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100