Cannot get past the first screen when creating a new map

[2michaelhammond]

Description

I cannot create a new map. The application does not advance from the "Create a map" step to the "Define Locations" step.

Steps to Reproduce

1) Select GeoOps (Public) from list of NR1 Apps 2) Select "New Map" 3) Fill in details on the "Create a Map" screen 4) Click on "Continue"

Nothing happens after that

Expected Behaviour

I expect to progress to the second screen "Define Locations"

Relevant Logs / Console output

I see this error in the Dev Console: "DOMException: Blocked a frame with origin "https://one.newrelic.com" from accessing a cross-origin frame."

Your Environment

• NR1 CLI version used:
• Browser name and version:
• Operating System and version:

Additional context

[jpvajda]

@bobj82 was going to take a look at this issue and let us know if we need to assist.

[pmoore123456789]

I have this issue too. Multiple browsers, and same problem. Clicking each step at the top takes you to it but the settings do not commit and the continue button does not work. Also tried the JSON upload method but none of the workloads appear in the list so can't assign to a location. Browser console indicates multiple JS errors

[jpvajda]

@bobj82 have you made any progress on resolving this?

[bobj82]

Since the catalog(Public) version and my local version are unchanged, this is outside the scope of what we can fix within this code without some direction. Mike and I need someone to solve this issue.

I have

• not made any progress.
• escalated the issue and provided the attached browser console log.
• tested the behavior with a standalone version running nerdpack:serve --verbose that is unchanged and worked properly prior to the problem appearing.
• tested the behavior using the public app accessible from my New Relic email.
• tested with both Chrome and FireFox with no difference in the outcome.
• noticed that CORS errors are appearing that had not appeared previously.

When you click on the Continue button to go to the location page, the log reflects:

1. CORS errors
2. DOM exception
3. location.search.match... is null
4. For the public catalog version, you end up on a page with a GUID URL. For example: https://02f8775c-c248-42d4-be54-2f96443f786a.g0.nr-ext.net/?
5. For a nerdpack serve, you end up on a NR1 Sandbox page.

Attached is one of the logs I captured for reference and a screen shot of the browser before and after clicking the Continue button. geoops-console-catalog_version.log

[pmoore123456789]

Thanks @zstix , much appreciated :)

[LizBaker]

we have a hypothesis about a react versioning issue since the platform is semi upgraded to react 17. specifically the react-jsonschema-form library has a form component that this app relies on. we've found a workaround for it that should be fine for now and we could consider swapping out this component entirely at a later time

[jpvajda]

@LizBaker YES! amazing work. Thank you so much. 🥳

[nr-opensource-bot]

:tada: This issue has been resolved in version 1.5.5 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: