Illegal option when using `expo build:android` with a keystore alias that starts with "-"

[expo]

Illegal option when using `expo build:android` with a keystore alias that starts with "-"

[cruzach]

Update for you @zaytrix- we're looking into this internally, thanks so much for bringing it to our attention 😊

I'll post any updates/info here as they come along

[dsokal]

Hello @zaytrix,
thanks for reporting. Unfortunately, there is nothing we can do about it. This is how jarsigner works and we're not going to change the way we sign .apk files for SDK 31 (this is the version you're using). It was changed in SDK 32 and we don't use jarsigner there.
You have two options here: you can either change the alias in your keystore or upgrade your project to SDK 32.

[zaytri]

I did some testing with jarsigner, I couldn't get it to accept an alias with a leading "-" at all. I was finally able to sign the app, I took the apk that Expo generated and manually signed it using zipalign then apksigner, and thankfully apksigner accepts an alias surrounded by quotes: "-myAlias".

zipalign -v -p 4 my-app-generated-by-expo-signed.apk my-app-unsigned-aligned.apk

apksigner sign --ks my-release-key.jks --ks-key-alias "-myAlias" --out my-app-release.apk my-app-unsigned-aligned.apk

It's inconvenient but it works.

[cruzach]

Hi @zaytrix!

I'm looking into this (glad you found a workaround in the meantime), but could you either share more of the build logs or send me your build id so I can take a look at them?

Thanks!
Charlie

[zaytri]

Here's my build id: afef4c23-dc1c-4cbc-991f-ccbb4f92a6d8
(I assume it's the one in the url when viewing the build)

Thanks for your help @cruzach!

[zaytri]

I've upgraded my project to SDK 33 and I can confirm that it works!