Problem: logged in driver side after a period of time was kicked offline
Troubleshooting: After the investigation, is uploaded the driver call record causes the service side returns the token invalidation, uploads the call record the driver number and the current driver log on the driver number does not match.
Debugging found that the list of call records stored in the database corresponds to a number of drivers (the phone number and the driver number of the driver will be recorded on each call to the database) for several reasons:
1, the driver switch over the environment, test environment and online environment, but the general test environment and the online environment of the driver number is inconsistent, and all through the telephone, because it is the same database, so stored up the call record has a number of drivers.
2, the driver has changed the driver's work number
WORKAROUND: Switch the environment, clear the local data within the code, or manually erase the data each time you switch.
Because the online driver has only one environment and cannot switch the environment, there is no such problem.
Database storage data leads to kicked off the downline problem