Fatal Exception: java.lang.NoSuchFieldError No static field activity_result_invalid_parameters of type I in class Lcom/razorpay/R$string; or its superclasses (declaration of 'com.razorpay.R$string' appears in base.apk!classes3.dex)

[Ashok-Rupeek]

Description

The below crash occur in v1.6.15 I found that this issue has been fixed in 1.6.10, but still this occur in above version. can you look into this issue refer here

Fatal Exception: java.lang.NoSuchFieldError: No static field activity_result_invalid_parameters of type I in class Lcom/razorpay/R$string; or its superclasses (declaration of 'com.razorpay.R$string' appears in base.apk!classes3.dex)
       at com.razorpay.CheckoutPresenterImpl.setOptions(CheckoutPresenterImpl.java:174)
       at com.razorpay.b__J_.onCreate(b__J_.java:106)
       at com.razorpay.BaseCheckoutOtpelfActivity.onCreate(BaseCheckoutOtpelfActivity.java:26)
       at com.razorpay.CheckoutActivity.onCreate(CheckoutActivity.java:8)
       at android.app.Activity.performCreate(Activity.java:8365)
       at android.app.Activity.performCreate(Activity.java:8343)
       at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1379)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3912)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4096)
       at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:103)
       at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2441)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:233)
       at android.os.Looper.loop(Looper.java:334)
       at android.app.ActivityThread.main(ActivityThread.java:8396)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:582)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1068)

Razorpay SDK Version :

happens in com.razorpay:checkout:1.6.15

[vivekshindhe]

@Ashok-Rupeek can you please update to the latest version which is 1.6.22 and check with that?

[dhavalpatel666]

I am using 'com.razorpay:checkout:1.6.26' in my android dependencies.

While running the payment scenario for my app, I am getting the below error go to razorpay page

java.lang.NoSuchFieldError: No static field NO_OPTIONS of type Lcom/google/android/gms/common/api/Api$ApiOptions$NoOptions; in class Lcom/google/android/gms/common/api/Api$ApiOptions; or its superclasses (declaration of 'com.google.android.gms.common.api.Api$ApiOptions' appears in /data/app/com.smaple-suaPyGsU26tVlh7gKARYpQ==/base.apk!classes2.dex) at com.google.android.gms.auth.api.phone.SmsRetrieverClient.(com.google.android.gms:play-services-auth-api-phone@@17.5.1:1) at com.google.android.gms.internal.auth-api-phone.zzab.(com.google.android.gms:play-services-auth-api-phone@@17.5.1:1) at com.google.android.gms.auth.api.phone.SmsRetriever.getClient(com.google.android.gms:play-services-auth-api-phone@@17.5.1:1) at com.razorpay.CheckoutPresenterImpl.onLoad(CheckoutPresenterImpl.java:874) at com.razorpay.J$0.secure(CheckoutBridge.java:27) at com.razorpay.CheckoutPresenterImpl.executeWebViewCallback(CheckoutPresenterImpl.java:1370) at com.razorpay.CheckoutPresenterImpl.access$700(CheckoutPresenterImpl.java:55) at com.razorpay.b$f.run(CheckoutPresenterImpl.java:1355) at android.os.Handler.handleCallback(Handler.java:873) at android.os.Handler.dispatchMessage(Handler.java:99) at android.os.Looper.loop(Looper.java:201) at android.app.ActivityThread.main(ActivityThread.java:6810) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:873)

[vivekshindhe]

@dhavalpatel666 This isn't reproducible at the moment for me. Is this happening in debug / release build? If the release build, have you added proguard rules there?