Project

General

Profile

Bug #4915

Trip request is not received to the driver properly

Added by Shalu T S 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Target version:
Start date:
06/11/2025
Due date:
06/14/2025 (about 10 months late)
% Done:

0%

Estimated time:
Milestone:
Sprint 29 Tukxi Ride 2025 Apr 02 to June 27
Branch name:

Description

Trip request is not received to the driver properly, sometimes the trip request is received to the driver after a long time makes the request sometimes the request is not received.


Files

updateFcmToken (89 Bytes) updateFcmToken Anandhu P Kumar, 06/11/2025 02:30 AM

Impact Analysis

The Firebase token gets refreshed in the database when the token is refreshed on the mobile app side.


Related issues

Related to Bug #4917: Android driver : Trip request is not received to the driver properlyNewAnupama P

Actions
Related to Bug #4916: Android rider : Trip request is not received to the driver properlyResolvedAnupama P06/11/202506/11/2025

Actions
#1

Updated by Anandhu P Kumar 10 months ago

  • Due date set to 06/14/2025
  • Start date set to 06/11/2025
#2

Updated by Anandhu P Kumar 10 months ago

  • Status changed from New to In Progress
#3

Updated by Shalu T S 10 months ago

  • Related to Bug #4917: Android driver : Trip request is not received to the driver properly added
#4

Updated by Shalu T S 10 months ago

  • Related to Bug #4916: Android rider : Trip request is not received to the driver properly added
#5

Updated by Anandhu P Kumar 10 months ago

Created the api update-fcm-token to sync the Firebase token with the backend.
Need to integrate the API into the Android rider and driver app.

#6

Updated by Anandhu P Kumar 10 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF