Bug #3295
Call receives to the previously logged driver app, when the rider calls between the trip.
Added by Shalu T S over 1 year ago.
Updated over 1 year ago.
Milestone:
Sprint 19 Tukxi Ride 2024 May 01 to May 31
Branch name:
sprint-19_nithun_3295
Description
Call receives to the previously logged driver app, when the rider calls between the trip.
STR
1. Login to the rider app and driver app.
2. Make a trip.
3. In enroute status logout the driver app and login to another device.
4. Make a call from rider to driver.
5. Check the driver loged devices(both).
ER.
5. The call only receives to the newly loged device.
AR
5. Call received to previously loged device also.
Impact Analysis
Check the following scenarios
1. A "Session is expired" popup should appear when the app is launched after being killed, if the same user is logged in on another device.
2. A "Session is expired" popup should appear when the app is launched after being minimized, if the same user is logged in on another device.
3. A "Session is expired" popup should appear while the app is in the foreground, if the same user is logged in on another device.
4. Location updates should function as expected.
5. Call services should work properly.
6. Notifications should be delivered correctly.
- Assignee changed from Jithin Kuriakose to Nithun C
- Milestone deleted (
Backlog)
- Milestone set to Sprint 19 Tukxi Ride 2024 May 01 to May 31
- Branch name set to sprint-19_nithun_3295
- Due date set to 08/30/2024
- Start date set to 08/27/2024
- Status changed from New to In Progress
- % Done changed from 0 to 70
- Estimated time set to 72.00 h
- Status changed from In Progress to Resolved
- % Done changed from 70 to 100
- Estimated time changed from 72.00 h to 32.00 h
- Status changed from Resolved to QA Ready
- Status changed from QA Ready to Reopened
1. Call receives to the driver app, previously logged in by the driver. if he/she not respond to the session out message.
step:- Login a driver and rider >> make a trip >> make the trip in en route status >> login the same driver in another device >> call the driver from rider app.
2. Call not shows in the newly logged in driver app.
Step :- Login a driver and rider >> make a trip >> make the trip in en route status >> minimize the driver app >> login the same driver in another device >> call the driver from rider app.
3. Call interface not showing in the driver app, also the ring sound is in the driver when the call accepts by the rider.
step: Login as a rider >> make a trip >> make the trip into en route status >> login the rider in another device >> call the rider from driver.
(line 167): TCP connect failed with error 101
2024-09-11 11:38:40.998 13720-21558 webrtc_bas...factory.cc com.tukxi.driver E (line 167): TCP connect failed with error 22
2024-09-11 11:38:41.006 13720-13720 IncomingCa...enActivity com.tukxi.driver E Started with invalid callId, aborting
- Due date changed from 08/30/2024 to 09/18/2024
- Status changed from Reopened to In Progress
- Start date changed from 08/27/2024 to 09/13/2024
- % Done changed from 100 to 10
- Due date changed from 09/18/2024 to 09/20/2024
- Status changed from In Progress to Resolved
- % Done changed from 10 to 100
- Impact Analysis updated (diff)
Shalu T S wrote in #note-11:
1. Call receives to the driver app, previously logged in by the driver. if he/she not respond to the session out message.
step:- Login a driver and rider >> make a trip >> make the trip in en route status >> login the same driver in another device >> call the driver from rider app. - Resolved
2. Call not shows in the newly logged in driver app.
Step :- Login a driver and rider >> make a trip >> make the trip in en route status >> minimize the driver app >> login the same driver in another device >> call the driver from rider app. - This bug cant be reproduced
3. Call interface not showing in the driver app, also the ring sound is in the driver when the call accepts by the rider.
step: Login as a rider >> make a trip >> make the trip into en route status >> login the rider in another device >> call the rider from driver.- This bug cant be reproduced
(line 167): TCP connect failed with error 101
2024-09-11 11:38:40.998 13720-21558 webrtc_bas...factory.cc com.tukxi.driver E (line 167): TCP connect failed with error 22
2024-09-11 11:38:41.006 13720-13720 IncomingCa...enActivity com.tukxi.driver E Started with invalid callId, aborting
- Impact Analysis updated (diff)
- Status changed from Resolved to QA Ready
- Status changed from QA Ready to QA In Progress
1. Call receives to the driver app, previously logged in by the driver. if he/she not respond to the session out message. Fixed
- Status changed from QA In Progress to QA Passed
- Related to Bug #3417: Application does not get logout, even if we logged in the same account in another device. added
- Status changed from QA Passed to Reopened
1. Loading issue in the driver app, if we login the same user in another device and restart the app.
Step :- Login the driver in Asus >> Login the same driver in another device >> Kill driver app in Asus >> Open the driver app in Asus.
- Due date changed from 09/20/2024 to 09/26/2024
- Status changed from Reopened to In Progress
- Start date changed from 09/13/2024 to 09/26/2024
- Status changed from In Progress to Resolved
- Status changed from Resolved to QA Ready
- Status changed from QA Ready to Reopened
1. Loading issue in the driver app, if we login the same user in another device and restart the app. Fixed
Step :- Login the driver in Asus >> Login the same driver in another device >> Kill driver app in Asus >> Open the driver app in Asus.
- Status changed from Reopened to Resolved
- Status changed from Resolved to QA Ready
- Status changed from QA Ready to QA Passed
- Status changed from QA Passed to Closed
Also available in: Atom
PDF