[🐛] In-app-messaging pop up is not triggered and not showing.

[NikolayChankov90]

I am with
"react-native": "0.76.6"
"@react-native-firebase/analytics": "^21.12.0",
"@react-native-firebase/app": "^21.12.0",
"@react-native-firebase/in-app-messaging": "^21.12.0",
"@react-native-firebase/messaging": "21.6.1",

i have installed the in-app-messaging library and configured:
Firebase.json

"messaging_android_notification_channel_id": "default",
"in_app_messaging_auto_collection_enabled": true

app.ts

  inAppMessaging().setMessagesDisplaySuppressed(false);
  inAppMessaging().setAutomaticDataCollectionEnabled(true);
  inAppMessaging().triggerEvent('on_login');
  inAppMessaging().triggerEvent('on_foreground');
  firebase.analytics().logEvent('event_name');

android/build.gradle
classpath 'com.google.gms:google-services:4.4.1'
android/app/build.gradle
apply plugin: 'com.google.gms.google-services'

Firebase message pop up is configured for my stg app , all registered , i have used firebase before in the app for push notifications .

The in app message configs are to trigger on_foreground

What else do i have to do ? Or what have i done wrong ?

[mikehardy]

Hey there - one thing that jumped out at me:

"@react-native-firebase/in-app-messaging": "^21.12.0",
"@react-native-firebase/messaging": "21.6.1",

You have mismatched versions, this should never be done: https://invertase.io/blog/react-native-firebase-versioning

I have noticed in analytics-interaction / campaign-membership type events that the devices were very slow to register themselves as being in a campaign or not - that is, I was seeing failures in my testing on my apps for things that depended on being part of some campaign or another because the device had not registered as part of the targetted group. I never could figure out exactly why but I personally avoided those features.

That's not a great final solution and I am not suggesting it is. However it may open up an avenue to test your implementation and see if that is the problem. Is it possible for to either force device membership in a campaign, or otherwise work around target group / campaign membership targetting and have the in-app-message popup every single time or trigger it for a specific device using the specific device ID?

[NikolayChankov90]

@mikehardy thanks for noticing i will check on the versions .
For the device ID, i could not see it in the LogCat for some reason, i left the issue aside to attack 🗡 it on a fresh brain tomorrow :D
Thanks again. I will get back , if that helped

[MichaelVerdon]

Hey there @NikolayChankov90 any updates on making the versions match? I can also confirm that it is a known issue internally that devices were slow to recognise themselves as being part of a campaign as Mike was saying so I would advise if you have not tested it out already that to give it a good amount of time.