test(messaging): cloud function sendFCM feature for messaging testing

[mikehardy]

Description

I have a large backlog of issues on Notifee, plus a couple issues in react-native-firebase that are related to messaging problems with FCM handling

I can'd diagnose those easily unless I can easily trigger an FCM to a specific device

This PR adds a new cloud function for testing that will take a TokenMessage (basically a regular FCM but with a device token in it) and just reflect that Message right back to the token, with an optional delay

As mentioned in the commit, it will only work if you have the correct google-services files and use the correct package names and even then on iOS it will only work if you have the Xcode developer profile installed for the com.invertase.testing bundle. So I'm not sure how it could be abused, even if you somehow knew some devices "react-native-firebase-testing" project-specific device token

Related issues

Too many to list, but all related to incorrect handling of FCM in various app states on various platforms

Here's one:

• RN 0.76+ Android + old-arch only - opening notification when the app is killed crashes on start #8131

Release Summary

All conventional commits, but also none of them will trigger release, they're all build or test

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

deploy function cd .github/workflows/scripts/functions && yarn deploy

Execution of function:

 const fcmRequest = await fetch(
      'https://us-central1-react-native-firebase-testing.cloudfunctions.net/sendFCM',
      {
        method: 'POST',
        headers: {
          'Content-Type': 'application/json',
        },
        body: JSON.stringify({
          data: {
            delay: 5000,
            message: {
              // TODO all the mesage stuff here
              token: await firebase.messaging().getToken(),
              notification: {
                title: 'hello world title',
                body: 'hello world body',
              },
            }
          },
        }),
        redirect: 'follow',
      },
    );
    const { result } = await fcmRequest.json();
    console.log('got sendFCM result: ' + JSON.stringify(result, null, 2));
  };

watch react-native console logs

got sendFCM result: {
"messageId": "projects/react-native-firebase-testing/messages/0:1731783390638267%6b3c7cd26b3c7cd2"
}

watch firebase function logs:

https://console.cloud.google.com/logs/query;query=%2528resource.type%3D%22cloud_function%22%20resource.labels.region%3D%22us-central1%22%2529%20OR%20%2528resource.type%3D%22cloud_run_revision%22%20resource.labels.service_name%3D%2528%22sendfcm%22%2529%20resource.labels.location%3D%22us-central1%22%2529;cursorTimestamp=2024-11-16T18:47:18.873543Z;duration=PT1H?authuser=0&project=react-native-firebase-testing&hl=en&inv=1&invt=AbhpwQ

---

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-native-firebase	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 16, 2024 7:30pm

[mikehardy]

There is no way to test functions without actually deploying them, so this is already actually deployed

Given that, I'm going to merge it so that source tree state matches deployed state of the cloud functions but I'll be clear: very happy to make any follow-on PRs related to review on this one if something looks off...