INVALID_PSD_URL When loading the editor with media

[Dakota32294208qhf9]

Just recently started getting this error on attempting to load the editor with our own media on startup:

INVALID_PSD_URL: Provided asset does not have the correct Photoshop Document
Error: Provided asset does not have the correct Photoshop Document

The integration has been working fine for months. I don't see any updates in the changelog that would break this. The editor works fine when started without any media.

I am using a URL to load the media into the editor.

[Dakota32294208qhf9]

Seemed to be an intermittent issue. No longer getting this error and everything is fine.

[nhung.ng]

I also encounter this issue. Does anyone know why and how to fix it?

[freked]

We have still not found a way around this one, thus blocking us from moving over to v4. Any suggestions on how to resolve this?

[Dat30188464j9d3]

Got the same issue when upgrade to v4. Any update?

[ErinF]

The engineering team is currently working on a fix!

[ErinF]

The fix for this is now in producion, please give it a try and let us know if it's working now.

[nhung.ng]

I got this issue when tried it out. Below is how I called the 'createWithAsset()' function:

ccEverywhere.editor.createWithAsset(
       {
	     ...docConfig,
	     asset: {
		type: 'video', // Both 'video' and 'image' gave the same error
		dataType: 'url',
		data: dataUrl,
	     },
        },
	appConfig,
	exportConfig,
	containerConfig
);

[nhung.ng]

Hello @ErinF, any update from your engineering team? This issue has blocked our migration to v4.

[erinferinferinf]

Hello @ErinF, any update from your engineering team? This issue has blocked our migration to v4.

I think engineering believes they've fixed it... I'll ping them again.

[erinferinferinf]

They've replied: 

DataType: "url" is not supported for both images/videos

Images: Base64 data is supported
Video: Start with video asset workflow is not supported as of now

[freked]

Hey, when you say "as of now" do you still mean it's coming at a later stage? Because if not, this is breaking a vital function of our implementation and we will not be able to move on to v4 until it's available!

[freked]

Just to clarify, above question was for @erinferinferinf regarding the below:

"Video: Start with video asset workflow is not supported as of now"

[Dat3473349766rv]

@nhung.ng @erinferinferinf It seem now the v4 editor coul pre-load and open video file type in url. But I cannot download/export the file. The dowload dialog keep showing that there is something uploading event though nothing there. Do you have any ideas about this?