High Fallback Rates Occur on Android When Using Auth0 Bot Detection

High fallback rates occur on Android devices when using Auth0 bot detection because the Android application requests use a default, unbranded User-Agent. Configuring the Android application HTTP client to send a descriptive User-Agent resolves this issue. The observable symptom is a high fallback rate on Android applications, while iOS applications remain unaffected.

• Auth0
• Android
• iOS
• Mobile SDK
• Bot Detection
• High fallback rates

Android application requests use the default okhttp/5.3.2 User-Agent with no application identification, while iOS automatically sends a descriptive User-Agent (tenant/... app/...). The Auth0 bot detection model treats generic or unbranded User-Agents as higher-risk because that pattern is far more common in automated clients. This difference in default User-Agent behavior causes Android applications to experience high fallback rates while iOS applications do not.

How is the high fallback rate on Android resolved?

Configure the Android application HTTP client to send a descriptive User-Agent identifying the application.

• Update the HTTP client configuration (for example, via an OkHttp Interceptor) to include a descriptive User-Agent that identifies the application.