Bug #3562: Android Rider :- Node API Integration
Added by Anupama P about 1 year ago. Updated 10 months ago.
0%
Impact Analysis
Search pickup location
Search dropoff location
Confirm pickup
Set location on map
Android Rider:- fetchAPIDetails Node API Integration in SearchlocationActivity failed
Issue:
Upon the first login, while searching for 'pickup' and 'Where To'location suggestions do not appear; however, after the rider app is closed and reopened, the suggestions are visible. failed
Issue:
On first login, pickup and drop location suggestions do not appear while searching. However, after closing and reopening the app, suggestions work as expected.
Root Cause:
The issue was due to GOOGLE_SERVER_ANDROID_PASSENGER_APP_KEY being null or missing during the first login session.
In the updated Node API implementation, this key is now meant to be fetched and stored only from the generalConfig API.
However, in the older implementation, it was also redundantly fetched from:
getDetail API
verifyOtp API
The old code for storing this key from multiple sources was not removed, and since getDetail and verifyOtp responses no longer include this key, they were overwriting the correct key from generalConfig with an empty/null value.
Fix Implemented:
Removed the redundant key storage logic from getDetail and verifyOtp API response handling.
Now, GOOGLE_SERVER_ANDROID_PASSENGER_APP_KEY is fetched and stored only once from generalConfig, as per the latest API structure.
This ensures the correct key is consistently available for location suggestions immediately upon login.