[iOS] paymentToken not present on real device

[Andreyco]

Yesterdays production deployment kinda surprised me.

When testing in sandbox/production on device, paymentToken got lost. On simulator, it works perfectly.

Despite token arrives into JS "accept" handler , it does pass _getPlatformDetailsIOS
The fact it works on simulator is an accident, present on these lines

return Object.assign({}, details, {
    paymentData: null,
    serializedPaymentData
});

Calling Object.assign copies whatever is present in details object and passes it further.
Unfortunately, for real device, returned values are hand picked.

In both cases, return values should be hand picked to make sure they are equal in shape and/or values.

I am aware of #21 PR, I will try to build on that (unfortunately found the PR after my fix)

Offtopic:
Apple review passed, this lib is definitely safe for work!

[Andreyco]

Several questions... Should we have access to serializedPaymentData? Isn't it sufficient to keep original/unserialised data?

[Andreyco]

PR provided, open to discussion.

[naoufal]

Just getting to this now.

I decided to expose serializedPaymentData so that users always have access to the original Apple Pay response.

Separately, I don't parse it on the native side, because the bridge serializes it before sending it over to JS.

[Andreyco]

I decided to expose serializedPaymentData so that users always have access to the original Apple Pay response.

Deserialising that data does not destroy any of original response, correct?