Tukxi Ride

I have thoroughly investigated the bug regarding the incorrect pick-up location displayed on the map. Over the past few days, I have analyzed the flow of parameters passed to the sendRequestToDrivers API, including message (CabRequestedJson), PickupLatitude, PickupLongitude, and PickupAddress. The pickUpLocation variable, which is declared globally, is assigned values based on multiple conditions, such as matching the current location, search inputs, or saved addresses like work or home. Despite extensive debugging and testing, I have been unable to reproduce the issue on the development side. The overwritten value of pickUpLocation seems to occur under rare and highly specific conditions that are difficult to replicate.

Additionally, I reviewed the push notification payload provided by the backend team from the QA reproduction case, which confirms that the correct latitude and longitude for the pick-up (Athani) and destination (Alakapuri) were passed. This suggests that the issue may not lie within the current code logic. Given the rarity of this occurrence and the lack of reproducibility, I believe this issue might require further investigation or additional context to identify external factors contributing to the behavior. Please advise on the next steps or any additional information that might help in resolving this rare scenario.

Add Logger code to the branch in Driver for testing in driver