Possible Bugs I Cannot Duplicate

[Steve Punter]

Dear Bike Tracker user:

Can you please help me determine if a couple of bugs exist in your copy of the app. I've not only had these bugs reported to me, but have seen screen capture videos that clearly demonstrate the problems. However, I've been unable to duplicate these issues on my own devices.

Here's how to determine if the first of these two bugs exist for you:

1) First, start a connection to a Bluetooth speaker or headphones, though I'm not sure if this step is actually necessary, but it SEEMS to be a factor.

2) Start Bike Tracker and load a route (preferably from a TCX file, but again, this may or may not be important).

3) Press the GPS button and wait for it to get a lock.

If the problem exists on your device, you will not see the START button become active and it will look like Bike Tracker is constantly searching for GPS. However, if you now tap on the name of the currently-selected Profile on the home screen and select a profile from the list (even the one that is current selected), the START button will suddenly spring to life.

So do you have a problem with Bike Tracker not establishing a GPS connection in order to start a ride?

Now for the second possible bug:

1) Open Bike Tracker and select SETTINGS

2) From there, select PROFILES and tap on one.

3) Select SPOKEN INFORMATION and drag one of the items to a new position in the list.

4) Tap the check mark icon and in response to the popup, select SAVE & BACK.

5) Once back at the previous screen, re-select SPOKEN INFORMATION.

6) Tap the 3-dot icon in the top-right corner and select ADD.

Does your app present the "Spoken Element" screen, or does it flash numerous times and return to the Bike Tracker home screen?

I'm hoping to find out if either of these bugs is widespread, and if so, what build of Android is being run. Thanks in advance for your assistance in this matter.

[John Ellerton]

Hi Steve, 

Looks like everything is fine on my phone, a Moto G4 on Android 7.0 - sorry can't see an actual build number.

On the first bug, the Start button becomes active, as normal.

On the second bug, I get the "Spoken element" screen as normal

JohnE

[Steve Punter]

Thanks for the help, but I've finally discovered how to duplicate the problems. Apparently, they ONLY affected user with a default units-of-measure set to IMPERIAL. Once I changed my own units-of-measure to imperial, I was able to duplicate both bugs. As a result, a fix these problems has now been released in Build 33.

[John Kretschmann]

I had the first bug where the GPS would appear to not lock and the Start button would never activate.  I just installed update 33 and problem fixed!  Thanks.