JSONDecodeError(Optional(""))??

[michaelsousa21]

I keep getting this error when I try to verify the receipt. How can I fix this?
I'm running the iOS version on xcode 7.3.1

Debug Output:
CoreFoundation = 1145.150000
Purchase Success: com.testapp.inapp10
Verify receipt Failed: JSONDecodeError(Optional(""))

[phimage]

In InAppReceipt, verifyfunction we receive safeData so no .NoRemoteData error
But data seems empty so no receiptInfo. Maybe another exception must be throw for that case.

[odedharth]

Also received this error after a verification of a successful purchase.
Any update on this?

[bizz84]

I created a PR to return .NoRemoteData when the receipt data is empty: #64

@odedharth @michaelsousa21 Can you try running on this branch? https://github.com/bizz84/SwiftyStoreKit/tree/feature/JSONDecodeError-empty-data

Note that with this change receipt verification will still fail, it just returns a different error case.

[odedharth]

@bizz84 As I understand the problem it seems that from some reason the purchase succeeds but the verification is failing. So I'm wondering that maybe the problem is with the purchase function, and not the verification function. Because if a purchase succeeds the verification should be successful.

[jayvenn]

So my purchase succeeded but my verification fail. However, my verification did not fail at first but then "one day" it failed. Something must have changed perhaps on iTunes Connect. Perhaps it is sandbox?

[bizz84]

@michaelsousa21 @nhantrivinh I still need to investigate this further. I'm going to label this as a bug for now.

[HyunjoonKo]

Hi.

The same thing happened to me. The user succeeded in the purchase, but the receipt was not decoded, so the app failed to purchase it. So the user made 10 payments in a row. Is there a way to avoid this?

[bizz84]

There have been some significant improvements to the purchase flows recently.

@michaelsousa21 @nhantrivinh @HyunjoonKo can you retest this with the latest version, and let me know if it works correctly now?

[bizz84]

@michaelsousa21 @nhantrivinh @HyunjoonKo Closing this issue. Feel free to open a new one if there are still issues. Current release is 0.9.0.