Skip to content
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

Companion/Transloadit Facebook "App not active" #5546

Closed
2 tasks done
argotechnica opened this issue Dec 12, 2024 · 1 comment
Closed
2 tasks done

Companion/Transloadit Facebook "App not active" #5546

argotechnica opened this issue Dec 12, 2024 · 1 comment
Labels

Comments

@argotechnica
Copy link

Initial checklist

  • I understand this is a bug report and questions should be posted in the Community Forum
  • I searched issues and couldn’t find anything (or linked relevant results below)

Link to runnable example

No response

Steps to reproduce

  • Go to https://uppy.io/examples/
  • Try to connect to Facebook
  • 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."

image

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

@Murderlon
Copy link
Member

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).

@Murderlon Murderlon closed this as not planned Won't fix, can't repro, duplicate, stale Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants