Project

General

Profile

Bug #3663

Bug #3562: Android Rider :- Node API Integration

Android Rider:- loadAvailableCab Node API Integration

Added by Anupama P over 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
05/29/2025
Due date:
05/29/2025 (about 10 months late)
% Done:

80%

Estimated time:
Milestone:
Sprint 27 Tukxi Ride 2025 Feb 03 to Feb 28
Branch name:
sprint-27_nithun_3663

Impact Analysis

Listing the vehicle on the map of the home screen and showing the vehicles in the request pop-up is based on this api.

#1

Updated by Anupama P over 1 year ago

  • Due date set to 01/02/2025
  • Status changed from New to In Progress
  • Start date changed from 11/11/2024 to 11/29/2024
#2

Updated by Anupama P over 1 year ago

  • Branch name set to sprint-24_nithun_3564
#3

Updated by Anupama P over 1 year ago

  • Status changed from In Progress to On Hold
#4

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
#5

Updated by Anupama P about 1 year ago

  • Due date changed from 01/02/2025 to 02/20/2025
  • Status changed from On Hold to In Progress
  • Start date changed from 11/29/2024 to 02/12/2025
#6

Updated by Anupama P about 1 year ago

  • Assignee changed from Anupama P to Sreedevi K S
  • % Done changed from 0 to 80
#7

Updated by Anupama P about 1 year ago

  • Assignee changed from Sreedevi K S to Nithun C
#8

Updated by Anupama P about 1 year ago

  • Due date changed from 02/20/2025 to 02/24/2025
#9

Updated by Anupama P about 1 year ago

  • Due date changed from 02/24/2025 to 02/25/2025
#10

Updated by Nithun C about 1 year ago

  • Branch name changed from sprint-24_nithun_3564 to sprint-27_nithun_3663
#11

Updated by Anupama P about 1 year ago

  • Due date changed from 02/25/2025 to 02/26/2025
#13

Updated by Nithun C about 1 year ago

  • Status changed from In Progress to Resolved
#14

Updated by Anupama P about 1 year ago

  • Status changed from Resolved to Reopened
  • Assignee changed from Nithun C to Sreedevi K S
#15

Updated by Sreedevi K S about 1 year ago

  • Status changed from Reopened to In Progress
#16

Updated by Sreedevi K S about 1 year ago

  • Status changed from In Progress to Resolved

Response Changed : LoadAvailableCabResponse

#17

Updated by Anupama P 10 months ago

  • Subject changed from loadAvailableCab Node API Integration to Android Rider:- loadAvailableCab Node API Integration
  • Status changed from Resolved to QA Ready
#18

Updated by Shalu T S 10 months ago

  • Due date changed from 02/26/2025 to 05/29/2025
  • Start date changed from 02/12/2025 to 05/29/2025
#19

Updated by Firosha Fathima 10 months ago

  • Status changed from QA Ready to QA In Progress
#20

Updated by Firosha Fathima 10 months ago

  • Status changed from QA In Progress to QA Ready
#21

Updated by Firosha Fathima 10 months ago

This bug is on hold as the backend bug 3385 is reopened.

#22

Updated by Anandhu P Kumar 10 months ago

  • Impact Analysis updated (diff)
#23

Updated by Anandhu P Kumar 10 months ago

2,Vehicle type:(select vehicle)
a)There is a space in listing the vehicle type failed.

#24

Updated by Shalu T S 10 months ago

  • Status changed from QA Ready to Reopened
#25

Updated by Anandhu P Kumar 10 months ago

2, Time estimation displayed is wrong failed

#26

Updated by Anandhu P Kumar 10 months ago

Note :A trip from smartcity to alakapuri takes 15 mins as per google maps but in app it shows as 2 mins

#27

Updated by Sreedevi K S 10 months ago

  • Status changed from Reopened to In Progress
#28

Updated by Sreedevi K S 10 months ago

Issue Reported:
Unwanted space is appearing in the vehicle type selection UI, especially when listing more than two vehicle types.

Root Cause Identified:
The UI was wrongly restricted to displaying a maximum of 2 vehicle types to avoid layout issues.
Attempting to display more than 2 vehicle types resulted in layout misalignment and blank space.
An unused FrameLayout with ID pickupChargePermissionArea ad its implementation was still present in the layout, contributing to unnecessary spacing.
The bottom sheet layout height was not dynamically adapting to the number of vehicle types, especially in relation to the Promocode section.

Fixes Implemented:
Removed Unused Layout Element:

Deleted FrameLayout with ID pickupChargePermissionArea from layout and removed associated logic from CabSelectionFragment.
Vehicle Type RecyclerView:

Handled visibility and dynamic positioning of the vehicle type RecyclerView across the entire UI.
Ensured consistent layout behavior irrespective of the number of available vehicle types.
Bottom Sheet Height Adjustment:

Note :A trip from smartcity to alakapuri takes 15 mins as per google maps but in app it shows as 2 mins : This issue will b handled in driver ride request ui : #3928

#29

Updated by Sreedevi K S 10 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF