ChatGPT says...
What you were told is basically correct—but the key point is that this isn’t really a B4A/B4i issue or related to HttpJob itself.
B4A (OkHttp/OkHttpUtils2) and B4i both rely on the **underlying OS trust store**. So whether an SSL certificate works depends entirely on:
* The **certificate chain (root + intermediate)**
* Whether the **device’s OS trusts that chain**
### Why this becomes a problem
Older Android devices have a **fixed list of trusted root certificates**, and that list does **not get updated**.
At the same time, websites and cloud services:
* Regularly **renew/update their SSL certificates** (often yearly)
* Switch to **new certificate authorities or chains**
* Adopt **stronger security requirements**
When that happens, older devices may no longer recognize the certificate chain as valid.
### The result
On older Android versions (especially 4.x–5.x, and increasingly 6–7):
* SSL handshake failures
* HTTPS requests fail
* Connections to APIs/cloud services stop working
### About your specific case
* Your current certificate (**GeoTrust RSA 2018**) is being deprecated, so yes—after April 2026 it may no longer be trusted by newer systems.
* Moving to **GeoTrust TLS RSA CA G1** is the correct step for modern compatibility.
However:
* It will work fine on **newer Android and iOS devices**
* It may **not work on older Android devices**, because they may not trust the newer certificate chain
### Important takeaway
There is **no longer a single SSL certificate that works across all Android versions**.
So if something “doesn’t work with B4A,” it’s almost always:
An **outdated root certificate store on the device**, not your code or the library.
### What you should do
* Move to the newer certificate (GeoTrust TLS RSA CA G1 or equivalent)
* Test against your **minimum supported Android version**
* Decide whether supporting very old Android devices is still worth it
### Reality check
If you must support very old Android versions, your options are limited:
* Find a certificate chain that still supports legacy trust stores (getting rare)
* Implement a custom trust solution (not recommended for security reasons)
Bottom line:
This is an **Android OS limitation + evolving SSL standards**, not a B4A/B4i problem.
