-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Code 401 Unauthorized when trying to upload from GoogleDrive/Dropbox #1356
Labels
Companion
The auth server (for Instagram, GDrive, etc) and upload proxy (for S3)
Comments
arturi
added
the
Companion
The auth server (for Instagram, GDrive, etc) and upload proxy (for S3)
label
Mar 19, 2019
Is this related to #1298? |
@arturi Are there any updates you can share on this item? |
Hi! Can you please try with the latest version of Uppy and Companion? |
I can confirm that I was facing the same issue with @uppy/core 0.29 and with latest version , this is not the case. |
Please re-open if you are still experiencing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm working on setting companion in a express app and a AWS lambda function and for the client I'm using (only for testing purposes) the React Example provided in the repository. I started with the serverless example and after some work I was able to upload local files to S3, and authenticate with Dropbox and GoogleDrive.
Unfortunately, after selecting a file (GoogleDrive or Dropbox) to upload, I keep getting a 401 unauthorized code. I thought it could be related to #1303 but my error has nothing to do with S3. Indeed, as I said above, I'm able to upload files using companion and AWS lambda. As I saw in this comment it might be related to an error with uppy-auth-token. Is there something I'm missing or any extra configuration I need to set in order to upload files successfully?
I'm attaching a Gif showing the flow and the error I'm getting in the console. Thanks in advance for any help.
The text was updated successfully, but these errors were encountered: