What the numbers mean: each number is a fixed marker placed at one specific point in the app — it identifies which screen and which server operation failed, not a unique fault type. In every case the alert is shown only after the app has already ruled out a lost connection (a dropped network shows a separate “Connection Lost” alert instead). So an “Internal Server Error N” always means the same thing: the server was reached but returned an error, or returned a response the app could not read. The number simply tells support and engineering where it happened.
General corrective steps (apply to any “Internal Server Error N”)
• Retry the action — these failures are often transient.
• Confirm the signed-in account has access to the asset and permission for the action.
• Check network and GoCodes server status; try again on a stable connection.
• If it still fails, report the exact number and the screen you were on so engineering can pinpoint the endpoint.
Error code table
Code | Message shown to user | Cause | Recommended corrective action |
1 | "Internal Server Error 1." | The server was reached but failed to return the account's custom field names / settings for the asset detail screen. | Retry. If it persists, verify the account's custom-names and settings configuration on the server. Report code 1. |
2 | "Internal Server Error 2." | Saving the edits to one asset failed on the server. | Retry the save. Confirm the entered field values are valid. Check the update endpoint / server logs. Report code 2. |
3 | "Internal Server Error 3." | A check-in or check-out started from the asset list failed on the server. | Retry. Confirm the asset and assignee are valid and the account has permission for the action. Report code 3. |
4 | "Internal Server Error 4." | Loading the allowed values (home-location / assigned-to lists) for the assign screen failed on the server. | Retry. Verify the account's allowed-values configuration. Report code 4. |
6 | "Error 6. Barcode Not Found" | The scanned or entered barcode is not associated with this account. This is expected when scanning an unknown code – not a server fault. | Confirm the barcode belongs to this GoCodes account. If it should exist, verify it in the web app. It commonly occurs when the user signs up for a personal free trial account, logs in and then scans a QR code from the company account or visa versa. |
9 | "Internal Server Error 9." | Same as code 1, but on the bulk-edit (Update All Assets) screen. | Retry. If it persists, verify the account's custom-names and settings configuration. Report code 9. |
10 | "Internal Server Error 10." | Loading the list of asset types for the bulk-edit screen failed on the server. | Retry. Report code 10 if it persists. |
11 | "Internal Server Error 11." | Same as code 4, but on the bulk-edit screen. | Retry. Verify allowed-values configuration. Report code 11. |
12 | "Internal Server Error 12." | The bulk “update all” save failed on the server. | Retry the save. Confirm the entered values are valid. Check the update endpoint / server logs. Report code 12. |
13 | "Internal server error 13." | Loading the edit-screen metadata (which fields are editable, or the asset-type list) failed on the server. This number is reused for three different loads. | Retry. Report code 13 plus the screen you were on so engineering can identify the exact call. |
14 | "Internal Server Error 14." | Same as code 4, but on the single-asset edit screen. | Retry. Verify allowed-values configuration. Report code 14. |
15 | "Internal Server Error 15." | Uploading the asset photo failed on the server. | Retry. Check the image size and connection. Verify the photo-upload endpoint. Report code 15. |
21 | "Internal Server Error 21" | A copy or swap between two assets failed, or one of the barcodes is not associated with the account. | Confirm both barcodes belong to the account and the account is allowed to copy/swap. Report code 21. |
N (dynamic) | "Internal Server Error N." (N varies) | Here N is the raw internal result code, not one of the fixed markers above: 2 = invalid request, 3 = connection lost, 4 = unknown error. | Treat like a generic failure: retry, check connection, and report the number shown. |
Notes
• The numbering is not a clean registry. It is non-sequential with gaps (there is no 5, 7, 8, or 16–20), and some numbers are reused across different operations: 13 covers three different data loads, 15 covers two photo-upload paths, and 1/9, 4/11/14, and 2/12 are the same underlying failure on different screens.