-
-
Notifications
You must be signed in to change notification settings - Fork 295
Signing Validation Error on bundle release #691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
After a lot of debugging related to the signing path, I have found the reason for the issue. The issue seems to be platform-specific(occurs on windows).
So I assumed that the changes may reflect on runtime on processing4. So I printed gradle.properties file data on runtime and it was showing me the proper signing data as expected. In short, if the path with a single slash is being used in gradle.properties for PROCESSING_UPLOAD_KEYSTORE_FILE I can resolve this with the condition to identify the platform and use Thanks! |
@rupesh-kumar-lpu ok the strings between "@@" are replaced by Processing with the actual values (not include in the file for security reasons since they are the key store password, etc). But, it makes sense the error you are seeing on Windows caused by the wrong slashes... I will double check on my windows computer |
@codeanticode thanks for clearing it Andres. |
@rupesh-kumar-lpu I confirm the error on Windows. It's strange, I thought I tested signed bundle export before, but anyways... Your fix is good Also, I think that replacing backslashes with forward slashes would also work, see this other part of the code: If you create a PR, I will merge asap. Thank you! |
It seems the Keystore path needs to be checked which is being used in the
gradle.properties
template. It looks like slashes are not being used in the returned Keystore file path.I'm looking into it.
The text was updated successfully, but these errors were encountered: