-
Notifications
You must be signed in to change notification settings - Fork 18
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
App Crash in iOS 18.0.1 #221
Comments
I am also facing the same : |
i also faced this issue.... with iOS-18.1.0 this is resolved. had raised this issue to Razorpay over email, but received a revert stating this is not at their end. |
Hey folks, this issue was related to Webkit. There wasn't anything we could have done about this. We tried to reproduce this on our end as well but were unable to do so. So currently we are only waiting to see if the next versions of Webkit have a fix for this. |
Description
Our iOS app is experiencing a crash in the background on iOS 18.0.1, specifically during the checkout process when the Razorpay SDK is invoked. The crash appears to occur either when initiating the Razorpay payment screen or while the screen is active. According to our Crashlytics logs and crash report, the issue seems to be linked to Razorpay's CrashReporter module, with WebKit also involved in the stack trace. This is significantly impacting app stability, particularly in asynchronous background operations, and we would appreciate guidance on resolving this to prevent further crashes.
Razorpay pod Version :
1.3.6
Xcode Version :
Version 15.3 (15E204a)
What you did:
What happened:
crash log:
The crash typically occurs during the checkout process, specifically when loading the Razorpay payment screen in the app. Here’s an excerpt from the crash log:
This trace suggests the crash might be occurring due to an unhandled exception within Razorpay's CrashReporter during the checkout process, potentially involving WebKit.
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
The text was updated successfully, but these errors were encountered: