You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Locally, everything works great, runs as expected, facebook, instagram, google drive all do their own Oauth flow to connect and then i can use files from there.
on staging and production, however (i'm using npm shrinkwrap, so it shouldn't be a version issue) i instead just get a message that says "The folder is empty" on any of these integrations. local file works, url works, imagesearch works, but facebook, instagram, and google drive connect all give me this error without ever trying to authorize a connection.
(screenshot taken with just "googledrive" in fromSources and not also "facebook" and "instagram")
Note: I realize i'm not using the latest version, and i'd love to update, but at the moment it's a lot of work migrating my entire app up to react 16. If this is the entire issue, then so be it.
The text was updated successfully, but these errors were encountered:
Locally, everything works great, runs as expected, facebook, instagram, google drive all do their own Oauth flow to connect and then i can use files from there.
on staging and production, however (i'm using npm shrinkwrap, so it shouldn't be a version issue) i instead just get a message that says "The folder is empty" on any of these integrations. local file works, url works, imagesearch works, but facebook, instagram, and google drive connect all give me this error without ever trying to authorize a connection.
(screenshot taken with just "googledrive" in fromSources and not also "facebook" and "instagram")
dependency versions
"react": "^15.6.2",
"filestack-js": "^3.23.1",
"filestack-react": "^3.2.0",
Note: I realize i'm not using the latest version, and i'd love to update, but at the moment it's a lot of work migrating my entire app up to react 16. If this is the entire issue, then so be it.
The text was updated successfully, but these errors were encountered: