Bug #3297
Call received to the rider app previously logged out.
100%
Description
Call received to the rider app previously logged out.
STR
1. Login to the rider app and driver app.
2. Make a trip.
3. In en route status logout the rider and login to another device.
4. Make a call from the driver.
5. Check the call received in the rider app, the rider previously logged in also.
ER
5. The call only expected to the newly loged in device.
AR.
5. The call logged in the previously logged in 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.
Related issues
Updated by Anupama P over 1 year ago
- Milestone deleted (
Backlog) - Milestone set to Sprint 19 Tukxi Ride 2024 May 01 to May 31
Updated by Nithun C over 1 year ago
- Due date set to 09/02/2024
- Start date set to 08/30/2024
- Estimated time set to 13.00 h
Updated by Nithun C over 1 year ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Updated by Shalu T S over 1 year ago
- Status changed from QA Ready to Reopened
1. The application is not gets logout, even if the rider loged in another device.
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.
2. The issue still exist, previously call receives to the previously logged device.
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.
Updated by Nithun C over 1 year ago
- Due date changed from 09/02/2024 to 09/24/2024
- Status changed from Reopened to In Progress
- Start date changed from 08/30/2024 to 09/23/2024
- % Done changed from 100 to 10
- Estimated time changed from 13.00 h to 6.00 h
Updated by Nithun C over 1 year ago
- Status changed from In Progress to Resolved
- Impact Analysis updated (diff)
Updated by Shalu T S over 1 year ago
- Status changed from QA Ready to Reopened
The issue still exists.
Updated by Nithun C over 1 year ago
- Due date changed from 09/24/2024 to 09/26/2024
- Status changed from Reopened to In Progress
- Start date changed from 09/23/2024 to 09/26/2024
Updated by Shalu T S over 1 year ago
- Related to Bug #3417: Application does not get logout, even if we logged in the same account in another device. added
Updated by Shalu T S over 1 year ago
- Status changed from QA Ready to Reopened
1. Call not end form the rider even if the driver end the call.
2. Call screen showing twise or blink in the previously logged in device whil call a rider.
3. Call not received to the rider in the second device he logged in.
Updated by Nithun C over 1 year ago
- Due date changed from 09/26/2024 to 10/03/2024
- Status changed from Reopened to In Progress
Updated by Nithun C over 1 year ago
- Status changed from In Progress to Resolved
1. In the Rider app, if an ongoing call doesn't end or if the ringtone keeps playing after the call has ended during an en route.This issue occurs because the Sinch service instance is not fully stopped on the device. According to the documentation, the service terminates completely only when the app is killed.
Updated by Shalu T S over 1 year ago
- Due date changed from 10/08/2024 to 10/15/2024
- Status changed from QA Ready to QA In Progress
- Start date changed from 10/01/2024 to 10/15/2024
Updated by Shalu T S over 1 year ago
- Status changed from QA In Progress to QA Passed
1. Call not end form the rider even if the driver end the call. Fixed
2. Call screen showing twise or blink in the previously logged in device while call a rider. Fixed
3. Call not received to the rider in the second device he logged in. Fixed
Updated by Shalu T S over 1 year ago
- Status changed from QA Passed to Closed
Verified in production.