![]() ![]() Here is a quick example of how they can be used: public void splashScreenDismissed ( Context context) Troubleshooting In-App messages fail to showīatch might not be able to display the message: make sure all of the prerequisites are satisfied by your app. Since calling this makes Batch delete its reference to it to save memory, further calls might return null. (), allowing you to fetch the pending message (if any).(), allowing you to peek into the queue.Note: Disabling Do Not Disturb mode does NOT make Batch show the enqueued message Displaying pending mobile landingsĪfter coming back from DnD mode, you might want to show the enqueued message, as Batch will not do that automatically.īatch exposes two methods for managing the queue: Once you want to start showing messages automatically, call the method with false to turn it off. ![]() ![]() Now, when you don't want Batch to automatically display, turn on Do Not Disturb: Batch.Messaging. Turning on "Do Not Disturb" mode will make Batch enqueue the latest message, rather than display it. It allows you to tell Batch to hold on an in-app message for you, rather than display it without using the fully manual mode.įor example, if launching your app results in a splash screen or a fullscreen ad, you might find it undesirable to have Batch display something on top of it. You can also get more control on when messages are displayed without giving up on the automatic mode, by using the "Do Not Disturb" (DnD) mode. Controlling the display using "Do Not Disturb mode" The automatic mode will only work properly if Batch is well integrated into ALL of your activities. If they don't, please head over to the troubleshooting section. Create some campaigns on your dashboard, and they will start There is no code required to make In-App Messages work in automatic mode.
0 Comments
Leave a Reply. |