Open rodrigojmlourenco opened 8 years ago
This BUG was addressed by first analysing the isTracking
state variable, and additionally protected it in a synchronized area.
This bug keeps happening. A new attempt was made by avoidoing closing the databases. This should be safe according to GoogleForum
Sometimes, the tracking is not stopped as the service considers the tracking to already be stopping. This is caused by the false evaluation of the
isFinishing
variable that is protected by a synchronized area.