Contact person: Fix FCM Bulk Notification Bug

Phone:Show

Email:Show

Location: India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"My multiservice platform combines ride-hailing and food delivery, and the driver app relies on Firebase Cloud Messaging for every critical alert—trip requests, order pick-ups, status updates, the works. When I trigger a bulk push (for example, surge-pricing or broadcast promos) some drivers receive a totally blank notification or receive it several minutes late. The behaviour is the same across every released build on both Android and iOS.

What I need is a clean, systematic fix. I’m looking for someone to:

• Audit the FCM implementation end-to-end—from payload structure and message type (data vs notification) to server-side throttling, token handling, and APNs configuration.
• Pinpoint why certain devices render an empty notification body and why delivery is delayed in larger batches.
• Patch the code or configuration so every driver gets a complete, timely push on the first try, no matter the OS version or device model.
• Provide a concise technical note summarising the root cause, the changes made, and any monitoring hooks or retry logic you add so we can track reliability going forward.

I’ll supply source access, existing Cloud Functions (Node.js), and sample payloads for testing. Final acceptance is simple: trigger a 1,000-device broadcast in staging and verify that all test phones display the full notification content within an acceptable delivery window (seconds, not minutes)." (client-provided description)