Skip to main content

Android Troubleshooting

This page covers common issues encountered during Android SDK integration and how to resolve them. [PLACEHOLDER] If you encounter an issue not listed here, enable SDK debug logging (enableLogging(true)) and check logcat for messages tagged VLPlay. You can also open a ticket via your VLPlay representative.

[PLACEHOLDER] Most integration issues are caused by missing permissions, incorrect App ID / Client Secret values, or network restrictions in the test environment. Always verify your credentials in your VLPlay representative before filing a bug report.

Common Issues​

VLPlayNotInitializedException​

Cause: You called an SDK method before VLPlaySDK.initialize().

Fix: Ensure you call VLPlaySDK.initialize() in Application.onCreate() before any Activity starts.

Gradle Sync Fails — Repository Not Found​

Cause: The VLPlay Maven repository is not configured in settings.gradle.kts.

Fix: Add the repository as shown in the Installation guide.

CLEARTEXT_NOT_PERMITTED on Android 9+​

Cause: Android 9+ blocks non-HTTPS traffic by default.

Fix: VLPlay SDK uses HTTPS exclusively. If you see this error, check that your own network calls are also using HTTPS.

SDK Crashes After Minification​

Cause: R8 / ProGuard is stripping SDK classes.

Fix: Add the ProGuard rules from the Installation guide.

Authentication Popup Does Not Appear​

Cause: The VLPlay WebView activity is not registered in the manifest.

Fix: Ensure the <application android:name=".MyApplication"> tag is present and correct.