RECORDING

A ride saved on the phone and not uploaded yet

A ride can exist on the phone before it exists in the cloud. Support says FoilBear saves a local pending copy before cloud upload. Reopen the app with a stable connection and stay signed in. The next launch retries the session and its route files. Do not describe that ride as lost, and do not describe it as backed up, until you know which of those the phone has finished.

What to do

Stay signed in. A signed-out phone cannot finish the retry Support describes. The sign-out guide is a different door.

Leave the app able to run long enough to send. Killing it at the first second and calling the upload failed is an unfinished try.

What not to do

Do not delete the app to clear a stuck ride. The pending copy is the copy you still have.

Do not type a route from memory into the note and call it the recorded line. If the file has not shown up, the not-recorded guide is the honest sentence.

Watch files are a second queue

A Watch ride that never reached the phone is not this pending upload. Support says to keep the Watch near the unlocked phone and not erase the Watch app while transfer is pending. The recording guide walks that case.

You can have one ride waiting on the Watch and another waiting on the phone. They are two files. Name which one you mean when you write support.

Questions

How long should the retry take?

Support does not publish a duration. It says the next launch retries when you are signed in on a stable connection. If that has failed, write support with the phone model, the app version, and what you expected.

Is the pending copy the private logbook?

It is the ride on the way into that log. Until the upload finishes, another device may not show it. Say “on this phone” if that is all you know.