- 
    
Bug
 - 
    Resolution: Duplicate
 - 
    
P2: Important
 - 
    None
 - 
    6.5.0 FF
 - 
    None
 
When running some tests that require a TLS connection, the Android configuration in CI provides multiple warnings like:
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_init_ssl
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_init_crypto
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve ASN1_STRING_get0_data
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve EVP_CIPHER_CTX_reset
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve EVP_PKEY_param_check
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_new_null
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_push
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_free
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_num
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_pop_free
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OPENSSL_sk_value
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve DH_get0_pqg
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_CTX_get_security_level
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_CTX_set_security_level
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_CTX_set_ciphersuites
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_set_psk_use_session_callback
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_SESSION_is_resumable
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_get_client_random
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve SSL_SESSION_get_master_key
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve TLS_client_method
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve TLS_server_method
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_STORE_CTX_get0_chain
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_getm_notBefore
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_getm_notAfter
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_get_version
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_STORE_set_ex_data
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve X509_STORE_get_ex_data
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve CRYPTO_free
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OpenSSL_version_num
QWARN  : tst_OAuth2::setSslConfig() : QSslSocket: cannot resolve OpenSSL_version
QWARN  : tst_OAuth2::setSslConfig() : Incompatible version of OpenSSL
QWARN  : tst_OAuth2::setSslConfig() : The backend "cert-only" does not support QSslKey
QWARN  : tst_OAuth2::setSslConfig() : Active TLS backend does not support key creation
The warnings suggest that a backend without TLS is selected. If the tests do not guard against that, they can fail.
Some examples:
qtbase
integration: https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1668655426
qtnetworkauth
integration: https://testresults.qt.io/coin/integration/qt/qtnetworkauth/tasks/1669075273
- duplicates
 - 
                    
QTBUG-110025 Android tests aren't bundling OpenSSL for any test
-         
 - Closed
 
 -