The images in our carousel push notifications won’t appear on Android devices.
It might be due to a third-party conflict or push handling.
If you have a third-party push provider, the Insider push handler and the third-party push provider should not conflict. Push handling must be corrected in either case. For further information, refer to the push handling issues.
The images in our rich push notifications won’t appear on Android devices.
It might be due to a third-party conflict or push handling.
If you have a third-party push provider, the Insider push handler and the third-party push provider should not conflict. Push handling must be corrected in either case. For further information, refer to the push handling issues.
I can't connect to the panel with a QR code scan with an Android device.
Insider SDK might not be initialized properly. In the Android project, Insider SDK should be initialized with the Insider onCreate method right after the super.onCreate() call.
If you have multiple callers inside the onCreate method, some callers are asynchronous. In this case, Insider SDK initialization might have issues. That’s why you should initialize it right after the super.onCreate() call.
You should not initialize the SDK before the super.onCreate() call as it will not function due to the lifecycle.
In the app-level build.gradle file, there must be one manifestPlaceholders under the defaultConfig, and this manifestPlaceholders must include the same partner name as the Insider.Instance.init method.
We're having issues with splash screen adoption.
If the splash screen exists as splash fragments and other main fragments in one activity while your Android project adopts the single activity architecture, you should follow the steps for the splash screen in Android Initialize SDK, but delay the SDK initialization so that it does not init while the splash screen is active.
Also, remember to change the MySplashActivity.class in the following method:
Insider.Instance.setSplashActivity(MySplashActivity.class);Usage Notes for setSplashActivity
If your splash screen is not implemented as a separate custom Activity, you should not use the setSplashActivity method.
Example Scenario
If you display the splash screen inside your MainActivity, and that same activity also manages the main application UI:
- The session_start event may not be triggered correctly on app launch.
- Notification deeplinks may fail to work as expected.
Recommendation
Only use setSplashActivity when you have a dedicated splash Activity.
If you do not manage splash screen behavior in a separate Activity, we strongly recommend not calling this method.
How can we remove the Location methods from our Android project?
To remove the Location methods:
1. Go to the project manifest file.
2. Replace the following lines with the new lines.
| Status | Lines |
|---|---|
| Old | <uses-permission android:name="android:permission.ACCESS_FINE_LOCATION" /> |
| New | <uses-permission android:name="android:permission.ACCESS_FINE_LOCATION" tools:node="remove" /> <uses-permission android:name="android:permission.ACCESS_BACKGROUND_LOCATION" tools:node="remove" /> <uses-permission android:name="android:permission.ACCESS_COARSE_LOCATION" tools:node="remove" /> |
If needed, add xmlns:tools="http://schemas.android.com/tools to the top of the manifest tag.
How can we set a custom sound for push notifications?
To add custom sound to your push notifications:
- Add the sound file inside the project. If it is Android, add it to the raw folder under.
- Go to your panel to add the file name in Edit Campaign Options > Sounds.
To add a custom sound to Android 8.0 and above, you should use Custom Channels. You can select Custom Channels at the bottom of the Edit Campaign Options step. You can create a custom channel under Settings > Mobile Settings > Android Channels > Create Channel.