Troubleshooting
Check file.max_chunked_file_size, file.chunk_size, and the selected disk's storage quota. HTTP 413 means the web server rejected a request before Sanchaya could process it. The request includes multipart overhead, so keep file.chunk_size below the PHP and web-server request-body limits (for example, use a 1 MB chunk with a 2 MB limit). On multiple app servers, make sure each request can access the same storage/app/sanchaya-chunks directory. If you replaced the controller, verify that it returns JSON with an increasing offset value.
Confirm that the upload disk matches the folder's disk. For a directory-scoped picker, the destination folder must also be inside that directory. Chunked uploads to folders created at the standalone manager root are supported from v1.1.1.
SanchayaPicker::directory() is relative to storage.base_directory. Confirm that the stored file paths are inside that namespace and that the picker is using the same disk as the files.
Do not submit the standard Upload action while Livewire is still transferring the selected file. The action is disabled during the transfer and becomes available when progress reaches 100%. If the issue persists, check the browser console, temporary upload configuration, PHP upload limits, and whether the temporary file has expired.
Filament v5 package views should render Heroicons through Filament's wrapper, for example <x-filament::icon icon="heroicon-m-chevron-up-down" />. If a published or customized view still uses a direct x-heroicon-* component, update it to the wrapper syntax.
If layouts appear unstyled or colors are missing, ensure you have a custom theme configured. Because Filament uses Tailwind CSS v4, you must add the package views directory to your custom theme's main CSS file using the @source directive: @source "../../../../vendor/dp0/filament-sanchaya/resources/views"; and rebuild your assets (npm run build).
The active Gate policy is returning false. Debug with Gate::inspect() or configure your policy in config/filament-sanchaya.php.
Confirm your disk is defined in config/filesystems.php and listed in allowed_disks (or leave allowed_disks => null to allow all configured disks).