File upload in progress

[Dat3473349766rv]

Hi, I'm upgrading adobe express embed from v3 to v4.

Things seem straight forward except for exporting a file. I initiated the project with a asset video url, bellow is how I did it:

ccEverywhere.editor.createWithAsset(
					{
						...docConfig,
						asset: {
							type:'video',
							dataType: 'url',
							data: dataUrl, //url to video file
						},
					},
					appConfig,
					exportOptions,
					containerConfig
				);

The video is loaded successfully into the canvas but when export it, the exporting modal keep showing File upload in progress but nothing is being upload.

 

I also notice that in browser console there are some warning log about 'Resource is missing for node'.

 

This was working nicely in v3. So any helps would really appreciate.

• Version of the app: https://cc-embed.adobe.com/sdk/v4/CCEverywhere.js

• Platform and OS version: MacOS sonoma v14.1.1, Chrome Browser v129.0.6668.90
• Expected result and actual result: Should be able to export the project.

[freked]

I can just add to the above that that even though the video is playable & editable, you don't see any circle progress indicating it's actually uploading anything. And if you open the project in a separate window, it just shows a grey placeholder instead of the video.

[Nimitha_J]

Hello,

We want to inform you that we are aware of the existing bug and that our team is currently addressing it. Rest assured, we will provide an update once the fix is implemented.

I appreciate your understanding.

Thank you, 
Nimitha

[freked]

That is fantastic news! Thanks for the update, eagerly awaiting the fix! 

[Dat3473349766rv]

That awesome! Thank you for your update. Can't wait for the next release. 🙂

[freked]

Hey again @Nimitha_J any new updates on the fix? Or just some time frame, are we days or weeks away? Thank you in advance!

[Nimitha_J]

Hello, 

We are actively working to resolve this issue and will provide an update within one to two weeks. We appreciate your patience and are also developing a temporary workaround. 

[freked]

@Nimitha_J Big thanks for the update, I've sent you some details regarding the workaround!