|
Post by Dave on Nov 13, 2017 17:19:05 GMT
I am using RhoStudio 6.0.12, and have an application that uses the openssl and openssl.so extensions. It all builds successfully, but after submitting to the Play Store, it is rejected because of the following:
Which version of OpenSSL is Rhodes now targeting? I was under the impression it was 1.1.0h?
Thanks
|
|
|
Post by Alex Epifanov on Nov 13, 2017 17:57:26 GMT
Hi Dave, current version of openSSL used in Rhodes is 1.0.1g we know it is outdated and we are currently upgrading 3rd party libraries we use. You have two options now: - we provide openssl-edge and openssl.so-edge extensions in rho-tau-extensions package, you can download it here: tau-technologies.com/developers/downloads/. You should change your build.yml to use them. It uses openssl v1.1.0a, however it will only work for Android. - upgrade work is going now in this branch: github.com/rhomobile/rhodes/tree/update_libs; openSSL from this branch is 1.0.2n and it is confirmed to work with Android. So you can switch to this branch temporaly, or just replace your openssl and openssl.so extensions with ones from this branch. main RMS release stream will be updated soon enough with these changes.
|
|
|
Post by Dave on Nov 13, 2017 18:35:53 GMT
Thanks for the reply Alex. I tired building using the edge variants of the extensions, and the build fails with a whole host of errors (I'm running on Windows 10 (x64), Android API 19, and Java JDK 9.0.1)
|
|
|
Post by Dave on Nov 13, 2017 18:36:51 GMT
Oh, and Android NDK 15c
|
|
|
Post by Alex Epifanov on Nov 13, 2017 19:32:09 GMT
Hmm.. yes it seems edge won't work with 6.0, as it was introduced for 5.5 and old Ruby VM. We won't be updating/supporting it further as mainstream openssl update is underway. So you may either rollback to 5-5 for a while and use edge version, or use updated libs from the branch.
|
|
|
Post by Dave on Nov 13, 2017 19:42:56 GMT
I managed to build using the updated libs from the branch you'd mentioned, end Google still rejects it. I ran grep on the apk, and it says it's using OpenSSL 1.0.2m, so I'm not sure why Google are still complaining? So I may have to roll back and use 5.5 for edge then?
|
|
|
Post by Alex Epifanov on Nov 13, 2017 19:47:39 GMT
Does Google rejects for the same reason? 1.0.2m should work for them.
|
|
|
Post by Dave on Nov 13, 2017 19:54:49 GMT
Yes. It's pretty strange. Their documentation says OpenSSL must be grater than 1.0.2f (which this should be), but they still rejected for OpenSSL. I could maybe try appealing it, but will just try compiling with the edge variants first, and see if that goes up OK.
|
|
|
Post by Dave on Nov 14, 2017 9:39:58 GMT
Just as an update, I rebuild using the edge variants, and it passed validation. So it didn't seem to like the 1.0.2m version for some reason? Just thought I'd better let you know, as if this is the version you are planning on upgrading to, it may have submission issues.
|
|
|
Post by Alex Epifanov on Nov 14, 2017 14:12:54 GMT
Thanks Dave, we'll try to submit a new one and see what Google says.
|
|
|
Post by Dave_ on Feb 7, 2018 11:03:14 GMT
I've just seen on the 6.0.22 changelog that you've updated the OpenSSL library, but just to v1.0.0h? Is this correct, or should it be v1.1.0h?
|
|
|
Post by Alex Epifanov on Feb 7, 2018 11:45:43 GMT
It's a mistake in changelog, thank you Dave. OpenSSL version is 1.1.0h. Changelog.txt is updated
|
|