Bug #3661
Bug #3562: Android Rider :- Node API Integration
Android Rider:- SendRequestToDriversV2 Node API Integration
100%
Impact Analysis
Sent trip request to drivers
Trip request popup in driver app
Updated by xavier joseph over 1 year ago
- Due date set to 11/20/2024
- Start date changed from 11/11/2024 to 11/20/2024
Test permission in projects.dooth
Updated by Anupama P over 1 year ago
- Due date deleted (
11/20/2024) - Status changed from In Progress to On Hold
- Start date deleted (
11/20/2024)
Updated by Anupama P about 1 year ago
- Target version changed from 1.0.7 to 1.0.9
- Milestone deleted (
Sprint 25 Tukxi Ride 2024 Nov 01 to Nov 30) - Milestone set to Sprint 27 Tukxi Ride 2025 Feb 03 to Feb 28
Updated by Sreedevi K S about 1 year ago
- % Done changed from 0 to 70
- Estimated time set to 15.00 h
- Impact Analysis updated (diff)
Ongoing word : Handling the Response of SendRquestToDrivers
Updated by Sreedevi K S about 1 year ago
Ongoing work : Handling the Response of SendRquestToDrivers
Updated by Sreedevi K S about 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
Updated by Firosha Fathima 10 months ago
- Status changed from QA In Progress to QA Passed
Android Rider:- SendRequestToDriversV2 Node API Integration
1,when the trip request is sent from rider to driver, driver receives the request and also he can accept the trip passed
ER: Request should received in the driver end
AR: As expected
Failed cases:
1.7075808590 for this number while requesting the trip,request is not received to the multiple drivers failed
2,As soon as the rider requests a trip, the driver receives the same trip request , prior to the rider's 'Retry' failed
3,when the pick up point is marker (pinned) with the pointer it is not correctly addressed in the pick up point failed
for example:if the pointer is in mariapps, smartcity it is displayed as kakkanad,Kochi
Updated by Sreedevi K S 10 months ago
- Status changed from Reopened to In Progress
Issue Found : Change in the request format of pickUpDistanceDuration to JSONObject : Resolved
Updated by Sreedevi K S 10 months ago
- Status changed from In Progress to Resolved
1. Trip Request Not Received by Multiple Drivers
Issue: For the number 7075808590, trip requests are not received by multiple drivers.
Status: Works for multiple drivers
Notes: Investigate server-side broadcasting or driver filter logic.
2. Driver Receiving Trip Request Before Rider Hits 'Retry'
Issue: As soon as a rider requests a trip, the driver receives the trip request prematurely, even before the rider retries.
Expected: The trip request should only be sent to drivers after the rider confirms or retries.
Status: Failed
Action Taken: Discussed with TL. Needs backend investigation and handling.
3. Incorrect Address Shown When User Pins Pickup Location
Issue: When the user pins a location manually, the displayed pickup address is incorrect.
Example: If the user pins “Mariapps, SmartCity”, the address shows as “Kakkanad, Kochi”.
Cause:
Currently using Google Maps Directions API to fetch location name.
Directions API returns postal-based location names (e.g., “2657/288, Kakkanad, Kochi”) and truncates postal code.
This causes the app to miss landmarks or business names like “Zudio, SmartCity, TransAsia”.
Suggestion:
Use Google Places API instead of (or in addition to) Directions API for more accurate, landmark-based names.
Status: Hold
Remarks: Discussed with Anupama; currently not feasible. Awaiting further instruction from TL.
4. Request Format Change – pickUpDistanceDuration
Issue: The pickUpDistanceDuration was expected as a JSONObject instead of its previous format.
Status: Resolved