Skip to main content

GoCodes Android Native - User Error Code Reference

When an operation in the GoCodes Android app fails against the server, the user sees an “Error” dialog whose body reads “Internal Server Error N.

Written by Todd

How to use this document: match the number the user reports to the table in Section 2 to learn which operation failed and what to advise. Section 3 covers the error dialogs that do not use a number. Section 4 is a short note for developers.

Numbered error codes

Displayed as “Internal Server Error N.” (dialog title “Error”), except code 6 which is shown as its own titled dialog. Codes are defined in GlobalValues.java; the numbering has intentional gaps (9–12 and 18–20 are unused and free for future use).

Code

Meaning (operation that failed)

Recommended action

1

Fetching custom field names failed (GetCustomNames). Custom fields could not be loaded for the asset/settings screen.

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

2

Updating an asset failed (UpdateAsset). Your edits were not saved on the server.

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

3

Check-in or check-out of an asset failed (CheckInAsset / CheckOutAsset).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

4

Loading the allowed values for a field failed in a list context. Defined but currently not shown by any active screen (reserved).

Not currently user-visible. If seen, treat as a transient load failure (see code 14).

5

Asset search failed (GetAssets).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

6

Barcode not found: the scanned QR/barcode is not an active asset in your GoCodes account. Shown as “Error 6. Barcode Not Found”.

Confirm the asset exists and is active in GoCodes, and that you are signed in to the correct account. This can occur when the user signs up for a personal free trial account, logins in, and then scans a QR code from the company account or visa-versa.

7

Fetching barcodes / scanned assets failed.

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

8

Barcode-based search failed.

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

13

Fetching asset types failed (GetAssetTypes).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

14

Loading the allowed values for a field failed during asset update / check-in / check-out (GetAllowedValues).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

15

Uploading an asset picture failed (AddAssetPicture).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

16

Deleting an asset picture failed (DeleteAssetPicture).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

17

Fetching column-updatable metadata failed (GetColumnUpdatable). The app could not determine which fields are editable.

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

21

Copy or swap asset operation failed (CopyAsset / SwapAsset).

Usually transient. Retry the action. If it keeps failing, check your connection, sign out/in, and confirm you have permission for the operation. Report the code + what you were doing to GoCodes support.

General guidance for support: codes 1, 5, 7, 8, 13, 14, 17 are read operations (loading data) and are almost always transient — a retry usually clears them. Codes 2, 3, 15, 16, 21 are write operations; if they fail, confirm the change did not partially apply before retrying.

Other user-facing error dialogs & messages

These errors do not use the “Internal Server Error N” format but are still shown to users. Two of them surface their own numbers: HTTP 401 (handled silently as a re-login) and the beacon State/Reason codes (from the beacon hardware SDK).

Dialog / message (what the user sees)

Meaning & origin

Recommended action

Session expired (HTTP 401)

The server rejected the request as unauthorized. The app force-signs you out and returns to the Sign In screen. Handled in DefaultErrorListener; 401 defined in NetworkValues.

Sign in again. If it recurs immediately after signing in, your account session/permissions may have changed — contact an admin or GoCodes support.

Connection Lost — “Please check your internet connection and try again.”

Shown when a request fails with no server response at all (no network). Source: NetworkErrorDialog + network_error_message.

Check Wi-Fi / cellular data and retry. No data was sent to the server.

Login Failed — “Invalid email or password, please try again. New to GoCodes? Sign Up.”

Sign-in credentials were not accepted (AuthResponse.success = false). Source: login_failed / invalid_credentials_message.

Re-enter your email and password. Use the app’s Forgot Password / Sign Up links if needed.

Permission prompts — “Please Grant Permissions for Camera / Location / Storage…”

A required Android runtime permission was denied. Camera is needed to scan, Location to geotag, Storage to attach photos. Source: grant_*_permissions_message, enable_location_in_settings_message.

Grant the permission when prompted, or enable it in Android Settings → Apps → GoCodes → Permissions.

Barcode not associated — “This barcode is not associated with your account.”

A scanned barcode did not resolve to an asset in your account. Source: barcode_not_found (distinct from Error 6).

Verify the barcode belongs to your GoCodes account, or add/register the asset first.

Location / geocoding errors — “No GPS information…”, “Invalid latitude or longitude used”, “Sorry, no address found”, “Network problems”

The device could not obtain or resolve a location. Produced locally by FetchAddressIntentService (SUCCESS_RESULT / FAILURE_RESULT). Source: no_gps_info, invalid_lat_long_used, no_address_found, service_not_available.

Enable GPS/Location, move to an area with signal, and retry. You can still update location by scanning the asset’s QR code.

Beacon errors — “Cannot connect to beacon”, “Beacon binding failed. State code X. Reason code Y”, “Scan Failed”, “Beacons scanning unknown error”

BLE beacon connect/scan/bind/unbind failed. The State code and Reason code come from the KBeacon SDK, not GoCodes. Source: beacon_binding_failed_state_reason and related strings.

Ensure Bluetooth is on and the beacon is powered and in range, then retry. Quote the State/Reason codes to GoCodes support if the failure persists.

Did this answer your question?