What you actually want to use is the FirebaseMessaging token which can be accessed by attaching a listener to a call to FirebaseMessaging.getInstance(). whilst the InstallationTokenResult does have a token property associated with it it.result.token is not what I should have been passing to registerDeviceToken anyway facepalm. I remember having to rewrite this code, and my thought process was "These methods have the word token in them, i'll just stringify that".
PINPOINT AWS BAD UPDATE
The result of this update was some changed APIs. I remember a while ago I updated the versions of my various Firebase dependencies. I was calling registerDeviceToken with a stringified representation of the result property.
I found what I believed to be the offending code, and immediately noticed that Task was being passed to the closure. This looked like the issue, but I stupidly made the assumption that Pinpoint wouldn't allow you to set an invalid device token. I checked the output for an iOS device which was indeed a string. On thing that did look untoward was the Address property which looked like a stringified representation of an object rather than a. The response I was getting looked correct, and the OptOut property that I'd been having issues with on iOS was correctly set to NONE. It essentially lists all the iOS/Android devices and email addresses associated with a given user. One of the functions I have written lists all the endpoints for a given user ID. I utilise Amazon Pinpoint for managing push notifications and I have a little test node script for testing if things are working correctly. Given that (similar to my iOS setup) both the Training Plan and Activity Filter apps were using the same code for push notification functionality I went ahead and checked if notifications were working in the Training Plan app. I was implementing push notification into the Activity Filter Android app, and noticed that they were not working having previously encountered completely different issues when implementing them on the iOS app.
0 kommentar(er)
