Hello,
I'm having a problem with a website I created in ArcGIS Experience Builder. I finished designing the layout for the desktop version and would now like to make some changes to the layout for the tablet and mobile versions.
However, when I switch to these versions in the Experience Builder app, I'm unable to change the body layout setting from "Auto" to "Custom." When I click on "Custom," I get a message asking me to confirm the switch, but after clicking "OK," nothing happens. This issue doesn't occur with the header or footer, where switching between layout types works fine.
The only explanation I can think of is that I created the project using a Living Atlas template— Topic Report and maybe the template has the custom layout option for mobile/tablet locked. However, that still seems unlikely to me.
Does anyone have an idea what might be causing this issue?
Solved! Go to Solution.
Thanks for your feedback! We’ve fixed this in the June 2025 release of ArcGIS Online. Please give it a try.
Amazing, it works now. Thank you.
I think I just ran into this same issue: I'm able to switch from Auto to Custom for the Header, but not the Body (same for both Medium and Small screens). Interestingly, I was just working on a different app a few hours ago and everything worked fine...
Any idea what's going on ESRI??
Looking at the Topic Report, it appears this template is already set to Custom from the start (when you create the app). Which menas this template is customized by default to provide a different experience on mobile, rather than Auto syncing with the Desktop layout.
You may need to switch back to Auto and then back to Custom to pull in your changes from desktop. But when doing this, you will lose any existing mobile customizations that were made, as the layout will sync back with what's in desktop.
Actually! I am seeing the issue you described now.
If you click on Auto and then on Custom again, the layout doesn't switch to Custom and remains "stuck" on Auto.
It looks like you found a bug, but it appears the team has planned a fix for it. It should be resolved by the end of this week! Thank you!
Thanks for your feedback! We’ve fixed this in the June 2025 release of ArcGIS Online. Please give it a try.