-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Firebase/InAppMessaging - Message display component is not present yet. No display should happen. #4768
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This comment has been minimized.
This comment has been minimized.
Hi @AngeloGiurano - thanks for the report. The instructions have been updated for the latest version of InAppMessaging (released yesterday) where the Display component is now part of Please make sure you run Let us know if that helps! |
@ryanwilson First of all thanks for the quick reply and flawless solution. I have been heavily testing to get back to you today, I've been able to display the In-App Messages but came up with a doubt The limit of one message per day to be displayed regards all In-App messages or just one per campaign? Because even if I create multiple campaigns with different names I'm getting this message
Please let me know if it is the desired outcome or I shall create another issue. Thanks once again and wish you a lovely day! |
I'm not sure personally but I'll reach out to the InAppMessaging team and get them to respond when they can, thanks! |
Hey Angelo! |
Hi @MeghaB, thank you for your reply and explanation, now everything is clear :) |
[REQUIRED] Step 1: Describe your environment
CocoaPods 1.7.5
[REQUIRED] Step 2: Describe the problem
I can not test the in app messages since they won't simply render, seems like there is an error in the rendering phase, since the message seems to be received:
Steps to reproduce:
Simply followed the documentation on https://firebase.google.com/docs/in-app-messaging/get-started
Tried both test on device and simply triggering a campaign but both of them fail on the render execution
Relevant Code:
Not applicable
The text was updated successfully, but these errors were encountered: