![]() We still haven't heard even when this will be addressed. It should take less than couple of days to make this change and may be few days for testing and then release. ![]() Since we rely on AppCenter for that, when we don't have the fix available it leaves us questioning why there is no solution provided. #Return code: Android 11 has been released, we developers need to support distribution of the apps. #Error: /usr/bin/jarsigner failed with return code: 1 Jarsigner error: : private key algorithm is not compatible with signature algorithm usr/bin/jarsigner -keystore /Users/runner/runners/2.171.1/work/1/s/.certs/keystore.jks -storepass *** -keypass *** -verbose -sigalg SHA256withRSA -digestalg SHA-256 -signedjar /Users/runner/runners/2.171.1/work/1/s/xxxx.aab /Users/runner/runners/2.171.1/work/1/s/ *** (node:2087) Warning: Use Cipheriv for counter mode of aes-256-ctr #Starting: Sign Android App Bundleĭescription : Sign and align Android APK files #Finishing: Build bundle from Xamarin.Android project However we currently only support jarsigner within this task." "As of build tools 24.0.3, Google has recommended that developers use "apksigner" I also found these articles that confirm my idea:Īnd this quote is from xamarin issue tracker The MD5withRSA algorithm specified for the -sigalg option is considered a security risk.) It seems that AppCenter is using an old version of signing the app, which is security vulnerability.Īs I can see from the logs AppCenter is using jarsigner and pass -sigalg MD5withRSA -digestalg SHA1, which is not secure and deprecated. We are trying to build release version of the app, using our release key, but it get "jarsigner error: : private key algorithm is not compatible with signature algorithm".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |