AEM Form Editor Not Working on Fresh Install | Community
Skip to main content
Level 2
August 6, 2024
Solved

AEM Form Editor Not Working on Fresh Install

  • August 6, 2024
  • 1 reply
  • 612 views

For some reason, the AEM Adaptive Form Editor isn't working, even with a fresh local install of the AEM Cloud SDK and the Forms Add On. This used to work fine, and now when you create a form and it tries to load the form editor, the page just shows the spinning loading animation, and the web console shows the following error:

Access to XMLHttpRequest at 'https://adobeid-na1.services.adobe.com/ims/check/v6/token?jslVersion=v2-v0.31.0-2-g1e8a8a8' from origin 'http://localhost:4502' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

 

We've also noticed all of our cloud environments that have AEM Forms enabled in Cloud Manager now are all also exhibiting this same behavior as of a couple of weeks ago. We haven't changed any configs or any CORS settings.

 

What is this URL call (above) trying to do, and what does it have to do with AEM Forms?
https://adobeid-na1.services.adobe.com/ims/check/v6/token?jslVersion=v2-v0.31.0-2-g1e8a8a8

 

This is on the following SDK versions:
AEM Cloud SDK: 2024.7.17258.20240726T172406Z-240700

Forms Add-on SDK: 2024.07.17.02-240700

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by pankajpr

Hi @cdressler,

The console error you have mentioned is not AEM Forms editor specific. This is coming from core editor, the same error can be observed when you open sites editor. This error should not have any functional impact AFAIK.

Can you please provide the below details.

  1. Are you working with foundation AF or Core Component AF?
  2. Did you observe any stacktrace in server logs when you open editor.
  3. Any other console errors?

 

 

 

1 reply

pankajprAdobe EmployeeAccepted solution
Adobe Employee
August 7, 2024

Hi @cdressler,

The console error you have mentioned is not AEM Forms editor specific. This is coming from core editor, the same error can be observed when you open sites editor. This error should not have any functional impact AFAIK.

Can you please provide the below details.

  1. Are you working with foundation AF or Core Component AF?
  2. Did you observe any stacktrace in server logs when you open editor.
  3. Any other console errors?