Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Messaging and Campaigns not sending push since today to Android devices #3635

Closed
MewanWA opened this issue Sep 4, 2024 · 3 comments
Closed
Labels
pending-maintainer-response Issue is pending response from an Amplify team member question General question

Comments

@MewanWA
Copy link

MewanWA commented Sep 4, 2024

State your question
I am getting an error regarding usage of deprecated API when I try to send a Test Push Notification via AWS Pinpoint. My question is basically, do we need to update our SDK version or is this something AWS needs to from their end? Even through segments, notifications do not seem to be received on Android while iOS works as expected.

The error is below:

Message not sent: We weren't able to send your push message to da...Rlq. Request Id 89 : [daz...Rlq: PERMANENT_FAILURE {"errorMessage":"Invalid Credentials","channelType":"GCM","pushProviderStatusCode":"301","pushProviderError":"FCM is rejecting requests because of deprecation of the legacy API","pushProviderResponse":"{\"error\":\"Deprecated endpoint, see https:\\/\\/firebase.google.com\\/docs\\/cloud-messaging\\/migrate-v1\"}"}]

Which AWS Services are you utilizing?
Pinpoint

Provide code snippets (if applicable)

Environment(please complete the following information):

  • Pinpoint SDK Version: com.amazonaws:aws-android-sdk-pinpoint:2.69.0
  • AmplifyCore version com.amplifyframework:core:1.4.1

Device Information (please complete the following information):

  • Device: Simulator and Samsung Galaxy A04e
  • Android 10-12
  • Specific to simulators: No

If you need help with understanding how to implement something in particular then we suggest that you first look into our developer guide. You can also simplify your process of creating an application, as well as the associated backend setup by using the Amplify CLI.

@github-actions github-actions bot added pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Sep 4, 2024
@tylerjroach
Copy link
Member

It appears that you need to reconfigure your Firebase + Amplify connect with Firebase's service account key (json) file. Firebase shut down legacy API usage.

See this page for the guide to use the service account key instead: https://docs.amplify.aws/gen1/android/sdk/push-notifications/setup-push-service/. See this notice from Firebase: https://firebase.google.com/docs/cloud-messaging/migrate-v1

@tylerjroach tylerjroach added question General question and removed pending-triage Issue is pending triage pending-maintainer-response Issue is pending response from an Amplify team member labels Sep 4, 2024
@MewanWA
Copy link
Author

MewanWA commented Sep 5, 2024

That seemed to be the issue. Thank you @tylerjroach!

@MewanWA MewanWA closed this as completed Sep 5, 2024
Copy link
Contributor

github-actions bot commented Sep 5, 2024

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

@github-actions github-actions bot added the pending-maintainer-response Issue is pending response from an Amplify team member label Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-maintainer-response Issue is pending response from an Amplify team member question General question
Projects
None yet
Development

No branches or pull requests

2 participants