razorpay / razorpay/razorpay-java
order not response
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 74
- Forks
- 83
- PR merge metrics
- No merged PRs in 30d
Description
ApiClient Class line no = 124 throw new RazorpayException("Unable to parse response because of " + e.getMessage());
java.lang.RuntimeException: com.example.razorpaytest.razorpay.RazorpayException: Unable to parse response because of com.razorpay.Order cannot be cast to com.example.razorpaytest.razorpay.Entity
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:578)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
Caused by: com.example.razorpaytest.razorpay.RazorpayException: Unable to parse response because of com.razorpay.Order cannot be cast to com.example.razorpaytest.razorpay.Entity
at com.example.razorpaytest.razorpay.ApiClient.parseResponse(ApiClient.java:123)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ApiClient.parseResponse around ApiClient.java line 123, using the stack trace and the reported Order-to-Entity cast failure as the entry point. Trace how an order response is parsed and identify what completion means: an order response should be handled without the reported RazorpayException. The payload names no test file, so locate the relevant existing response-parsing tests before changing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100