"ppapi_error_code_10870 - Please go to the App Store to install the latest version of the PayPal app.

[paypal]

"ppapi_error_code_10870 - Please go to the App Store to install the latest version of the PayPal app.

[dgoldman-pdx]

Thanks, @parkej60. I'll pass this along to the people in charge of our Sandbox server. There seem to be some intermittent problems there.

[parkej60]

@dgoldman-ebay It doesn't seem intermittent at all to me. Since yesterday morning I just haven't been able to connect using the sandbox.

[dgoldman-pdx]

@parkej60 I'll let the Sandbox people know. Thanks!

[dgoldman-pdx]

@parkej60, I just wanted to provide an update.

We've now got over a dozen people inside PayPal looking into this. I have found a way to reliably reproduce your issue on Sandbox but not on Production, same as your experience.

There seem to be some odd things going on in Sandbox that are incorrectly triggering this error. I'm hoping that somebody from that team will be able to get to the bottom of this quickly!

[dgoldman-pdx]

@parkej60, we're still looking into this. I hope to have something more useful to tell you very soon!

[parkej60]

It appears the latest build which supports iOS 7 has fixed this.

[samskiter]

this issue still exists

We are using the client ID and corresponding text account as listed under the api credentials "test credentials" section.

The error we receive is:

Request failed with error:"ppapi_error_code_10870 - Please go to the App Store to install the latest version of the PayPal app.
PayPal debugId: 20d505b59cd94"

We are able to successfully bring up the payment screen with the production details

[dgoldman-pdx]

@samskiter sorry to see this issue back again! (I'm reopening this github issue now.)

The upshot when we investigated the original report 6 months ago, and so far today in investigating your report, is that it looks like some Sandbox server(s?) contains bad code. This code ends up thinking that your requests from mSDK 1.4.6 are actually coming from version 1.4.6 of a completely different PayPal mobile app.

If you're still getting the same error on Sandbox tonight, could you hit it maybe 4 more times, and tell us the 4 resulting debugIds? That will help us investigate whether there is a particular server common to these errors.

Fortunately, both your experience and @parkej60's original experience have so far indicated a problem only on Sandbox, and not on Production.

[samskiter]

just hit it a bunch this morning. Debug id's coming in pairs (probably because I'm using the 'prepareForPaymentUsingClientId' call). Here they are:

1:
c17d9138f1090
cb660b9614bed

2:
e1a06633c31fd
985b8e357ccb

3:
c342c02e48e6d
eea565cad6ca9

4:
d020d5046d0c7
ecfa08afbd9d6

[dgoldman-pdx]

@samskiter thanks for hanging in there! I've got bad news and good news.

The bad news: so far we haven't found a pattern as to why some connections to Sandbox succeed and others fail.

The good news: this should all become irrelevant next week. As just announced yesterday, version 2.0 of the PayPal mobile SDK will be released on Monday, Feb 24. One of the differences in the new version of the mSDK is that we have now switched all server calls to the new PayPal REST APIs. That means that the old-style authentication API we use in version 1.x, which is generating your errors, will no longer be in play.

When the new version of the mSDK becomes available on Monday, it will probably take you an hour or so to integrate into your app. And then all should be good!

[samskiter]

Thank-you. I will take a look on Monday at integrating this.

[dgoldman-pdx]

Fixed (I certainly hope!!!) in the just-posted mSDK 2.0.0.