I’m building file upload into my app with the AWS File Uploader and am generally successful across the board, especially after some helpful guidance here on the forum. The documentation notes that the first call to the plugin will typically be a little slow due to the way Bubble instantiates server-side actions. I do see this in practice; the first photo upload is markedly slower than subsequent uploads. I want to make use of the “warm start” functionality that is outlined in the Tips section of the documentation but cannot get it to work. As far as I can tell, this should go:
-
On page load, fire the ‘Generate Pre-Signed URL’ workflow action. Provide a static file and a valid bucket name.
-
This should load the Bubble server-side modules. By the time your user is actually uploading files, the temp modules are installed and ready.
I am looking for some insight on the best practices for where to store this static, “dummy,” file. I haven’t yet succeeded in setting this warm start functionality up, and get ‘Invalid keypath / unexpected token’ in my browser console. I’m trying to pass in a file dynamically that is stored on a record.
Thank you for any suggestions!