You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use the same Android.keystore file for multiple apps.
When doing a build I was prompted for the keystore and chose the keystore I had used a week before for another app.
After being prompted for the password the build is fired off.
This doesn't give me the opportunity to specify which APP in the keystore I am using.
The build completed with what I am assuming the wrong keystore information (app name from last week that is stored in extension settings).
I had to delete the stored settings.
I propose when doing an Android build, after selecting the .keystore file, the extension prompts the user with "Use Last Saved Keystore Information?" (Yes/No). Alternatively, the build process could still prompt for the keystore alias but at that point we are entering almost everything again. Alternative #2, the extension could prompt during build "Use saved keystore information for ${<Alias Name>} ?"
It took me a couple builds to see in the bottom right corner a notification that saved keystore information was being used and a button to delete the saved information.
The text was updated successfully, but these errors were encountered:
@newportsolutionsgroup I'm not sure I'm understanding "This doesn't give me the opportunity to specify which APP in the keystore I am using.", the information used/saved for a keystore is the alias, location, password, and privateKeyPassword.
My understanding is that if a keystore is shared between apps then this information is the same between apps as the information is for the keycstore itself and not the application. If the information was invalid (say alias=foo was provided but alias=bar is correct) then the Titanium build would error as it wouldn't be able to sign the application using that keystore as it is invalid.
Is my understanding incorrect/incomplete? Doing some research it seems like a keystore can contain multiple keypairs that can be identified by the alias argument? That makes storing the keystore information a bit more complex as we currently use the keystore path as a key for the information (including alias) so I think that would need completely reworking here
We use the same Android.keystore file for multiple apps.
When doing a build I was prompted for the keystore and chose the keystore I had used a week before for another app.
After being prompted for the password the build is fired off.
This doesn't give me the opportunity to specify which APP in the keystore I am using.
The build completed with what I am assuming the wrong keystore information (app name from last week that is stored in extension settings).
I had to delete the stored settings.
I propose when doing an Android build, after selecting the .keystore file, the extension prompts the user with "Use Last Saved Keystore Information?" (Yes/No). Alternatively, the build process could still prompt for the keystore alias but at that point we are entering almost everything again. Alternative #2, the extension could prompt during build "Use saved keystore information for ${
<Alias Name>
} ?"It took me a couple builds to see in the bottom right corner a notification that saved keystore information was being used and a button to delete the saved information.
The text was updated successfully, but these errors were encountered: