Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash triggered by [PFBaseSecureKeyWrapper getSignatureBytesUsingPrivateKey] #272

Open
patpatchpatrick opened this issue May 6, 2024 · 3 comments

Comments

@patpatchpatrick
Copy link

PayPal SDK Version

1.1.0

Environment

Both

Xcode Version

15.2

OS Version & Device

No response

Integration type

CocoaPods

Development Processor

Both

Describe the bug

Our app users are hitting crashes due to this line of code in iOS version 1.1.0 of the PayPal/PayPalNativePayments SDK.
(This crash has affected 31 users in the past 90 days.)

0x505b24 __75-[PFBaseSecureKeyWrapper getSignatureBytesUsingPrivateKey:data:completion:]_block_invoke + 72

Looks like a possible memory access issue.

Here is one example from crashlytics:
image

To reproduce

Unclear. I can't reproduce it myself but this crash has been reported 31 times in the past 90 days via our crashlytics dashboard.

Expected behavior

No crash

Screenshots

No response

@agedd
Copy link
Collaborator

agedd commented May 7, 2024

hi @patpatchpatrick 👋🏽 - thanks for bringing this issue to our attention. unfortunately, i've not been able to reproduce it on version 1.1.0. could you please try updating to our latest version 1.3.1 if possible and let us know if this issue still occurs.

@KunJeongPark
Copy link
Collaborator

KunJeongPark commented May 8, 2024

Hello @patpatchpatrick, we've forwarded this to team in charge of PayPalCheckout module to see if they can help.

I am also wondering if this is a new issue. When you started observing this behavior.
If you have some dates, we can see if there are any helpful logs.

Thank you for you patience.

@patpatchpatrick
Copy link
Author

It looks like it possibly started around April 18. I'm not seeing any logs of this crash prior to then.

I can try updating and see if the resolves this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants