Still buggy in sept 2016
Updated Sept 2016...
Still buggy. Once per week after finishing a walk or run, hitting stop and stop and syncing the app sometimes will continue "adding" time and km. This is frustrating. My new routine now after an event is to hit stop, stop, sync then take screen captures and then remove the app from memory. Otherwise the app sometimes forgets it has been stopped and will continue to add to and butcher a logged event.
Updated January 2015...
This app needs HealthKit integration. Ill use Strava until this app fixes this.
-----
April 18... New issues... If you own a Pebble its pretty much impossible to stop the app on the phone from communicating to the pebble watch. First we need a switch or toggle so that its a choice for it to communicate or not. Id like MapMyTracks to work onU phone alone while another proffered app commincates to the watch. The reason I want this is that I found the communication between MapMyTracks and the pebble to be hinky/unreliable. I like to go one epic bike rides in the 100+ km range and I find that the pebble can cause the iPhone app MapMyTracks to stop recording my trek. Not cool.
----
Ive loved this app in the past and the team has incorporated past suggested in updates.
Well its new feature time again. We need a good/better method for exporting/importing my history.
In my case I have an aging iPhone 4 that has 3 years of daily treks records. I now have an iPhone 5s. Im looking for to spring weather and getting back out on my bike. However Ive noticed that despite putting my account on the new phone, it doesnt have my past history that is stored locally on the iphone4.
Yes I could go day by day on the iPhone 4 and export but that could take me days.
We need a better mass import/export function. Same issue when updating to the website. Pita doing it one by one.
So, mass import/export. Make it happen. Please. I dont want to stop using this app but without this function Im better served by other apps. Please fix.
Trichjm about Map My Tracks: ride hike pro, v4.6.1
