Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devices with TLS 1.0 and TLS 1.1 are being reported (Android 4.x) #389

Closed
vladaman opened this issue Nov 25, 2023 · 1 comment
Closed

Devices with TLS 1.0 and TLS 1.1 are being reported (Android 4.x) #389

vladaman opened this issue Nov 25, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@vladaman
Copy link

Expected Behavior

OkHttp should support TLS 1.0 and TLS 1.1

Current Behavior

Old devices that don't support TLS 1.0 and TLS 1.1 are not posting data to Amplitude REST API. Therefore, we are missing about 20% of events due to legacy devices that use Android 4.x.

Possible Solution

Provide the ability to inject custom OkHttpClient for those who require to track legacy clients or re-enable TLS 1.0 and TLS 1.1 on your REST API.
See https://gist.github.com/Karewan/4b0270755e7053b471fdca4419467216

@vladaman vladaman added the bug Something isn't working label Nov 25, 2023
@Mercy811
Copy link

Hi @vladaman, both https://api2.amplitude.com/ (endpoint used by Amplitude Android SDK) and https://api2.amplitude.com/2/httpapi (endpoint used by Amplitude Kotlin SDK) support only TLS 1.2. TLS 1.2 is supported starting from Android API level 16 (Android 4.1). the Android SDK is now in maintenance mode. We'd recommend to upgrade to the Kotlin SDK which uses HttpURLConnection rather than OkHttp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants