I assume that this problem is here to stay due to the age of the problem.
I’ve set a workaround up to circumvent the problem for now on Android with the Nextcloud app.
In the SwiftScan app
Go to Settings > Advanced Settings > Storage Location and set a new location within the Internal Storage. Example: Internal Storage/Documents/SwiftScan/
In the Nextcloud app
Go to Auto upload > Set up a custom folder and use the following settings:
Local folder: Point to the folder we set up in the SwiftScan app.
Remote folder: Choose a folder on your Nextcloud server.
Only upload on unmetered Wi-Fi: optional
Only upload when charging: optional
Also upload existing files: checked
Use subfolders: unchecked
Original files will be…: kept in the original folder
What to do if the file already exists?: Rename new version
This allows me to upload all files within SwiftScan to a Nextcloud folder.
The current SwiftScan version allows for native uploads to Nextcloud.
The workaround is no longer needed, so it would be best to disable it the auto-upload in the Nextcloud App and re-enable the upload feature in the SwiftScan app.
Unfortunately, if you were to redirect all “SwiftScan” user agents to that webdav location on the nginx side, that’s not going to work unless we find a way how to use the username submitted to the webdav service (it’s not standard web auth /$remote_user based on my tests).