Every code Carbura can return, what causes it, and what to do about it. A driver reading a code out loud and a developer reading a log are looking at the same thing.
The credentials did not match any account.
Qué hacer. Check the email and password and try again.
Deliberately does not say which of the two was wrong: telling someone an email exists confirms which accounts are real.
The access token is no longer valid and could not be refreshed.
Qué hacer. Sign in again.
Sign-up was attempted with an email that is already in use.
Qué hacer. Sign in instead, or reset the password.
Passwords must be at least 10 characters.
Qué hacer. Use a phrase you can remember. Length matters more than symbols.
An administrator blocked the account for abuse.
Qué hacer. Contact whoever administers your fleet.
The server has sign-up disabled; accounts are created by invitation.
Qué hacer. Ask your team leader to create your account.
The account cannot be deleted while it owns a team. The team belongs to the people in it as much as to whoever created it, and its trip history is their record too.
Qué hacer. Hand the team over to another leader, or close it, and then delete the account.
The account exists but its Carbura profile was never created, so there is nothing on file to check the request against.
Qué hacer. Open the app again. It creates the profile by itself the first time it loads. If this keeps happening, sign out and sign back in.
Kept apart from CBR-1005 on purpose. Both refuse the request, and the server is right to refuse either way, but telling somebody their account is blocked when it simply has no profile yet sends them looking for a punishment that does not exist.
No active team matches the code.
Qué hacer. Check the code with your leader. Codes are 8 characters and never contain the letter O or the digit 0.
Says the same thing for a non-existent code and an expired one, so probing cannot tell them apart.
More than 10 wrong codes in 15 minutes.
Qué hacer. Wait a few minutes before trying again.
The team has reached its member limit.
Qué hacer. Ask the leader to raise the limit or remove inactive members.
The action requires membership, and you left or were removed.
Qué hacer. Join again with the team code.
The action is restricted to leaders.
Qué hacer. Ask your leader.
Enforced by the database, not the UI. Even a modified app gets rejected.
Teams are temporary and this one passed its end date.
Qué hacer. Ask your leader to create a new one.
A person can own at most 20 active teams.
Qué hacer. Archive a team you no longer use.
Only one trip can be live at a time.
Qué hacer. Finish or cancel the current trip first.
Completed and cancelled trips cannot be reopened.
Qué hacer. Start a new trip.
Reopening an old trip would allow backdating false positions onto it.
The trip was dispatched by a team leader.
Qué hacer. Ask your leader, or leave the team if you should not be under dispatch.
No road on the way allows the declared height, weight or cargo.
Qué hacer. Check the vehicle's height and weight are correct, or pick a different destination.
A legitimate and frequent answer for trucks, not a malfunction.
The route falls outside the map region loaded on the server.
Qué hacer. Contact whoever administers the server: the map region needs to be extended.
The team leader assigned a new destination while driving.
Qué hacer. Follow the new directions when it is safe to do so.
Not a failure. It is announced loudly on purpose: finding out late is worse than the change itself.
The route has not been calculated.
Qué hacer. Calculate the route before starting to navigate.
Location permission was denied.
Qué hacer. Grant location access in system settings. Without it there is no navigation.
Background location permission was not granted.
Qué hacer. Allow location "always" so directions continue with the phone in your pocket.
System location services are disabled.
Qué hacer. Turn on location in system settings.
Your position is outside the route's tolerance corridor.
Qué hacer. Return to the route, or recalculate if the road is blocked.
Your leader is notified. Nothing is blocked: blocking a driver would be dangerous.
The operating system reports the position comes from a mocking app.
Qué hacer. Turn off the mock location app. Your leader has been notified.
More than 180 positions were sent in one minute.
Qué hacer. Usually a bug in the app. Restart it.
The device clock differs from the server by more than five minutes.
Qué hacer. Set the date and time automatically in system settings.
Positions are still recorded, but flagged for review.
The search server did not answer.
Qué hacer. Try again, or pick from your saved places.
There is no connection, so previously saved results are being used.
Qué hacer. Nothing. Addresses rarely move, but results may be out of date.
The search returned no results.
Qué hacer. Try fewer words, or the street and city separately.
Home and Base can only exist once each.
Qué hacer. Rename the existing one, or save this as a custom place.
The device could not reach the server.
Qué hacer. Check your signal. Navigation continues with the route already downloaded.
The request exceeded its time limit.
Qué hacer. Try again in a moment.
The server returned an unexpected error.
Qué hacer. Try again. If it keeps happening, report this code.
Valhalla is unreachable or still building its map.
Qué hacer. Try again shortly. After a fresh deploy, building the map takes a while.
The server sent data this version does not understand.
Qué hacer. Update Carbura.
Required server addresses were not provided at build time.
Qué hacer. Rebuild with the required --dart-define values. See the README.
The app asked for something the server does not serve. Either the app is older than the server, or it is pointed at the wrong address.
Qué hacer. Update the app. If it is already up to date, check the server address it was built with.
Answered at the front door rather than by the service behind it, so a request for an address that does not exist never costs any work. Anything that is not a real endpoint gets this, which also means a scan of common paths learns nothing from the difference between them.
Routing will treat it as an ordinary vehicle.
Qué hacer. Add the height and weight before navigating. Without them the route may pass under a bridge your truck does not clear.
The single most consequential missing field in the whole app.
A value is far outside what a real vehicle measures.
Qué hacer. Check the units. Height goes in centimeters, weight in kilograms.
No default vehicle is registered for this account.
Qué hacer. Add your vehicle so routes account for its size.
The database rejected the operation.
Qué hacer. If you believe this is wrong, report this code.
The rate limit for this action was exceeded.
Qué hacer. Wait a moment and try again.
The distance between two positions implies a speed no vehicle reaches.
Qué hacer. Usually a GPS glitch. If it repeats, your leader will be notified.
A server-side key was found in the app configuration.
Qué hacer. Rebuild with the public key. A server key inside an app exposes the entire database.
The app refuses to start. This is intentional.
An error occurred that the app does not recognize.
Qué hacer. Try again. If it keeps happening, report this code with what you were doing.
The server response did not match the expected shape.
Qué hacer. Usually means the app and the server are different versions. Update the app.