Version 3.0.7 still has problems
 

Hey guys, it looks like the 3.0.7 version still has some problems. I upgraded yesterday, and just launched the app and migrated my data. Now, on the main screen (vehicle details), the city/highway % shows 50/50, even though the individual fueling logs show the correct ratios. Looks like the calculation for the main page display needs to be fixed.

Also, when I click on the "New feedback from Fuelly Support..." banner, the app crashes. Also, when I go through the hamburger menu to give feedback, the app crashes.

After the update and data sync both cars are showing +100xxxk km for total mileage and completely out of whack AVG/LAST/BEST tallies. Logging into the web from my computer they both show the proper information tracked thus far.

An update to GasTracker with fixes for all mentioned above has been submitted to Apple for review (as of noon yesterday) so hopefully it should be rolling out soon.

I installed the new 3.0.8 version, and closed all apps, and rebooted the phone - looks like this version has all the same bugs (city/highway pie chart shows 50/50, clicking the feedback banner crashes the app, and clicking Feedback from the menu crashes the app) as 3.0.7. Keep trying, guys.

iOS version is 9.3.1.

This is strange. I think this is the first report I've heard of 3.0.8 NOT fixing the issues.
We may need to reach out to you privately and send another build with more log reporting for us to research what's happening on your device.
I'll get back to you.

I'm seeing some problems too since updating to version 3.0.9
When entering a new fuel-up, it was correctly showing the previous odometer readings, but once I hit save, it showed that I had done 0km. When I hit edit again, it was now showing the previous odometer readings as the same as the new odometer reading - thus the 0km. I couldn't edit the previous reading, so I deleted the entry and started again. It did the exact same thing again - showing the details correctly unit I hit save and then messing them up. After the same result on a third go, I made the entry via the website, and now it is showing correctly.
Also, after making an edit to a service note, although it shows correctly on the website, on my phone it has combined this enter with a fuel-up from the day before. It I hit edit, all the details are showing correctly, but in the log list, it is showing the spanner logo for a service with the details from the previous day's fuel-up alongside it.
It is all saving okay on the website, so nothing is being lost, but the iPhone app is a bit of a mess.

Have you updated to the latest version? Are you still experiencing issues? If you can confirm all your data is synced properly to Fuelly.com, it should be safe to just delete and fresh install GasTracker. Let me know if the problems persist.

Thanks for the feedback. We'll look into this.
Can you provide me some screenshots and an example of what you were entering vs what it's displaying in the app?

I haven't been able to replicate the second issue, but the first one is still consistent. Here is the sequence of screenshots at each step.

In this first picture, I am entering the data for the first time. The current and previous odometer readings are showing correctly.
https://laughingbird.net/html/IMG_2315.jpg
Then I hit "save", and the "latest fuel efficiency" pop-up suddenly shows that no distance has been covered.
https://laughingbird.net/html/IMG_2316.jpg
I close that, and the entry content now similarly shows no distance.
https://laughingbird.net/html/IMG_2317.jpg
If I hit "edit" to go back into it, it is now showing a "last odometer" reading that is actually the current odometer reading that I have just entered.
https://laughingbird.net/html/IMG_2318.jpg
If I input the entry via the website instead, it works correctly.
I am running the latest version of Gas Tracker on an iPhone 5 running the latest version of iOS.

I am currently experiencing the same problem with my fill up's and it's happening more often. It's not using my last odometer readings from previous ones, but instead, it puts my most recent odometer reading into previous logs and can't calculate it...