-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Unable to upload caption to a video #871
Comments
can you please provide the file name and your curl call. You may obfuscate data you don't want to be publicly visible, but please in a way that don't changes important information ;) |
Hi, fileName is 'Test.en_US.srt' curl is:
Thanks! |
Hi, I just wrote a small integration test and tried to add a subtitle to an video. My code looks like the InputStream is = getClass().getResourceAsStream("/binary/jellies.srt");
byte[] subtitleAsBytes = getBytesFromInputStream(is);
GraphResponse result = client.publish("<video_id>/captions", GraphResponse.class,
BinaryAttachment.with("captions_file","jellies.en_US.srt",subtitleAsBytes)); This worked without a problem. The only change between your code and mine is the content type. I did not provide one. Can you please check your |
The same is without the content type... I also checked bytes and the data is correct. Not sure what to do next since I tried different combinations of data... I even tried with delay between video upload and caption upload... Thanks! |
Okay. I used an page access token with only two permissions |
I'm using app with more permissions, but that shouldn't be a problem.... |
Hi guys,
I'm having issue with uploading caption to a video. GraphResponse is successful, but caption is not published.
I'm adding file as:
BinaryAttachment.with("captions_file", fileName, bytes, MediaType.APPLICATION_OCTET_STREAM_TYPE.toString());
If I try CURL from command line (direct call to graph api) caption is published.
Can you please help?
Note: I'm using version 1.44.0, switching to a 2.3.0 doesn't solves the issue.
Thanks!
The text was updated successfully, but these errors were encountered: