This error usually means the NativeFileDocuments.NativeActionLog entity is not available in the offline database on the device. The JavaScript action is trying to write a log entry into the local SQLite DB, but that table was never created, so you get the no such table error. The Native File Documents module documentation explicitly says that NativeActionLog is used by the JS actions for logging, and that its synchronization must be configured in the native navigation profile. It also mentions that after installing/upgrading the module, there is custom setup required.
So the first things I would check are:
- In your native navigation profile, make sure NativeFileDocuments.NativeActionLog and DeviceLogFile are included in the sync configuration exactly as described by the module docs. The docs recommend setting them to “Nothing (clear data)” in the sync configuration.
- Make sure you completed the module’s manual installation steps, especially the custom logging nanoflow setup (SUB_IsLoggingEnabled / Application.SUB_NativeFileDocuments_IsLoggingEnabled). Missing that setup can also break module behavior after install or upgrade.
- If you recently installed or updated the module, do a full native rebuild and remove the app from the device/emulator before testing again. If the local offline DB was created before the entity existed, the old app can still be using an outdated schema.
- Check whether your upload nanoflow or JS action has writeToLog = true. If yes, that explains why it is trying to access NativeActionLog. As a quick test, you can temporarily turn logging off and see if the upload works.
So in short, this is usually not an upload problem itself. It is mostly an offline database/schema issue for NativeActionLog. I would start by checking the sync configuration for that entity, then rebuild the native app from scratch and test again.
If this resolves your issue, please mark it as accepted.