Closed enzzoperez closed 9 months ago
@enzzoperez, sorry to hear that you're experience this! Can you clarify if any recent upgrades were made to either the aws-amplify
package or another dependency that resulted in these errors happening? Are the consistently reproducible for every notification on the Android device or more sporadic? Hoping to get you unblocked ASAP.
Thanks for response @cwomack .. No, we didnt make any changes/upgrades related to aws packages (ws-amplify
nor @aws-amplify/rtn-push-notification
), days ago the notifications was working well. We were trying to move to some previous version of our app, clean deps and re-build, but we got the same results.. And as you say, all notifications that we sent broke the app
udpate: we had to uninstall the @aws-amplify/rtn-push-notification
package, then the pre-launch report told us that the bug was gone
we previously tried to downgrade versions of this package and aws-amplify, but the error remained
Hi @enzzoperez, I was only able to reproduce the error you mentioned in the description when using an older version of @aws-amplify/rtn-push-notification
.
Keeping all the other packages the same version as you show in the image above, can you only upgrade the @aws-amplify/rtn-push-notification
to 1.2.12
and see if that solves the problem? I am trying to track down the root cause but upgrading as I mentioned solved it in my reproduction. Hope this helps.
This is my version set for reference,
"dependencies": {
"@aws-amplify/rtn-push-notification": "~1.2.12",
"@react-native-async-storage/async-storage": "^1.21.0",
"@react-native-community/netinfo": "^9.5.0",
"aws-amplify": "~5.3.11",
"react": "18.2.0",
"react-native": "0.71.5",
"react-native-get-random-values": "^1.10.0",
"react-native-url-polyfill": "^1.3.0"
},
Hi @Samaritan1011001 , sorry about delay, upgrading to rtn v1.2.12 works, thanks. Previously I'm upgrading to amplify v6 and also worked, so I thinks that I'll take the new version of package .. again, thanks for you workaround!
Okay... I'm having the same issue, but problem is I can't upgrade rtn-push-notification because I'm using v5, and according to the docs. V5 doesn't work with later versions of rtn-push-notification. What can I do? If nothing, I think that v5 documentation should be updated to state it can't handle notifications.
Update, despite being on v5, I upgraded rtn-push-notification to the latest version, and it worked (contrary to what the docs said). Not sure if I should leave it like that thought, I imagine the docs suggest you use 1.1.x. on v5 for a reason.
Before opening, please confirm:
JavaScript Framework
React Native
Amplify APIs
Push Notifications
Amplify Version
v5
Amplify Categories
notifications
Backend
None
Environment information
Describe the bug
Hi, how are you?.. Im having issues ONLY ANDROID with push notification, It was working until some days, then the pre-launch report from google play informed us about this bug.. later we builded the app and we were testing the notifications with aws pinpoint test messaging and when the phone receive the notification we get the same bug that google give us, a NRA error, on Iphone the notifications is working fine..
At this time we dont touch anything about notifications, module, version or packages
this is the message:
java.lang.RuntimeException: Unable to create service com.amazonaws.amplify.pushnotification.PushNotificationFirebaseMessagingService: java.lang.ClassNotFoundException: Didn't find class "com.amazonaws.amplify.pushnotification.PushNotificationFirebaseMessagingService"
Expected behavior
get a notification on android
Reproduction steps
Follow guide to install V5 push notifications modules on react native Try to send a push notification with aws console
Code Snippet
Log output
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