Android Push Handling

    Reteno.initWithConfig(
        RetenoConfig.Builder()
            .accessKey(...)
            .defaultNotificationChannelConfig { builder ->
                builder
                    .setName("Custom name")
                    .setDescription("Custom description")
                    .setImportance(NotificationManagerCompat.IMPORTANCE_HIGH)
                    .setLightColor(Color.RED)
                    .setLightsEnabled(true)
                    .setShowBadge(true)
                    .setVibrationEnabled(true)
                    .setVibrationPattern(longArrayOf())
                    .setSound(...)
            }
    )
    .build()

    Reteno.initWithConfig(
        new RetenoConfig.Builder()
        .accessKey(...)
        .defaultNotificationChannelConfig((builder) -> {
            builder
                .setName("Custom name")
                .setDescription("Custom description")
                .setImportance(NotificationManagerCompat.IMPORTANCE_HIGH)
                .setLightColor(Color.RED)
                .setLightsEnabled(true)
                .setShowBadge(true)
                .setVibrationEnabled(true)
                .setVibrationPattern(longArrayOf())
                .setSound(...);
            return Unit.INSTANCE;
        })
        .build()

For handling deeplinks on Android12+, keep in mind the recent changes as explained at developer.android.com

Also, make sure to set up the proper intent filter for your activity developer.android.com

It is important to add a <meta-data> tag containing the com.reteno.Receiver.PushReceived and com.reteno.Receiver.NotificationClicked names of your receivers so that the SDK will be able to trigger them.

The data key name is optional but recommended. You can use any other name.
We do not recommend using the notification key name to specify the name of the object in JSON and the es_interaction_id key name inside JSON.