Participant

INVALID_PSD_URL When loading the editor with media

Forum|Forum|1 year ago
February 22, 2024
13 replies
1755 views

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.

D

Dat3473349766rv

Participating Frequently

@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?

freked

Known Participant

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

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

freked

Known Participant

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!

erinferinferinf

Adobe Employee

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

erinferinferinf

Adobe Employee

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.

nhung.ng

Participating Frequently

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

nhung.ng

Participating Frequently

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
);