Passing a video asset into the quick actions window

[karl_6591]

Hi,

I'm implementing the Adobe Express SDK into our app, I'm about 90% of the way there but one thing I've been attempting to do is load a video into the Video quick actions simlar to the way you can with images into the image quick actions.

I've tried a few ways and the closest I've got is adding a blob into docConfig

docConfig.asset = {
  data: video,
  dataType: 'blob',
  type: 'video'
}

When I do this, the video opens in the quick action window and I thought I'd cracked it but then an Uploading Media spinner carries on spinning and eventually the video vanishes stating that the video failed to upload.

I'm assuming it's trying to further upload the video into assets or something like that?

I'm now starting to question if it's even possible as I realise there are no examples of loading a video into quick actions even in the Git examples and I can't find any discussion about it which I find strange but I thought I'd ask before abandoning all hope 🙂 

 Is this possible or do I need to require the user to open the quick action first and then upload the video directly into the window?

[Barranca]

Hi there,

I've been able to replicate this behavior. We do have a tracked bug related to video uploads, I believe this is linked to it. Thank you very much for reporting. I'll update it and report back when I have news to share.

[karl_6591]

Hi, thanks for the quick response and the info. I'll focus on some other bits while I wait for an update to this one 🙂

[karl_6591]

Hi, just wondering if this video issue was any closer to being resolved?, I really want to get the app review process started but with this feature not working I can't really prove that whole process works in our app.

[Barranca]

It's been prioritized but not yet solved.

[karl_6591]

Hi, is there any update on this issue please?

[freked]

Hey, @karl_6591 I think this is probably related to the same issue my team reported back in October https://community.adobe.com/t5/adobe-express-embed-sdk-bugs/file-upload-in-progress/idi-p/14908523
Last I heard two weeks ago was that it's still ongoing but got no further ETA.

[Barranca]

I'm testing this, and I've got mixed results (some things work indeed, some others don't). I'm waiting for an answer, and then I'll post some more here. Thanks for your patience!

[karl_6591]

Thanks @Barranca . May I ask what you have tried that works? It would be good if I have some way of testing whilst waiting for the fix. I'm testing with mp4's and .mov but I can never get past that failure popping up.

Not sure if this helps or you probably already are aware but it seems to be when it's making a call here that causes the failure:
https://cclight-transient-user.adobe.io/assets/upload_component?storage=CSS&asset_id=d6daab02-57bc-4...

It gets a response: 415 Unsupported Media Type. It retries a few times and then throws the error message up.

[karl_6591]

Hi @freked, yes, it does look like the same issue, I did stumble accross yours after it was mentioned there was an bug already reported and wondered if that was the one.

Fingers crossed it gets fixed soon, I'm in a bit of a bind because I only just started integrating after v4  came out so I have no app approved yet, since they aren't allowing under v4 to be accepted I can't really get any furher as I have a broken workflow.

[freked]

@karl_6591 Yes, we where able to resolve the issue for loading the full editor with help from @Barranca on friday https://community.adobe.com/t5/adobe-express-embed-sdk-bugs/full-editor-throw-error-when-createwitha...

But we are facing new issues like you when now trying to make the same implemenation using blob for the quick actions also. So I'm also eager to hear what works and not 🙂

[karl_6591]

Hi @freked thanks for that tip, that got my full editor working. 

Also regarding this issue with the quick actions, I randomly tested the same video file again yesterday without making any changes to the code and it just worked, I've not had an issue since with any other videos. Has there been a fix pushed out @Barranca ?