I believe the issue with your story is that each of your web maps uses a vector basemap. There is currently an issue on iOS devices if there are too many vector tile layers. We are looking into how to address this in the future, but we have a few technical challenges to overcome to get there. Here are two things to try to workaround this:
First, if you can do without the overview map the simplest thing would be to try removing it from each section. Having that open is currently doubling the number of vector tile layers in your story.
If removing the overview maps doesn't fix things, this should (and you may want to do this anyway, for reasons mentioned below): try using a single web map for all the sections of your story map (that way the vector basemap will only load once). To do this:
- Add all your layers to the same web map and turn them all off
- Add the web map you created in step one to the main stage of each section of your story
- In each section use the "Custom Configuration" option for Content and Location to set the visible layers and map extent for that section. You can see this article for more information.
If you do this second workaround, you may be able to keep the overview maps. Also, the main stage won't need to reload each time you switch tabs, you'll just see the new layers pop-in and the map pan/zoom to the correct extent, which will be a much nicer experience for your readers.
Let me know how these work out for you.
Owen Evans
Lead Product Engineer | StoryMaps
