nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Popups completely break and domains don't show in Experience Builder since the June 2026 update

IvaneKonchakovi

Hi everyone,

I’m running into a issue with an Experience Builder app right after the June 2026 update, and I wanted to see if anyone else is experiencing this.

First, the domain descriptions in my popups stopped showing and reverted back to raw coded values. After navigating around and clicking a few features, the popups freeze completely and stop opening at all.

The underlying web map works perfectly fine when opened in Map Viewer. The popups work great there and domains display correctly. The issue only happens inside the Experience Builder app itself.

It looks like something changed under the hood with how the new JS SDK reads table templates and background web workers for coded domains, causing the whole click framework to crash after a few pans and zooms.

Is anyone else hitting this since the update?

タグ付きの投稿をもっと見る

ArcGIS Online

Accepted answers

All comments

JonHaslag

Seeing the same thing in some of by Experience Builders. Also seeing issues where related records are not showing up in these pop-ups. Have tried clearing the cache on my browser, as was suggested in other posts. While this did temporarily fix issues I was having with other EBs where the pop ups were not displaying at all, or not displaying arcade/html, it did nothing for this issue with domains and related records.

Just like you said the domains, and related records, continue to display correctly in the Map Viewer. In addition, when I use the Near Me widget in Experience Builder to view these records the domains and related records do show up as expected in the widget search results. When I then use the 'Actions' button in the widget results to 'Show pop-up' the pop-up displays correctly in the map pane (all domain values and related records) and continues to work as I navigate through related records and back to the parent until the pop-up is closed.

Hi @IvaneKonchakovi and @Jon_Haslag I encourage logging Tech Support Cases so we can take a closer look at the app configurations. https://support.esri.com/en-us/overview

kxu

Hi @IvaneKonchakovi,@Jon_Haslag,

I couldn't reproduce this issue. Could you share a public app for us to troubleshoot?

Thanks,

IvaneKonchakovi

Hi,

Unfortunately, I can't share our apps publicly.

I am attaching some screenshots here. Last one displays errors in dev tools.

If I can provide other details/information without sharing the app, please let me know.

Thanks!

Screenshot 2026-06-30 095937.png Screenshot 2026-06-30 100101.png Screenshot 2026-06-30 100207.png

kxu

Hi @IvaneKonchakovi，

Thanks for your reply.

The popup in Experience Builder is not displaying correctly, but it works correctly in Map Viewer, right?

Experience Builder popups use the ArcGIS Maps SDK for JavaScript API, and the popup content cannot be modified on our side. I’m not sure if this is related to the data.

Could you share the steps to create and publish the data? If we can reproduce it, we can investigate further.

Thanks,

IvaneKonchakovi

Hi Ke,

Thank you for looking into this.

To clarify, the data works perfectly in map viewer, and the exact same layers and pop-up configurations previously worked in Experience Builder right up until the June 2026 update.

Data is created in ArcGIS Pro version 3.5.0 and fields utilize standard coded value domains configured at the geodatabase level. Published as a map service directly to our organization's on-premises ArcGIS server and then added to ArcGIS online web map as an layer via its REST URL. Experience Builder app contains a map widget pointing to the web map above.

Because the data is coming from a ArcGIS server, it looks like the updated JS SDK layout in Experience Builder is failing to parse or fetch the domain sub-layer resources from the server's REST endpoint properly, causing a memory leak or a thread crash in the background web workers.

I am sharing one of our apps with some publicly accessible layers -

https://experience.arcgis.com/experience/9d4f04577a224bc082a24d570ffeb688

Let me know if you need any additional details.

IvaneKonchakovi

I have some updates on reproducing this issue. It looks like the June 2026 update actually introduced two separate regressions regarding how Experience Builder and the Maps SDK interact with external ArcGIS server services.

As displayed on the one of the above attached screenshots the underlying SDK type accessor is failing to recognize or autocast domain schemas coming from our ArcGIS Server REST endpoints. Here is the console error trace:

core.js:5
[@arcgis/core/core/accessorSupport/ensureTypes] Accessor#set Invalid property value, value needs to be one of 'esri.layers.support.RangeDomain', 'esri.layers.support.CodedValueDomain', 'esri.layers.support.InheritedDomain', or a plain object that can autocast (having .type = 'range', 'coded-value', 'inherited')
s@core.js:5_log@core.js:5error@core.js:5
...
(anonymous)@TableTemplate.js:3set columnTemplates@TableTemplate.js:3
...
createDataSourceByLayer@index.js:1

As you can see from TableTemplate.js and createDataSourceByLayer in the trace, when Experience Builder initializes the layer's data source, the newly updated JS SDK fails to parse the coded value domains. It throws a hard validation error, causing the pop-ups to revert back to raw coded values instead of domain descriptions.

I managed to isolate why the click framework was freezing completely after a few pans and zooms. Upon service publishing, our layer's Shape/Geometry field was hidden.

While this was never an issue prior to the June 2026 release, the new update causes the pop-up click listener to completely crash if it hits a feature layer with a hidden geometry field. I went back, unhid the geometry field, and republished - the hard freeze stopped happening.

Current status:

The Freeze Bug: Can be bypassed by ensuring geometry fields are visible, but the Maps SDK team should look into why a hidden shape field now crashes the pop-up handler.

The Domain Bug: This is still fully active. Even with the map clickable, the error trace above prevents the app from displaying domain descriptions, leaving us with raw codes.

IvaneKonchakovi

BrandonForman

I have also noticed this when publishing new maps and or/overwriting existing maps since the June 2026 update. Any new map I published displays the expected domain descriptions in map viewer, but not in experience builder or other apps. An existing map/experience builder app I have was working fine in both areas until I overwrote it yesterday. The domain descriptions now no longer display in experience builder. We are using the Utility Network model.

I also tried the work around of selecting a feature using the select tool and/or selecting a record from the table (the table IS showing the domain descriptions). Then using the action button to display popup. The descriptions will then show up for that record. So the problem seems to be from directly selecting the feature on the map.

JianxiaSong

@IvaneKonchakovi, Thank you for the detailed information. It appears that Map Viewer popups use a different underlying technology than Experience Builder and Dashboards. To help narrow down the issue, could you try using the same map in ArcGIS Dashboards and let us know if the problem occurs there?

JianxiaSong

@BrandonForman , the domain description issue in the pop up appears a known issue. It is currently under investigation.

IvaneKonchakovi

Hi @Jianxia

I can confirm that issue persist in Dashboards too.

Screenshot 2026-07-01 120552.png

JianxiaSong

@IvaneKonchakovi , thanks for the confirmation. This is a known issue and is being looked into.

LA_GOHSEP_CIS_Coordinator

Experiencing this issue with fields in popups not showing across all of our Experience Builders as well, but popups in our dashboards are fine.

JianxiaSong

@LA_GOHSEP_CIS_Coordinator , this seems a different issue. Can you share a reproducible sample or contact Esri Support?

JianxiaSong

@IvaneKonchakovi and all, the pop-up issue should now be resolved in production.

If you are still seeing the issue, please share a reproducible sample or contact Esri Support, and we will continue to investigate.

Thank you for reporting the issue and for your patience while we worked to resolve it. We appreciate your help and feedback.

IvaneKonchakovi

@Jianxia Thank you for collaboration. The pop-up issue is resolved on our end.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.