-
Notifications
You must be signed in to change notification settings - Fork 7
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
Callbacks are not executing on client.on(SplitEvent.SDK_READY) #544
Comments
Hi @gastsail in order to check if the SDK is running into any issues while initializing could you enable the SDK's debug logging (see: https://help.split.io/hc/en-us/articles/360020343291-Android-SDK#logging) and share the logs here? |
@agustinona I have tried again and is not triggering any callback even if I put the callback right after the splitFactory.client() |
The error log shows this
|
@gastsail In this case it seems the SDK is unable to establish a connection to Split's CDN due to a SSL handshake error: Is this happening in an emulator? Could you check is you are running into the issue described here? https://help.split.io/hc/en-us/articles/360042140631-HTTP-Exception-Chain-validation-failed |
Platform: Android
I have followed the documentation and used everything stated there, created my SDK API Key for client-side inside an Environment as below
I have hidden organization details.
But after adding everything just to test on my MainActivity
Nothing returns in the logs, I have already created the feature flag and everything, granted INTERNET access into the manifest, IDK what is happening, it should work
implementation("io.split.client:android-client:3.3.0")
compileSdk = 34
I'm only receiving
Also added
val config: SplitClientConfig = SplitClientConfig.builder().impressionsMode(ImpressionsMode.DEBUG).build()
but cannot see anything in the console
I have also followed the demo app here
https://github.com/Split-Community/Split-SDKs-Examples/blob/main/android-sdk/UI_App/app/src/main/java/com/example/example_app/ui_app/SplitSDK.java
but no success
The text was updated successfully, but these errors were encountered: