getActualFileFromTempUrl error codes
When using the included custom action getActualFileFromTempUrl, which extracts the actual file (as an FFUploadedFile) from the temporary route stored in each file item, certain errors might occur during the conversion or reading process.
Every time an error occurs in this action, the onErrorAction callback is triggered. This callback receives two parameters:
errorCode(available under Callback Parameters > errorCode)fileName(available under Callback Parameters > fileName)
You can use them to create a custom error-handling flow, display messages in your preferred language, and inform the user through modals, snackbars, conditional logic, redirection, or any other UI feedback method.
If an error occurs but the onErrorAction is not triggered, it’s likely that the issue is not directly related to the File Uploader or this custom action.
For example, your storage provider may block the upload due to file size limits. Supabase, for instance, enforces a 50MB limit per file on free-tier accounts. If a file exceeds this size, the upload will silently fail without triggering an error from the component.
🧾 List of Possible Error Codes
INVALID_TEMP_URL
This error occurs when the tempUrl provided in the receivedFileInfo is null or an empty string. The action cannot proceed without a valid temporary path to the file.
WEB_FETCH_ERROR
Indicates an issue while attempting to download the file's bytes using http.get. This could be due to an invalid or expired URL, network failure, or a non-200 HTTP status response.
FILE_NOT_AVAILABLE
This means the file at the tempUrl (a local file path) either doesn't exist or cannot be accessed.
CONVERSION_ERROR
A generic error triggered if an unexpected exception occurs while converting the tempUrl to file bytes, either during HTTP download or file system reading.
FILE_BYTES_EMPTY
Triggered when, after attempting to retrieve the file bytes, the result is null or an empty byte list. This indicates the file contents could not be recovered.
Last updated