You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
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.
How are able to get the scopes ? Can you please a way .In my developer dashboard its showing no scopes and I cant find a way to request scopes . Any help on this will be appreciated .
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.
The text was updated successfully, but these errors were encountered: