Azure Notification Hubs - Issues with Tags after FCM Migration

MooreJohnJ-6039 0 Reputation points

After migrating all our android installations to FcmV1, I'm seeing odd behavior that didn't exist prior to the migration.

I have two subscriptions each with a notification hub and they're exhibiting different behavior when sending template notifications. When I use the tag expression, {Default && attribute:value}, Notification Hub A sends it to both my iOS and Android devices, but the Notification Hub B only sends it to my iOS device.

I've included the difference in the message telemetry below.

Notification Hub A

  • I received the notification on iOS and Android
  • Target platforms only show apple
  • Shows the outcome results for both Apns and FcmV1
    User's image

Notification Hub B

  • I received the notification on iOS only
  • Target platforms only show apple
  • Shows the outcome results for Apns and no attempts for FcmV1 User's image

Now here is the kicker: When I change the order of the tags to attribute:value && Default, both notification hubs work as expected with the exception of the telemetry still only showing apple as the target platform.

I would appreciate any ideas on what could be causing this behavior.

Azure Notification Hubs
Azure Notification Hubs
An Azure service that is used to send push notifications to all major platforms from the cloud or on-premises environments.
298 questions
0 comments No comments
{count} votes