Skip to content
This repository has been archived by the owner on Jun 23, 2021. It is now read-only.

Will CargoBay break in-apps verification after February 14, 2016? #81

Closed
xjki opened this issue Jan 20, 2016 · 11 comments
Closed

Will CargoBay break in-apps verification after February 14, 2016? #81

xjki opened this issue Jan 20, 2016 · 11 comments

Comments

@xjki
Copy link

xjki commented Jan 20, 2016

Apple WWDR Certification Intermediate Certificate is expiring February 14, 2016 and new certificate is issued.

CBCheckReceiptSecurity function that checks receipt security uses intermediate certificate (marked with FIXME comment in code) - see in code

Question - will validation of in-app purchases/restore using CargoBay will break after February 14, 2016?

Setting date on device after Feb 14, 2016 + restarting device + restoring old purchases still worked but not sure if it will accept/validate purchases made after Feb 14, 2016 with new certificate in receipts?

@xjki xjki changed the title Will CargoBay break after February 14, 2016? Will CargoBay break in-apps verification after February 14, 2016? Jan 20, 2016
@jam
Copy link

jam commented Jan 20, 2016

I was just about to post asking the same question. If this is the case, we have very little time to get a new update submitted and approved, so a quick response would be greatly appreciated 😄

@jam
Copy link

jam commented Jan 26, 2016

I've extracted the cert from the code & checked the date - it's due to expire on May 18th, so there's a little less urgency now 😄

@xjki
Copy link
Author

xjki commented Feb 3, 2016

@jam If cert (new one?) received in the transaction receipt from App Store will not match one included in the Cargo Bay, verification will fail anyway.

It seems that Cargo Bay does not support new way of validating app and in-app purchases, as I understand it uses (pre-iOS7 way of processing validating purchases) transactionReceipt from transaction data, not from receipt stored with app itself.

@gnatok
Copy link

gnatok commented Apr 7, 2016

Happens to us already. Seems weird but definitely certificate.
Some DIY fix?

@xjki
Copy link
Author

xjki commented Apr 8, 2016

@gnatok Are you sure? Mines verifies using existing code, thou I added DIY extra steps (validating transaction remotely) if Cargo Bay default verification fails. As far as I can see in my analytics there are less than 1% verification fails and these are isolated incidents from few users (hacking attempts perhaps?)

@gnatok
Copy link

gnatok commented Apr 8, 2016

@xjki production version is Ok. But new build was rejected by Apple Because payments fail. Seems they changed something on Sandbox side.
Yesterday we disable local validation inside CargoBay and we successfully made purchase with sandbox user.

@xjki
Copy link
Author

xjki commented Apr 8, 2016

@gnatok I see, that makes sense.

@ccombes
Copy link

ccombes commented May 3, 2016

Aside from validation, any guess as to how much longer the old receipt format will be accepted for purchases in production?

@ren6
Copy link

ren6 commented May 18, 2016

Today I found that validating in-app purchases no longer works! Please update your apps by changing/removing validation

@antongaenko
Copy link

as quick workaround: just comment local validation as here https://github.com/abaenglish/CargoBay/tree/master and all should work
pod 'CargoBay', :git => 'https://github.com/abaenglish/CargoBay'

@mkral
Copy link

mkral commented May 26, 2016

Man I wish I knew about this prior, really messed up some IAP workflows. Thanks for the quick fix @Just-

@mattt mattt closed this as completed Jun 22, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants