CallbackReceiver

interface CallbackReceiver<T>

An objects that can receive remote callbacks.

Remote callbacks provide an easy way to bundle arguments and pass them directly into a method rather than managing PendingIntents manually.

Example:

public class MyReceiver extends BroadcastReceiverWithCallbacks {
  public PendingIntent getPendingIntent(Context context, int value1, int value2) {
    return createRemoteCallback().doMyAction(value1, value2)
        .toPendingIntent(context);
  }

  \@RemoteCallable
  public MyReceiver doMyAction(int value1, int value2) {
    ...
    return this;
  }
}

The following types are supported as parameter types for methods tagged with RemoteCallable.

• byte/Byte/byte[]
• char/Character/char[]
• short/Short/short[]
• int/Integer/int[]
• long/Long/long[]
• float/Float/float[]
• double/Double/double[]
• boolean/Boolean/boolean[]
• String/String[]
• Uri
• Context *

This interface shouldn't be implemented in apps, instead extend one of the implementations of it provided.

• BroadcastReceiverWithCallbacks
• AppWidgetProviderWithCallbacks
• ContentProviderWithCallbacks

Just like PendingIntents, Remote Callbacks don't require components be exported. They also ensure that all parameters always have a value in the PendingIntent generated, which ensures that the caller cannot inject new values except when explicitly requested by the receiving app. They also generate the intent Uris to ensure that the callbacks stay separate and don't collide with each other.

Summary

fun createRemoteCallback(context: Context!): T!

    createRemoteCallback().callMyMethod("My arguments", 43, 2.4)
             .toPendingIntent(context);

    \@RemoteCallable
    public RemoteCallback callMyMethod(String argStr, int argInt, double argDouble) {
        ...
        return RemoteCallback.LOCAL;
    }