Instant Apps (Basic) – Configuration panel freezes on public ArcGIS Online account (Uncaught TypeError: includes of null)

280
1
Jump to solution
02-26-2026 11:52 PM
HG_
by
New Contributor

I am experiencing a critical issue with ArcGIS Online Instant Apps (Basic template) on a public (individual) account that is not connected to any organization. Issue started recently (after latest Instant Apps update – Calcite Components 5.0.2) When creating a new Instant App, even from a brand-new Web Map without any custom layers (no GeoJSON, no WMS, no search configuration), the configuration panel behaves incorrectly. Opening the app configuration works. Clicking the “Share” button opens the publish panel. After the panel appears the “X” button does not close it.The rest of the UI becomes unresponsive. The only clickable button is “Publish”. Clicking “Publish” causes the page to freeze completely. The same behavior occurs with newly created Web Maps, default settings only

Console errors (relevant excerpt):

mapA11yDesc does not have a default value defined.
measureAreaUnit does not have a default value defined.
measureLinearUnit does not have a default value defined.
enableHighlightColor does not have a default value defined.
enableHighlightHaloColor does not have a default value defined.

Uncaught TypeError: can't access property "includes", t is null
at buildSettingsPanel
at _initConfigPanelUIBuild
at initialize

The error appears to originate in ApplicationBase during configuration initialization. It looks like required default values are not being provided, and the UI attempts to call .includes() on a null value.

Has anyone else encountered this issue recently?
Is this related to the recent Instant Apps / Calcite update rollout? Any guidance would be appreciated.

Thank you.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
ChryseMorales
Esri Contributor

Hi, we are able to reproduce and have logged BUG-000183113. We'll work on getting this fixed 

View solution in original post

1 Reply
ChryseMorales
Esri Contributor

Hi, we are able to reproduce and have logged BUG-000183113. We'll work on getting this fixed