Hello Developers,
We’ve found an issue where if you have unicode characters in Android certificate key passphrase or keystore passphrase then the build is failing. The issue is being fixed, but meanwhile we ask that you do not use non ASCII characters in key passphrase or keystore passphrase when you create a new certificate. If you have already created a new certificate we ask that you delete that and create a new one with only ASCII characters in alias, and pass phrasses.
If you had converted a legacy certificate with unicode in alias, key passphrase or keystore passphrase, you have couple of options.
1) Reconvert the legacy certificate: (If you have used the legacy certificate earlier to publish an app and you need the certificate to make updates then use this option)
- Download your certificate,
- Delete your converted certificate from Account Settings
- Send a private message to this forum thread to enable reconversion
- Then we will enable the conversion and you can convert the legacy certificate again
- Convert the legacy certificate from Account Settings with ASCII characters only in the alias, key passphrase and keystore passphrase field.
2) Create a new certificate (If you do not have apps in store that use the legacy certificate then use this option)
- Create a new certificate from Account Settings with only ASCII characters in the alias, key passphrase and keystore passphrase field.
