-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors during init doesn't throw and event for the callback #276
Comments
I'm echoing this issue. I've placed " The "hitting startUpload" log hits, and the payload looks 100% correct. The "hitting inside event" never fires. No console errors. No signs of anything being requested in the Network tab when viewing the app in dev tools. Worth noting:
So it appears that the issue is occurring due to using a...correct filePath format? |
One note I forgot to include: my project is a Capacitor project (v.5.5.0). I'm wondering if there's a compatibility issue here..... |
I ran an
I'm not super-duper positive that this is the cause of our issue, but right now it's the only lead I've got. Despite the |
Hello @TOMassey, The warning you have provided in not the problem. This is a Node version update in package.json of the library. As for the callback error you are encountering, we have not tested on Capacitor yet. We will not work on this soon but it is in our roadmap. For now, a pull request is most welcome. |
If there is an error during init, there is no event thrown so the error can't be caught in the callback.
There is an error accessing the file defined in the payload object, resulting in an error - but there is no way to catch the error so it can be handled.
Even worse is there is no way to purge the upload queue to remove this problem upload, so no new uploads work without uninstalling and reinstalling the app (opened a separate issue for that)
The text was updated successfully, but these errors were encountered: