Harry's GPS Suite Forum

Hi Harry,
unfortunately I'm experiencing problems in tranferring single laps or entire track days btw different devices.
An error message on the receiving device appears "Transfer failed" and the lap (see data recording pic) is only transferred partly.

On the sending device no message appeared.
I tried transferring from iPhone to iPhone as well as iPhone to iPad. In the iPhone to iPhone case I'm sure we used the identical version of laptimer (17.4.3).

Thanks in advance
Christian

There are several reasons this can happen. Either it is a transfer issue (I assume you tried multiple times?), or the data exported cannot be imported due to invalid data in the transferred file. Actually I assume the later. To fix that, please export exactly the lap you tried to send to the other device to .hlptrl and send it to me using LapTimer's Export / Mail feature. Thanks.

- Harry

Hi Harry,
file is on it's way via e-mail to you.
Yes, I tried it many times but always fails.

Best regards
Christian

RaftRacing wrote:Hi Harry,
unfortunately I'm experiencing problems in tranferring single laps or entire track days btw different devices.
An error message on the receiving device appears "Transfer failed" and the lap (see data recording pic) is only transferred partly.

On the sending device no message appeared.
I tried transferring from iPhone to iPhone as well as iPhone to iPad. In the iPhone to iPhone case I'm sure we used the identical version of laptimer (17.4.3).

Thanks in advance
Christian

The pic where you see the track layout recorded has nothing to do with what has been transfered. It shows you what Laptimer recorded while lapping, so in your case it really seems as if the recording was interrupted while lapping and the data might be corrupt and that's why it's failing (probably at least). When you try to transfer the whole day, is this corrupt lap also part of the set?

Hi Christian,

It seems the device to device communication is somewhat broken in iOS7... I have been able to reproduce the failing transfer (sending from an iOS6 device and receiving on an iOS7 device). The sender side sends 14 data packages in a row, but only 10 packages arrive on the receiver side. When LapTimer imports this incomplete file, it finds an unexpected and of file and issues the error message. All data up to package 10 is added to the database. I will try to find a workaround and search the developer forums. Worst case is we need to wait for an iOS7 update here. As a workaround, you may export your laps to a mail file and send it to an account on the other other phone currently.

On a side note (because others experience issues with device 2 device transfer will tread this thread), the iPhone5S cannot receive or send data this way at all currently. This is a known bug in iOS7.

- Harry

bulls23 wrote:

RaftRacing wrote:Hi Harry,
unfortunately I'm experiencing problems in tranferring single laps or entire track days btw different devices.
An error message on the receiving device appears "Transfer failed" and the lap (see data recording pic) is only transferred partly.

On the sending device no message appeared.
I tried transferring from iPhone to iPhone as well as iPhone to iPad. In the iPhone to iPhone case I'm sure we used the identical version of laptimer (17.4.3).

Thanks in advance
Christian

The pic where you see the track layout recorded has nothing to do with what has been transfered. It shows you what Laptimer recorded while lapping, so in your case it really seems as if the recording was interrupted while lapping and the data might be corrupt and that's why it's failing (probably at least). When you try to transfer the whole day, is this corrupt lap also part of the set?

The file Christian provided includes the full lap (a pretty fast one by the way), the above picture is indeed the incomplete transfer.

- Harry

Hi Harry,

thanks for the fast analysis and reply!

Cheers
Christian

Hi again,

Found a workaround already. The above issue is not exactly an iOS7 bug but simply a "different behavior" by the OS. I will add the workaround to LapTimer v17.5

- Harry

Thank you for your great support!

Regards
Christian