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
Receive error, "App not active: This app is not accessible right now and the app developer is aware of the issue. You will be able to log in when the app is reactivated."
When running in my own setup, I have verified I'm using all current uppy packages.
Expected behavior
"Connect to Facebook" results in proper connection
Actual behavior
Receive error, "App not active: This app is not accessible right now and the app developer is aware of the issue. You will be able to log in when the app is reactivated."
Whether running on Uppy Examples, or in my own site using Companion/Transloadit, there doesn't appear to be anything helpful in console / network logs.
Instagram is unfortunately gone forever as they completely stopped with their APIs for regular accounts. Facebook should be possible to retain but it's a long verification process for us.
I'll disable the checkboxes for now and reenable Google Drive/Photos, since we have the picker APIs (#5443), we can request access again without going through a painstaking approval process with third-party audits and such.
In the meantime, the plugins still work if you are able to obtain an API token yourself and use that instead of ours (which is recommended anyway for your own setup).
Initial checklist
Link to runnable example
No response
Steps to reproduce
When running in my own setup, I have verified I'm using all current uppy packages.
Expected behavior
"Connect to Facebook" results in proper connection
Actual behavior
Receive error, "App not active: This app is not accessible right now and the app developer is aware of the issue. You will be able to log in when the app is reactivated."
Whether running on Uppy Examples, or in my own site using Companion/Transloadit, there doesn't appear to be anything helpful in console / network logs.
See also: #5455
The text was updated successfully, but these errors were encountered: