setMessageDisplayComponent

Makes messageDisplay render the messages, in place of the default UI. It must report what happens to the message through the FirebaseInAppMessagingDisplayCallbacks it is given, so that the SDK records the impression and click and moves on to the next message.

• Android: the display SDK binds its own component again whenever an activity resumes, so a custom component only stays in place in an app that excludes com.google.firebase:firebase-inappmessaging-display.

• Apple platforms: messageDisplay runs on the main thread (the iOS SDK calls its display component on a background thread). When the user clicks an action the iOS SDK opens its URL itself, while on Android that is up to the component.

Sets the iOS SDK's messageDisplayComponent: the iOS SDK's own default UI for com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay (none on tvOS, which then displays nothing), or else a component that converts each message and calls messageDisplay on the main thread.

Makes messageDisplay render the messages, in place of the default UI. It must report what happens to the message through the FirebaseInAppMessagingDisplayCallbacks it is given, so that the SDK records the impression and click and moves on to the next message.

• Android: the display SDK binds its own component again whenever an activity resumes, so a custom component only stays in place in an app that excludes com.google.firebase:firebase-inappmessaging-display.

• Apple platforms: messageDisplay runs on the main thread (the iOS SDK calls its display component on a background thread). When the user clicks an action the iOS SDK opens its URL itself, while on Android that is up to the component.

Does nothing: no message is displayed on the JVM.