-
Notifications
You must be signed in to change notification settings - Fork 29
Illegal option when using expo build:android
with a keystore alias that starts with "-"
#60
Comments
I did some testing with 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. |
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 Thanks! |
Here's my Thanks for your help @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 |
Hello @zaytrix, |
I've upgraded my project to SDK 33 and I can confirm that it works! |
Description
I am manually uploading an existing keystore using
expo build:android
, and the alias that I need to use has a leading "-", for example:-myAlias
. When prompting for the keystore alias, that's what I type in.? Keystore Alias: -myAlias
Expected Behavior
I thought it would work fine, I even tried all of these options to attempt to escape the "-" character: https://stackoverflow.com/a/26453747
Observed Behavior
It seemed like everything was successful, but I was unable to install the app, so I checked the build logs and saw this under signing created apk:
Environment
I am using Expo Cli 2.17.0
The text was updated successfully, but these errors were encountered: