On December 18th we released Fleetio Go 3.4.2 to the Google Play Store. This version improved how Fleetio Go handles completing an inspection internally, but introduced an error which caused previously resolved Issues to remain cached on users' devices. The device failed to recognize when Issues were resolved elsewhere, forced the user to include previously resolved Issues via an inspection, and raised an error when submitting the inspection due to the inconsistency. Users were then stuck as there was no way to tell the app which Issues had been resolved and could be safely ignored.
Our mobile engineers worked to fix this problem and on December 28th released Fleetio Go 3.4.2.2, which did two things:
1. The app is now able to recognize when Issues are resolved elsewhere by other users.
2. Ensures that Issue resolutions and open Issues are handled appropriately when completing inspections.
We're also working to improve our automated testing suite to account for more scenarios to make critical errors on inspections easier to diagnose before they make it to the app stores. While we currently have a robust testing suite, our goal is to add as many of our users’ workflows as possible. We apologize for the inconvenience this issue caused and thank you for your patience while we worked on a resolution.