-
Notifications
You must be signed in to change notification settings - Fork 107
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
'RazorpayCheckout' has different definitions in different modules; first difference is defined here found 1 referenced protocol #292
Comments
Hey @niyasmhdth , can you try running the project in xcode first and share the error logs here |
I think the issue is with xcode 12 , the update came out today, and my mac
has auto update, so it updated my xcode from 11 to 12, now I downloaded
xcode 11 and it works fine
…On Thu, 17 Sep 2020 at 6:12 PM, Sachin Nautiyal ***@***.***> wrote:
Hey @niyasmhdth <https://github.com/niyasmhdth> , can you try running the
project in xcode first and share the error logs here
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#292 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKRT4KQVPWYK6E4WWEPSIV3SGH74NANCNFSM4RQFXYJQ>
.
|
*@interface* RazorpayCheckout : NSObject <RCTBridgeModule>
'RazorpayCheckout' has different definitions in different modules; first
difference is defined here found 1 referenced protocol
…On Thu, Sep 17, 2020 at 6:20 PM Niyas Mhd ***@***.***> wrote:
I think the issue is with xcode 12 , the update came out today, and my mac
has auto update, so it updated my xcode from 11 to 12, now I downloaded
xcode 11 and it works fine
On Thu, 17 Sep 2020 at 6:12 PM, Sachin Nautiyal ***@***.***>
wrote:
>
>
> Hey @niyasmhdth <https://github.com/niyasmhdth> , can you try running
> the project in xcode first and share the error logs here
>
>
>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#292 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AKRT4KQVPWYK6E4WWEPSIV3SGH74NANCNFSM4RQFXYJQ>
> .
>
>
>
|
Error is the same as here #286 |
@RomaJZ I didn't download just the CLT of 11.7, I went to the apple developer website and downloaded the Xcode 11.7 full file and added as separate xcode app in applications folder |
Same issue. Any solution so far apart from downgrading to 11.7? |
@vivekexc Even I’m looking for solution, for time being I’m using CLT 11.7 , waiting for razorpay to fix the issue. 😊 |
Hi @niyasmhdth, I am working on this issue, will post you an update as soon as I'll find the solution. |
@Nautiyalsachin Thank you 😊 |
@Nautiyalsachin Keep us updated. We are also facing same issue. |
@niyasmhdth Yes, I am facing the same issue as you after xcode 12 update. |
Hi Everyone, As I can see there is something wrong with React-Native platform as there are so many issues coming up related to XCode 12. Here are some open issues on react Native like 30000, 29846, 29984, and many more. I'll ask you guys to wait for the next React Native release or at least let them add some updates, as internally there are so many things breaking up. They are also working on the new version release v0.64.0 Discussion. Till then, I'll still be trying to fix this issue, and for any new updates, I'll keep you posted here. |
I am also facing the same issue with xcode 12 |
@Nautiyalsachin is there some way we can fix this by changing the native code? |
@Nautiyalsachin Seems like this thread is our case. |
The only workaround for now to resolve conflict with Swift class name is to rename RN module name. |
@philly25 gets an undefined error code after changing the native code. |
@weingenious72 It works for me. At least I can build app and payments works as usual. |
@philly25 its possible to explain more about ur changes |
@kathirsuresh The issue raised because of the equal interface name
Because we can't modify Razorpay SDK (swift code), all we can do is to rename React Native module interface to avoid conflict. That's what I've done. |
Yes, @philly25. This is happening internally as the framework is getting compiled again and maybe the shared library resources are getting certain conflicts. Agree with you here, if you change the class name from |
please change according to this link , the issue is fixed for me in xcode 12.1 |
Can we get this published in npm ? Seems like npm is still holding old version |
Please release a new version |
Yes, please release the new version on npm |
Hey @gauthampait, i am working on it, releasing it soon. |
Any updates? |
Hi @akhilumapathe, we have released the new plugin v2.2.2 with the changes. |
Still getting the same problem |
@eramudeep : Your react-native-razorpay package is still 2.2.1, It should be v2.2.2. Try removing and adding it again. |
I am also facing this issue on Xcode 12.3? Is there any fix to it yet? |
Have you tried updating our plugin to latest version v2.2.2? And also please update your pods by using |
@Nautiyalsachin I'm getting the same error with v2.2.2 and even with the current latest v2.2.4. This is only happening in release scheme and not debug in iOS. |
Hey @anmolpandeyy, change Build Active Architecture Only to yes for both release and debug. |
changing Build Active Architecture Only to yes will work only when we change it in build configuration of the lib. |
@nkpatnis I would suggest you to check your |
Same happening with the Sample Project in XCode 12.5. Please help me with the solution |
@vishalkhoje in my case it was the MBProgressHUD library, updating to the latest version of the MBProgressHUD library resolved the issue for me. |
Description
'RazorpayCheckout' has different definitions in different modules; first difference is defined here found 1 referenced protocol, shows an error after updating to xcode 12,
I have tried updating Razorpay pod to the latest version by using 'pod update'.
Razorpay Package Version :
2.2.0
Xcode Version (iOS) :
xCode 12
Razorpay-pod version (iOS) :
What you did:
After upgrading to xCode 12 facing this issue
What happened:
When ios was running , facing this issue
The text was updated successfully, but these errors were encountered: