-
Notifications
You must be signed in to change notification settings - Fork 479
Unable to bind to service com.paypal.android.sdk.payments.PayPalService #117
Comments
Minor nitpick: latest SDK is 2.7.3 Also, are you setting your clientId? |
Can you specify what "time to time" means? When do you start/stop the service? This error only occurs if the intent or its extras are null. |
Wow! New versions appears so fast :) I'll update to the latest one tomorrow, before app release.
This crash appears only in production mode. Service starting in onCreate(), before starting PaymentPayPalActivity. Destroying service are done in onDestroy(). "From time to time" means that is appears approximately for 1% of users, and are not reproducible on sandbox environment. |
So you're not able to reproduce this yourself in the production environment? Do you notice if the crashing occurs on a certain set of devices, or is the distribution pretty even across device types? We haven't seen this error in any of our testing, so it leads me to believe there are other factors at play. |
I was able to reproduce this issue, although not intentionally. I believe it occurs when the something has been cleared from memory, and the service attempts to restart itself. |
Yes, you are right, I'm not able reproduce it neither on sandbox mode not in production mode. Looks like it appears without any dependencies to device or Android version. |
It happened when I left our sample app backgrounded overnight while in the middle of testing. When I tried to open the app again the next day, something changed, and we see the crash. If you have a device lying around, I'm sure you can test and may see the same behavior. |
Ok! I'll check it in that way! |
Your steps for reproducing bug is correct! I've reproduced the bug. I've left paypal app opened for long time (near 3-4h) and then after unlocking phone try press button "Pay" - app was crashed. |
Excellent! We're working on fixing this, as well as some other defects at the moment. Thanks for your patience! |
Can't wait for the fix to be released. I ran into the same issue according to a Crashlytics report. |
Fixed in 2.8.2+. |
Please make note of the release notes, and the recommended changes to the integration. |
Hello guys!
In my app, I'm using the latest SDK (2.7.1) and starting service like described in sample app:
I'm sure that intent is not null and extras also are not null, but from time to time I'm getting such error:
Also the same error appeared on previous SDK versions.
The text was updated successfully, but these errors were encountered: