Bug Reports

Our Express Embed has stopped letting anyone click the sidebar to add media or elements. Users can upload media but not click any of the other buttons to use any saved in files or add stock media or text. Thanks, Ru Howe

Using adobe express and find that every time I replace an image the change doesn't apply and I have to go in and do it a second time before it registers. I click image, click replace, click replace w/ upload, navigate to folder of image I’m uploading, select image, hit enter. It exits the upload screen, however the image remains the same as previous. Repeat the steps and it will then change.Definitely not express if I have to make every change twice.

We've just heard from another customer that login to Express Embed is not working on Safari on Mac, but is working on Chrome.In Safari in Express Embed, it loops back to the login screen after logging in with a valid account. We've tested on different Macs for us here. See screen recording here that my colleague just recorded.https://www.loom.com/share/f59cf896943f41dabf19553c726bc6a8But in full page Express, it is fine with the same account.We are on SDK v3. Perhaps it's that?I'm worried that something's changed in Safari.Please could you test at your end and see if it's the same for you for your own test Express Embed instance? This may be related to the other thread that I just posted about students not being able to log in - we're asking about their browsers.Attached is the Safari console log during the failure to login. I've run this past GPT, and it says:Observed Errors from Safari Console log:Identity Authentication FailuresIMSProfileNameMissingError: User profile is missin

Hey! I just got a report that the language switch in the embed SDK is not working.If you go into the settings & update the language, the UI will update at first. Then once you close the settings menu, the whole app will refresh and the language defaults back to english again.I'm seeing the same issue using both v3 & v4, and it can also be reproduced on the demo site https://demo.expressembed.com/ 

We recently switched to Adobe Enterprise licenses from Adobe personal licenses. One of our users has video he created in Adobe Express with his old account. He migrated the videos to the new account, but since starting to use the new account, he is no longer able to download video media. He can download pictures. THis is the error from the console.Access at ....from origin https://new.express.adobe.com has been blocked by CORS policy: response to preflight request doesn't pass access control check. No 'Access-control-allow-origin" header is present on the requested content. 

I’m trying to use the embed within an app that’s rendered in an iframe. I added the embedding domain to the allowed domains, but still get this error: > Refused to frame 'https://new.express.adobe.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' [REDACTED].com".

  1. Version of the app "dependencies": { "@adobe/react-spectrum": "^3.42.2", "@spectrum-icons/workflow": "^4.2.22", "axios": "^1.6.1", "react": "18.2.0", "react-aria": "^3.30.0", "react-aria-components": "^1.0.0-rc.0", "react-dom": "18.2.0"},   2. Platform and OS version: Desktop 3. Basic steps to reproduce the problem   - When mouse hover on the component, it throws Uncaught ReferenceError: process is not defined 4. Expected result and actual result   - The components should show the list of options and tooltip correctly.    Hi! I am currently working on my company's Adobe express Add-on. We've released the add on in the last year and now we want to update our Add on asap.   I found issues in adobe/react-spectrum during the development.    1. Tooltip component <TooltipTrigger delay={0}> <ActionButton isQuiet={true} onPress={() => HandleAvatar(item.key, page)} height={"10

Hi, Exporting a video with a colour background to use against a same colour background on our website, the background colour in the video changes on export.We've found this via our Express Embed so I am reporting it here.Background colour of images does not change on export.Specifically: I set the background colour of the Adobe document to FFCF03I export it as video and the background colour in the exported video comes out as FDD506See attached screenshot - the video is lighter, less saturated.The workaround for us to to edit our images and background colours to use the same colour as the video, rather than the other way round. Ideally that shouldn't be the case, of course - it should match the RGB colour we specified.And I understand the difficulties in colour profiles with video - but if possible, it would be great for the team to do some work on trying for greater colour matching on export.Thanks,Ru Howe

Logging into the v4 Embed doesn't seem to work and causes it to login momentarily but then refresh and reload the embed to a logged out state in seconds. Searching the forums it seems reported previously and is related to Safari blocking third-party cookies. It looks like there's missing implementation in the Embed SDK to make this work. Safari does support requestStorageAccess to allow users to opt-in to allowing it to work.https://privacysandbox.google.com/cookies/storage-access-api It would be worth attempting to detect if Partitioned cookie flag is supported too as Chrome/Edge and Safari 26 will support that. (CHIPS - Cookies Have Independent Partitioned State) Not easy to detect though.

Our Express Embed has completely stopped working around 1pm UK time.This is the browser console page.We are still on v3: https://sdk.cc-embed.adobe.com/v3/CCEverywhere.js

Urgent - the Resize, Background colour and other controls have disappeared from the top of the Embed modal.Screenshot attached.This affects all our users.This is a big problem. These are vital features.Could someone reply asap to acknowledge that you have seen this and logged it, or if it's not a bug let me know why it's disappeared?I wrote about this before, but it definitely still seems like this forum is not being checked, and so I am still very anxious about this given how prominent Express Embed is in our app.I realise the enterprise customers like Miro take priority - but the disappearance of replies feels stark at times like this. My other posts are not getting responses, even the fix I posted to the Safari bug. And that bug previously mostly went unresponded to before that, after I reported it in February.Looking at the forum here, the last 2 posts from people on 22 May went unanswered, and the last Adobe employee reply was May 9, 6 weeks ago.The forum URL was changed in the me

Hi folks,@ErinF  replied here in September to @JC França about opening a specific brand template where she said:An engineering team member says this:It is possible to load the Express with a specific template.createWithTemplate( docConfig: Editor.CreateWithTemplateDocConfig, appConfig?: FirstParty.Editor.EditorAppConfig, exportConfig?: ExportConfig, containerConfig?: ContainerConfig ) : void; Let us know if you need any clarification on this.Yes please, I'd like some help with it!And @Barranca helped @Pro Imaging LFP. with the issue I'm having with it, in November.Where Davide provided a Template ID copied from Adobe's own template section.When I use the templateId that Davide provided for the Adobe template:urn:aaid:sc:VA6C2:67e8c8d8-f5d0-5277-94a5-17c9b2b9bf25It works.But when I use my own published template ID (see URL) for a button image:urn:aaid:sc:EU:e7ae7e26-ad9e-469c-8a64-5f6afc8209dchttps://new.express.adobe.com/publishedV2/urn:aaid:sc:EU:e7ae7e26-ad9e

Hi all I am new to using the Embedded SDK in my new role and I was wondering why I am getting the following error when trying to authenticate my user in order to use Express features in my web app any information would be appreciated! { message: "invalid_credentials Invalid referer or origin", stack: "Error: invalid_credentials Invalid referer or origin at https://quick-actions.express.adobe.com/static/index.a2a53cf49afb42c82427.js:1:88248 at c.invoke (https://quick-actions.express.adobe.com/static/hz-startup-otel.cfde22d5d7383eb2d39d.js:2:8031) at s.run (https://quick-actions.express.adobe.com/static/hz-startup-otel.cfde22d5d7383eb2d39d.js:2:3424) at https://quick-actions.express.adobe.com/static/hz-startup-otel.cfde22d5d7383eb2d39d.js:2:18271 at c.invokeTask (https://quick-actions.express.adobe.com/static/hz-startup-otel.cfde22d5d7383eb2d39d.js:2:8649) at s.runTask (https://quick-actions.express.adobe.com/static/hz-startup-otel.cfde22d5d7383eb2d39d.js:2:4

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.jsPlatform and OS version: MacOS sonoma v14.1.1, Chrome Browser v129.0.6668.90Expected result and actual result: Should be able to export the project.

Hey! I'm currently unable to load any brand assets through the editor. When trying to open a brand, I just get an empty catalog like the image below.It works fine on https://new.express.adobe.com/, but not when viewed through the embed SDK so the issue seems to be isolated to the embed, same issue can also be verified on the demo site https://demo.expressembed.com/

Hi,I want to use the createWithAsset API. One of the parameters is createWithAssetDocConfig, which includes an asset.According to the documentation, the asset can be a PDF, but when I try to call the API with a PDF, I get the error: INVALID_ASSET_TYPE.Is PDF supposed to be supported?

Hi, We've had a support query coming in: A teacher in California is able to launch the Express Embed modal and login, but his students are not. In our application, they have exactly the same permissions. It seems to be a limitation from their IT department. I imagine blocking the student accounts from using cookies with Embed.Email from him after some investigation - where "Create Video in Adobe Express" is the Embed workflow: We discovered that I (with teacher credentials) am able to access the "Create Video in Adobe Express" - however my students cannot. They are able to work with Express in its own browser tab at new.express.adobe.com, download files to their workstation, then upload to Stornaway. However the "Create Video in Adobe Express" is the most seamless option which I'd like them to use. As such, I think this is an issue on our end. So in summary the students can use the full version of Express in its own browser tab but not the Embed. The teacher can use

Hi, I'm trying to create project with a video by using blob type. I used createWithAsset () method with bellow configuration but the edtior show an error message and then close. So if anyone know what I did wrong please let me know, any helps would be really appericated. Version of the app: v4Platform and OS version: Chrome 131.0.6778.205 (Official Build) (arm64)Basic steps to reproduce the problem:  ... // data dataUrl is a url to the mp4 file // fetch the file const fetchedVideo = await fetch(dataUrl); // covert to blob const videoBlob = await fetchedVideo.blob(); //open and upload to adobe embeded with below config ccEverywhere.editor.createWithAsset( { canvasSize: 'Video', asset: { type: 'video', dataType: 'blob', data: videoBlob, }, }, { selectedCategory: 'media', allowedFileTypes: ['image/png', 'image/jpeg', 'video/mp4'], callbacks: { onPublish: (intent, publishParams) =&

this pops up every time I try to open SDK in a localhost environment. Yes - it is set in allowed domains, yes - it has https. Could you please take a look why is this happening?Also is there a delay time between - chanigng the allowed domaind and actually seeing the change? I did a change adding a domain I wanted to test in on the production env. It din't work out. It worked out like 15 hours later without any changes from my side. Is there a way to speed this up? Also2, I have a feeling it's very random sometimes in terms of whether it opens or not. Like it's I'm not in a mood now, vibes off - not working. And starts working an hour after (again no changes). Is it because it's not yet review?

Hey everyone, I know this issue has been raised before, but we’re running into the same roadblock with V4 of the SDK. Everything functions as expected in our local environment, but once deployed to our dev instance (dev.appos.io), we hit the error: “Adobe Express is Not Available” We’ve triple-checked our API key, verified that *.appos.io, dev.appos.io, www .appos.io are all listed in the approved domains, and ensured we’re accessing the SDK over a secure HTTPS connection. I’ve scoured the forums and other resources, tested every suggested fix I could find, and still haven’t found a solution. We need to get this resolved ASAP. Any insights from Adobe or the community would be greatly appreciated! Thanks in advance.

I'm receiving this message, "Adobe Express is not available, You do not have access to this service. Contact your IT administrator to gain access." when I try to performance an action, I'm trying to use the SDK in a Google extension, but I've created a local server with HTTPS in the same port that I put in my API credentials, I tried to create a new credential but none of this worked  

Hello everyone,# Issue with Adobe Express Embed SDK - animateFromAudio Quick Action## Environment- SDK Version: v4- Browser: [Microsoft Edge Version 132.0.2957.115]- Client ID: Properly configured in Adobe Developer Console- Implementation: Web application using vanilla JavaScript ## What I'm Trying to AchieveI'm trying to implement the animateFromAudio quick action to create animations from audio files using the Adobe Express Embed SDK. The goal is to allow users to upload an MP3 file and convert it into an animation. ## Current ImplementationI've followed the demo example, github and sdk from the documentation: javascript const docConfig = { asset: { type: "image", dataType: "base64", data: base64Audio // Base64 encoded audio file } }; const appConfig = { callbacks: { onCancel: () => {}, onError: (err) => { console.error('Error:', err); }, onLoadStart: () => {}, onLoad: () => {}, onPublishStart: () => {}, onPublish: (publishParams) =&

I see the following messages when running the examples from https://github.com/AdobeDocs/cc-everywhere “Adobe Express is not available”.“You do not have access to this service. Contact your IT administrator to get access.” With the Adobe account I’m signed in with, I do have access to Express. Reproduction1. I downloaded the example from Github and followed the instructions.2. I installed local certificates.3. Server is running on www.jowan-deisgn.vercel.app Allowed domains includes that localhost port.

I see the following messages when running the examples from https://github.com/AdobeDocs/cc-everywhere “Adobe Express is not available”.“You do not have access to this service. Contact your IT administrator to get access.” With the Adobe account I’m signed in with, I do have access to Express. Reproduction1. I downloaded the example from Github and followed the instructions.2. I installed local certificates.3. Server is running on https://localhost:8000 Allowed domains includes that localhost port.  

Issue Description: We have implemented a CSP policy on our website to enhance security and protect against various types of attacks. However, we're experiencing a specific CSP violation related to framing content from 'https://quick-actions.express.adobe.com/'. The error message states: Refused to frame 'https://quick-actions.express.adobe.com/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors 'self' staging.paraclete.ai".Expected Behavior: We expect to be able to embed content from 'https://quick-actions.express.adobe.com/' within frames on our website without encountering CSP violations.Steps Taken: We have reviewed our CSP policy and confirmed that it includes 'self' and 'staging.paraclete.ai' in the 'frame-ancestors' directive. Despite this, we're still encountering the aforementioned violation.Request for Assistance: We kindly request your assistance in resolving this issue. Could you please provide guidance on how we can adjust o