fbsamples / fbsamples/reels_publishing_apis
REELS API Copyright Check Always Returns Error
- Dominant language
- JavaScript
- Stars
- 76
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
[From the Meta for Developers Community Forum:](https://developers.facebook.com/community/threads/365125712916290/)
I've been running into some difficulties lately with uploading videos for both Reels and Stories on Facebook. Whenever I try to upload, the process seems to hit a snag, and I can't seem to get my content to go live.
Looking forward to hearing from you all and hopefully finding a solution together! Thanks in advance for your help."
Steps to Replicate
After Uploading Videos to the following Graph APIs https://graph.facebook.com/v19.0/page_id/video_stories https://graph.facebook.com/v19.0/page_id/video_reels
Checking the status of the Videos using this API https://graph.facebook.com/v19.0/video_id?fields=status
Response : { "status": { "video_status": "processing", "processing_progress": 0, "uploading_phase": { "status": "complete", "bytes_transferred": 151626 }, "processing_phase": { "status": "not_started" }, "publishing_phase": { "status": "not_started" }, "copyright_check_status": { "status": "error" } }, "id": "*****" }
-------------------------------------------
[It looks like this is happening to quite a few people when trying to upload a Reel,](https://developers.facebook.com/community/search?text=reels%20copyright%20error) even when uploading the sample video used in this repo. Additionally, I'm not seeing any error handling for copyright checks when looking at the Facebook Reel Posting here. I notice this repo uses 14.0 - is this a known issue with 19.0?
Contributor guide
Research direction
Start by reproducing the upload and status-check requests against the v19.0 video_stories and video_reels endpoints using the sample video, then compare them with the repository's v14-based Facebook Reel Posting flow. Inspect how the sample handles the returned copyright_check_status error; done means identifying whether a repository change is possible or documenting an external API issue and its workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100