FAQ & troubleshooting for Android SDK

This page answers common questions about integrating and using the Blueshift Android SDK.

Setup and initialization

Where do I add the SDK initialization code?

Add SDK initialization in your Application class's onCreate() method. See SDK setup for complete instructions.

What permissions does the SDK require?

Required permissions:

INTERNET - For API communication
ACCESS_NETWORK_STATE - To check network availability
POST_NOTIFICATIONS - For push notifications (Android 13+)

How do I get my API key?

Push notifications

Push notifications aren't being received. What should I check?

Verify google-services.json is in your app/ directory
Check if the FCM token is generated (look for "FCM Token" in Logcat)
Confirm notification permissions are granted (Android 13+)
Test with a direct FCM token send from Push Studio

See Push notifications → Test for details.

Do I need to request notification permissions?

Yes, for Android 13 (API level 33) and above. The SDK provides requestPushNotificationPermission() to handle this. See Push notifications → Request permissions.

Will notifications work if the app is closed?

Yes, if FCM is appropriately configured. Push notifications are delivered by the system even when your app is not running.

In-app messages

In-app messages aren't showing. What should I check?

Verify the activity is registered: registerForInAppMessages(activity)
Check that the trigger event fired (look for the event in Logcat)
Confirm the device ID matches the test send
Check that the campaign is active and targeting your user

How do I show in-app messages on specific screens only?

Call registerForInAppMessages(activity) only in activities where you want messages to appear. Call unregisterForInAppMessages(activity) when leaving those screens.

Mobile inbox

How do I check the number of unread messages in the inbox?

Use BlueshiftInboxManager.getUnreadMessagesCount(). See Mobile inbox → Get unread count for code examples.

Inbox is empty even after sending test messages. Why?

Verify isInboxEnabled = true in your Configuration
Check that the device ID matches the test send
Confirm the message was sent with "Deliver to inbox" enabled
Wait a few minutes for sync to complete

Universal links

Universal links open in the browser instead of the app. Why?

This happens when Android hasn't verified domain ownership. Common causes:

assetlinks.json file is not accessible at https://your-domain/.well-known/assetlinks.json
Domain verification hasn't completed yet (try reinstalling the app)
Intent filter missing android:autoVerify="true"

See Universal links → Troubleshooting.

How do I test universal links locally?

Use a custom scheme for local testing:

adb shell am start -a android.intent.action.VIEW -d "yourappname://test"

See Universal links → Test for complete testing steps.

Event tracking

How do I verify events are being sent?

Check Logcat for event logs:

adb logcat | grep "Blueshift"

Go to Blueshift dashboard → Users → Search by device ID.
Check the user's activity timeline

See Testing SDK → Event tracking.

Where do I find my device ID?

The device ID is logged when the app starts. Check Logcat:

adb logcat | grep "Device ID"

Debugging

How do I enable debug logging?

Add this to your SDK configuration:

BlueshiftLogger.setLogLevel(BlueshiftLogger.VERBOSE)

See SDK setup → Enable logging.

How do I view SDK logs?

Use Logcat with the Blueshift tag:

adb logcat | grep "Blueshift"

Or use the Logcat window in Android Studio and filter by "Blueshift".

Live content

Live content returns null. Why?

A null response means no content is available. This happens when:

The slot doesn't exist in the dashboard
No active campaign is targeting the slot
The campaign is not targeting the current user
User identity (email/customer ID) is not set

Ensure user identity is set using identifyUser() before fetching live content.