Hi,
i got a question about the cloud builds for Android.
Google switched in Android 6 from OpenSSL to BoringSSL, so software expecting openssl on the device no longer works with https [1].
This is also described in this blog post by esri [2], which tells Qt developers to include OpenSSL in their builds.
Well, the question now is, does ESRI plan to include OpenSSL in their cloud builds?
Because currently APKs produced by the cloud build don't work on android 6 with HTTPS (they do e.g. with android 5).
And OpenSSL doesn't seem to be included, it's nowhere to be found (in lib\armeabi-v7a\).
Or is ESRI's recommedation to setup a local build and try steps similar to [2]?
Or maybe I'm completly wrong?
Any input is appreciated.
And please excuse my clumsy english.
Cheers,
Armin
[1] https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html
[2] https://community.esri.com/community/developers/native-app-developers/arcgis-runtime-sdk-for-qt/blog...
Well, colour me pleasently suprised and a little bit confused.
I built an APK today using the ESRI cloud service and https now works on an Android 6.0.1 device 🙂
A peek inside the APK reveals a new "libcrypto.so" - which looks an awful lot like OpenSSL.
No idea, when ESRI changed this (maybe with the rollout of AppStudio 1.3), but it works now.
Cheers,
Armin
Yes, the libcrypto.so is added with the release of AppStudio 1.3
Armin, as Nakul mentioned, AppStudio 1.3 was rolled out end of November 30 includes upgrades to Local Make and Cloud Make to include OpenSSL for all Android apps built.