AWS PINPOINT - NOTIFICATION PUSH FCM is rejecting requests because of deprecation of the legacy API

[FidelMaster]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

Not applicable

Amplify APIs

Push Notifications

Amplify Version

v6

Amplify Categories

No response

Backend

None

Environment information

 System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-12400
    Memory: 1.39 GB / 15.75 GB
  Binaries:
    Node: 18.12.1 - C:\Program Files\nodejs\node.EXE
    npm: 8.19.2 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @aws-amplify/react-native: ^1.0.7 => 1.0.7
    @aws-amplify/rtn-push-notification: ^1.2.7 => 1.2.7
    @babel/core: ^7.20.0 => 7.23.6
    @babel/preset-env: ^7.20.0 => 7.23.6
    @babel/runtime: ^7.20.0 => 7.23.6
    @react-native-async-storage/async-storage: ^1.21.0 => 1.21.0
    @react-native-community/masked-view: ^0.1.11 => 0.1.11
    @react-native-community/netinfo: ^11.2.1 => 11.2.1
    @react-native/babel-preset: ^0.73.18 => 0.73.18
    @react-native/eslint-config: ^0.73.1 => 0.73.1
    @react-native/metro-config: ^0.73.2 => 0.73.2
    @react-native/typescript-config: ^0.73.1 => 0.73.1
    @react-navigation/bottom-tabs: ^6.5.11 => 6.5.11
    @react-navigation/drawer: ^6.6.6 => 6.6.6
    @react-navigation/native: ^6.1.9 => 6.1.9
    @react-navigation/native-stack: ^6.9.17 => 6.9.17
    @types/react: ^18.2.6 => 18.2.45
    @types/react-test-renderer: ^18.0.0 => 18.0.7
    HelloWorld:  0.0.1
    amazon-cognito-identity-js: ^6.3.7 => 6.3.7
    amazon-cognito-identity-js/internals:  undefined ()
    aws-amplify: ^6.0.7 => 6.0.7
    aws-amplify/adapter-core:  undefined ()
    aws-amplify/analytics:  undefined ()
    aws-amplify/analytics/kinesis:  undefined ()
    aws-amplify/analytics/kinesis-firehose:  undefined ()
    aws-amplify/analytics/personalize:  undefined ()
    aws-amplify/analytics/pinpoint:  undefined ()
    aws-amplify/api:  undefined ()
    aws-amplify/api/server:  undefined ()
    aws-amplify/auth:  undefined ()
    aws-amplify/auth/cognito:  undefined ()
    aws-amplify/auth/cognito/server:  undefined ()
    aws-amplify/auth/server:  undefined ()
    aws-amplify/datastore:  undefined ()
    aws-amplify/in-app-messaging:  undefined ()
    aws-amplify/in-app-messaging/pinpoint:  undefined ()
    aws-amplify/push-notifications:  undefined ()
    aws-amplify/push-notifications/pinpoint:  undefined ()
    aws-amplify/storage:  undefined ()
    aws-amplify/storage/s3:  undefined ()
    aws-amplify/storage/s3/server:  undefined ()
    aws-amplify/storage/server:  undefined ()
    aws-amplify/utils:  undefined ()
    babel-jest: ^29.6.3 => 29.7.0
    babel-plugin-module-resolver: ^5.0.0 => 5.0.0
    babel-plugin-react-native-nodeify-hack: ^1.0.1 => 1.0.1
    base-64: ^1.0.0 => 1.0.0 (0.1.0)
    buffer: ^6.0.3 => 6.0.3 (4.9.2, 5.7.1)
    date-fns: ^3.0.0 => 3.0.0
    eslint: ^8.19.0 => 8.56.0
    jest: ^29.6.3 => 29.7.0
    moment: ^2.29.4 => 2.29.4
    prettier: 2.8.8 => 2.8.8
    process: ^0.11.10 => 0.11.10
    react: 18.2.0 => 18.2.0
    react-native: 0.73.1 => 0.73.1
    react-native-config: ^1.5.1 => 1.5.1
    react-native-date-picker: ^4.3.5 => 4.3.5
    react-native-device-info: ^10.12.0 => 10.12.0
    react-native-fs: ^2.20.0 => 2.20.0
    react-native-gesture-handler: ^2.14.0 => 2.14.0
    react-native-get-random-values: ^1.10.0 => 1.10.0
    react-native-image-picker: ^7.1.0 => 7.1.0
    react-native-paper: ^5.11.4 => 5.11.4
    react-native-pdf: ^6.7.3 => 6.7.3
    react-native-push-notification: ^8.1.1 => 8.1.1
    react-native-reanimated: ^3.6.1 => 3.6.1
    react-native-safe-area-context: ^4.8.1 => 4.8.1
    react-native-screens: ^3.29.0 => 3.29.0
    react-native-splash-screen: ^3.3.0 => 3.3.0
    react-native-stepper-ui: ^0.0.9 => 0.0.9
    react-native-toast-message: ^2.2.0 => 2.2.0
    react-native-url-polyfill: ^2.0.0 => 2.0.0
    react-native-vector-icons: ^10.0.3 => 10.0.3
    react-native-version-check: ^3.4.7 => 3.4.7
    react-test-renderer: 18.2.0 => 18.2.0
    rn-fetch-blob: ^0.12.0 => 0.12.0
    typescript: 5.0.4 => 5.0.4
    uuid: ^9.0.1 => 9.0.1 (8.3.2)
  npmGlobalPackages:
    react-native-cli: 2.0.1
    react-native: 0.74.3
    sequelize-cli: 6.6.2

Describe the bug

After create Push Notification Test Message from the console i receive the following error:

Expected behavior

create and receive notification in mobile app

Reproduction steps

1. Enter To Console
2. Go to Pinpoint Service
3. Send Push Notification using Test Message to Endpoint FCM

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[cwomack]

Hello, @FidelMaster and sorry to hear you're experiencing this. That error doesn't appear to be one that would come from the Amplify side, but rather from Pinpoint. Going to investigate this with the Pinpoint team and follow up as soon as I can.

[Samaritan1011001]

Hi @FidelMaster, thank you for opening this. Firebase discontinued use of their legacy method of authenticating their API calls which is why you are seeing that error.

You can update your Pinpoint console settings to use the new Firebase V1 method.

1. Generate a Key according to this section of the Firebase docs.
2. Upload the downloaded key to Pinpoint under Settings -> Push notifications -> Edit push notifications by selecting "Token credentials" and upload the json file from Firebase.

[FidelMaster]

Thanks @cwomack for your follow up, @Samaritan1011001 thanks for your advice this was the solution. greetings

[cwomack]

Good to hear! Thanks for confirming, @FidelMaster. We'll close this issue then and feel free to open another if you encounter any other blockers.