uber / uber/rides-android-sdk

v1.2/requests/current gives 404 error code only for India location

Open
#182 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
293
Forks
132
PR merge metrics
No merged PRs in 30d

Description

Github issues are for bug reports. If this is a question around usage or understanding please use
Stack Overflow. https://stackoverflow.com/questions/tagged/uber-api

Library version: 0.9.1

Repro steps, stacktrace, screenshots:
We have integrated uber_rides sdk v0.9.1 in android application which has all_trips scope on uber developer dashboard.
After SSO with Uber, android application tries to fetch information about user's current ride. Currently our app hits https://api.uber.com/v1.2/requests/current endpoint and it gives correct response for USA location. But for India location, it gives - 'Response{protocol=h2, code=404, message=, url=https://api.uber.com/v1.2/requests/current}' response which indicates - "User is not currently on a trip".

To debug this issue further, we tried Uber sandbox apis, https://sandbox-api.uber.com/v1.2/requests/current, which gives correct response even for India location.

Note - We have observed same behavior for v1/requests/current api as well. We are referring to https://developer.uber.com/docs/riders/references/api/v1.2/requests-current-get for api documentation.

Can you please help us to resolve this error asap because of this issue, all India users are not able to use one of the major feature of our application.

Expected Behavior:
/v1.2/requests/current should give response as per https://developer.uber.com/docs/riders/references/api/v1.2/requests-current-get for all regions/countries.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the documented /v1.2/requests/current request in the Android integration for India and the USA, then compare production with sandbox responses and the corresponding /v1 endpoint. Review the linked API reference and verify whether the SDK or the service produces the 404; done means the production endpoint returns the documented response for India or the regional limitation is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
api, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.