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

Streamable Upload Errors #1754

Closed
Hakaan256 opened this issue Jul 31, 2016 · 4 comments
Closed

Streamable Upload Errors #1754

Hakaan256 opened this issue Jul 31, 2016 · 4 comments
Labels

Comments

@Hakaan256
Copy link

Hakaan256 commented Jul 31, 2016

Screen recordings uploaded to Streamable come up with this error:

StreamableError.txt

I'm logged in to Streamable (it didn't work anonymously either) and the video actually uploads to my account, but the URL fails to copy to my clipboard.

@Jaex Jaex added the Bug label Jul 31, 2016
@Jaex
Copy link
Member

Jaex commented Jul 31, 2016

@lawlmart should I use nullable int or string for status? Nullable int is not good idea in API because not all programming languages support it.

@lawlmart
Copy link
Contributor

lawlmart commented Jul 31, 2016

That's looks like a bug in our api. Status should never be null, I'll check it out.

@lawlmart
Copy link
Contributor

lawlmart commented Jul 31, 2016

I'm going to hotfix our API so the file descriptor conforms to the ShareX class definition, but for the future StreamableStatusResponseVideo class definition should probably be changed to:

StreamableStatusResponseVideo
{
public string url { get; set; }
}

@lawlmart
Copy link
Contributor

lawlmart commented Aug 1, 2016

Looks like that did the trick. Everything but url in the files array is undocumented and therefore subject to change so this should probably still be fixed in ShareX in the future. I'll submit a pull once I get this windows box set up.

@Jaex Jaex closed this as completed Aug 2, 2016
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

3 participants