Closed raquelmsmith closed 2 years ago
@raquelmsmith I have only been using this library today but haven't seen this issue. That is very strange though. Is it possible your logging system is somehow injecting that date stamp? I don't see any date stamps in the raw JSON body from Apple.
I'm using the library in production and I've never received a payload like that. How are you logging the token? It looks to me like your logging solution splits the token into two output. The timestamp is the prefix to the second output.
I'll go ahead and close this issue since I'm fairly confident it's related to how the token is logged to the console. Feel free to open an issue again if you are still experiencing problems.
When I use this library with the signedPayload from Apple I am getting an error:
This doesn't surprise me - when I was researching this project I took the signed payload from Apple and just manually decoded it myself. However, Apple says there are three encoded strings separated by
.
. However, in the string that is sent over there are actually four. That is because in the middle of one of the strings there is a timestamp. I have received multiple payloads from Apple and am seeing this in all situations.In the below payload you'll see:
(space) after the Z.
2022-05-20T21:43:16.046463081Z
with a.
before the milliseconds and aI was hoping that this library would know how to handle it, but alas. Do you have any ideas what should be done with this payload? Are you seeing the same thing in your projects using this library?