Hi everyone,
I'm wondering if anyone else has encountered this issue since the June 2026 ArcGIS Online update.
I'm trying to label linear features (rivers) in Map Viewer using the Center along placement. Instead of rendering correctly, the labels randomly drop letters from within the text (for example, "Castle River" may render with one or more letters missing, reading as "Cas l Riv r"). The missing characters mostly occur within the word rather than at the beginning or end, and the affected letters change as the map redraws with zooming/panning.
I've found that the issue persists for all label placement types, including Center along, Above along, and Below along label placement, and occurs at multiple zoom levels.
Environment/details:
- ArcGIS Online (June 2026 release)
- Map Viewer
- Line labels using the Name attribute of my data (no Arcade expression)
- Browsers tested:
- Microsoft Edge 149.0.4022.98 (64-bit)
- Google Chrome 150.0.7871.47 (64-bit)
The issue occurs identically in both browsers.
Troubleshooting:
I've tried the following without success:
- Simplified the river geometry extensively (including creating extremely simplified test features).
- Created additional line features to determine whether the problem was data-specific. The issue affects these new features as well.
- Changed the label font from Avenir Light to web-safe Arial (and many other test fonts).
- Disabled browser hardware acceleration.
- Enabled Repeat labels with a non-zero interval, and enabled overrun.
- Tested all available line label placements (Center along, Above along, and Below along).
None of these changes resolved the issue.
Additional notes:
- The issue occurs both in Map Viewer and when when the same web map is embedded in an ArcGIS StoryMap.
- The labels rendered correctly prior to the June 2026 ArcGIS Online update.
- Because the problem affects multiple line layers, multiple browsers, all available fonts, and newly created simplified features, I suspect this may be a rendering issue introduced in the June 2026 release.
Has anyone else experienced this? If so, were you able to find a workaround?
Thank you!
