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; } } }

Experience Builder map disappears in mobile layout for Pixel 5>Android 14 >Chrome Browser

dcoley

Hello - I've spent many hours tuning my 3-page experience. This is a Utility Locator with a home page, a water map and a sewer map. I am using a layer list, legend, search and near-me widgets in both maps.

For the map pages, the experience is using a custom Grid layout, each tuned to go 'go vertical' for Tablet and Mobile sizes.

On Desktop in Chrome, the expand and full screen options work just fine.

On/in an Pixel 5>Android 14 >Chrome Browser, the expand function for the Grid does not work, the full screen option does. More disturbingly however, the map begins to 'flicker' when zoomed into 1000ft, and then disappears entirely when zoomed in further.

I tested the experience (dart layout) that can be found in this recent post:

https://community.esri.com/t5/arcgis-experience-builder-questions/map-freezes-or-locks-up-when-panning-or-zooming/m-p/1345040#M9130

and the same behavior is displayed when zooming the @Matt-Barrett map as well, so I would say the behavior is not unique to the Grid layout on mobile android.

I can say that in both experiences, grouped layers are being used from the webmap and consumed in the layer list widget. When I turn off the grouped layers at the group level, the map does remain visible on screen, but the Grid layout expand capability remains disabled.

Lastly, I have tested my experience on iPhone14 and iPhone15 Safari and everything behaves as expected, in fact very nice on the iPhone15

Pleas see for yourself if you have time:

https://experience.arcgis.com/experience/b6f8a5bc44e145c48b6d2e06189276cc

@TonghuiMing

@Jianxia

@AzizaParveen1

Thanks,

David

Vind meer berichten getagd met

ArcGIS Online

Accepted answers

All comments

DanCopKac

Popups have something to do with it. When a popup is present (docked, undocked, minimized), so when a feature is selected, it blocks the redraw of the map view. You can tell the redraw is not happening because the screen usually flickers when something changes. If the popup is present, already drawn elements remain on the screen until the map view is forced to redraw, in which case it won't, and the screen goes blank.

Absolutely infuriating. Just one bug after another in nearly every widget. Sure, maybe THIS TIME, it's Android's fault, or JS's fault, but its just happening one time too many, way too often.

Gene_Sipes

Do you have an idea of how large the problem is? 3 in 10 users, etc.

dcoley

So the current version of Javascript is 4.30 and so what I think the bug fix notes mean that the issue is resolved in the upcoming 4.31 release, which I believe that the next ExB release will include.....

AlexErnst_IDPR

ExB Update released October 18 did not resolve the bug.

Esri wrote:

Updates have been made to the following defect which you are associated with:
BUG-000166041 - Unable to view more than five layers in the ArcGIS Experience Builder Map widget on Android devices.

Status: Fixed (Learn More)
Version Fixed: 4.31
Alternate Solution:

Use devices with more resources running the latest supported manufacturer OS.

Additional testing of users' affected devices is ongoing, but so far this issue --known to be based on the Javascript release starting after 4.27 with 4.29, with release 4.31 has not abated on affected devices.

Test here https://arcg.is/0vzLeu (click through "Let's Ride!") ...

If you see features rendered on this map right away, your able device is not affected.
If the map frame is gray and featureless, your device is affected by the bug and is a "device of differing capabilities." (Map should finally render if you zoom out to 10+ miles.)

Having to maintain separate, max-5-layers versions of our ExB apps to accommodate "devices of differing capabilities" continues to cause reputational harm to State of Idaho's mapping program efforts.

Gene_Sipes

Thanks for the update!

AlexErnst_IDPR

Esri has informed us that the target for releasing a fix for this bug is now November 2024.

In the meantime, we have released a parallel app which is tuned to display a max of 5 layers at a time:

https://experience.arcgis.com/experience/cbf69647a0774d83a3e419fc82e1ddda

We worked around the issue by limiting the visibility range of boundary layers to drop out as the user approach <15 miles, and reducing filtered visibility granularity of routes by type. Zooming all the way in to max now shows roads and trails without blanking out. In our landing page (trails.idaho.gov) we've characterized this an "option" for "devices of differing capabilities" so as not to impugn Android users' life choices (like mine). And you can switch between the two so it appears fairly seamless.

AlexErnst_IDPR

Screenshots of just a few of the Androids that succumb to the bug. If any theme emerges, hopefully this will give Esri engineers a clue how to resolve.

Samsung S10e

Sam A42 (A32 work fine though!)

mthompson_WellesleyMA

Having a similar issue. Map works great in desktop and tablet but on a phone the features do not show up at most zoom levels. Seems to be related to when a feature is selected for me. Layers work ok when first opening the app, but once a feature is selected they all disappear.

Gene_Sipes

Thanks for providing further context on this bug. ESRI support logged the following bug for me in regard to this issue.

https://my.esri.com/#/support/bugs/bugs?bugNumber=BUG-000166041

AlexErnst_IDPR

Update 6/28/24: Have received several more screenshots of affected phones' system details to provide to Esri Engineers.
The problem is getting worse... Recently Firefox --the workaround was to install and use a non-Chromium browser, started exhibiting the blank map bug too, for some but not all users experiencing the problem in Chrome. So, Update Creep is biting us.
Bug has been escalated, has a status of "...added to the backlog, to be addressed in near-term release."
https://my.esri.com/#/support/bugs/bugs?bugNumber=BUG-000166041

UPDATE 4/30/24: Investigation show that Javascript 4.29 may be at the heart of this problem. An Esri engineer and my colleague who are working through this found rolling back to JS 4.27 in a test app resolves the map-blanking-on-zoom problem. Now, how to fix Experience to work correctly with 4.29, or get the relevant open-source community (?) to fix JS if the problem is not just Esri's products?

Updated 5/6/24: A Samsung S22 has the same problems and tested out the same way on a 4.27 SDK test version, that the problem is likely how ExB handles JS 4.29.

...................................................................................................

With thanks to OP @DavidColey , and @TonghuiMing, for their contributions, I'll chip in anew to bump the thread. This remains an issue. My org is attempting to communicate with Esri at a higher level but we have not many facts to go on.

But I'll add a few more facts to the collection, to help Esri in resolve this ongoing issue...

David pointed out that updating phones' OSs may resolve the issue, so I'm open to the idea that this may be an Alphabet Inc. problem and not an Esri problem. But we'll need help in outreach to Alphabet if that is where this needs to go.

In my group alone, 2 out of 12 testers of EB apps on various phones encountered the Chrome-browser-goes-blank-on-zoom issue on two related but different apps. I have a high-visibility EB app in "Beta" at the moment that is being held back and overdue for full public implementation over this problem. (iOS has no reported issue of this kind; Firefox on Android works without issues [Note 1], but that is not a good solution to tell users they need to load and use Firefox just for our app.)

In this app: https://arcg.is/0ivqPS

With the default settings as-published, the blank-map behavior is found to occur on zoom closer-in than "10 mi", or "2 mi", or even closer-in under another visibility circumstance, on two different model Samsung Android phones, in Chrome and Samsung's own browser simply called "Internet": A42 and S10e. (Firefox does not exhibit the behavior on either phone.)

Sam S10e OS etc., trying to get that info...
Sam A42 Android OS V. 13, Baseband V. A426USQS8EXB2, Kernel 4.19.152-perf-... dated 22-Feb., Security SMR Jan 2024 R1 ...more. Software update dated 2-Mar 2024 A426USQS8EXB2 insists it is current.
Almost identical Sam A32 does NOT exhibit the problem: Android OS V. 13, Baseband V. A326U1UESDDXC2, Kernel 4.14.186-27095505 dated 14-Mar., Security: SMR Mar-2024 R1 ...more. Last successful update 3 Ap 2024 (but testing prior did not show our issue) A326U1UESDDXC2.

Interestingly, the behavior resolves if the number of Map Layers selected as visible=1 is reduced from the default for our app of 20, and that final max number is variable dependent on the zoom level.
Set to ~7 or 8 layers visible, map visibility returns at 10 mi... until you get under 2 mi. Then map visibility resolves again if visibility is reduced to 6 or 5 or fewer Layer, then goes away again at 2000' with more un-checks getting the map back visible.
Example https://arcg.is/znLP
At this view of the app, zoomed in to 1000' and only 6 of the 20 standard layers in this EB app checked, the visibility problem abates (but there is a screen flicker on adding the 6th). Check visibility=1 on another layer and it's back to blank-map. Zoom out to 2mi and the map renders (maybe), but add an 8th layer, and we're back to blank-map. Out to 10 mi, we're back to visible; the app can render a map for 9 but not 10 layers, etc. (Visibility by Layer is tuned variably in the Web Map for features to start coming in at 20mi, then 10mi, etc. for different features filtered on a linear feature's type such as a road versus a trail).

I suppose our app is asking a lot of the EB platform. One linear class gets 10 Filtered cases to distinguish and make each case separately-selectable for visibility in Map Layers. But these filters are set in the Web Map, not on the Experience app. And Filtering does not appear to be at issue: In a temporary version of our app with no special filtering on the linear class in its Web Map, the blank-map behavior in its EB app is about the same-- 7 layers max allowed at 5000'. See https://arcg.is/1PWr9H1

Thing is, 20 or more visible layers was never an issue with our /webappviewer/ version of our map site, which we are scrambling to replace as the tech ages-out and we've been moved onto AGOL away from a soon to be retired Portal server.

One last detail: Pulling in REST services as optional layers may or may NOT add to the number of visible layers that tips the app over to blank-screening. I cannot put my finger on the theme as to why (play with our visibility settings of Optional Layers and you'll see the variability). May be a difference between a service being consumed from a Hosted Feature Service versus older tech Map Service?

. . . . . .

Note 1: Firefox mobile has an annoying auto-refresh "feature" which resets the app every time you tab away to another app then return to the browser. A solution is turning on all Manage URL options settings in the EB project, which solves the problem by having the page refresh to the exact view and visibility settings last set for the app as contained in the extensive URL parameters these settings drive.

Gene_Sipes

I am experiencing this too. Only on some Android phones but not any iOS.

Matt-Barrett

My issue may have actually been a failing video card in my desktop system. Dell just left after swapping out my card, and so far that seems to have been my problem.

dcoley

Hi @TonghuiMing - thanks for the reply and yes potentially I've maybe isolated the issue. It could also be device specific too. I've just upgraded my Pixel 5 to a Pixel 8 pro, and the map issues on the Instant apps and the ExB app are no longer present, whether point layers are present or not. The maps no longer flicker, go black, or disappear below certain scales on the 8 pro.

I can say that the 'Allow Resize' option does not function on the pixel 5 or 8, although the 'Allow Expand' continues to work.

TonghuiMing

@DavidColey Sorry for the delay as I am on from time to time, and glad to see that you've isolated the issue. I did create an internal issue for the corresponding party, but I am not clear about their timeline/schedule on the fix for this.

Bringing it up to a support analyst would also be a good idea. It might help move this forward. Thanks.

dcoley

Well, I'm completely stumped on this. I tried republishing my feature layer collection of water device POINTS from pro with the "use symbol types compatible with all clients", re-creating a simple map and publishing that map in a simple Basic Viewer Instant App. Same results - map disappears below certain scale levels when more than one point layer is visible.

Doesn't seem to matter if the map uses grouped layers or not. Doesn't seem to matter is the map is saved in map viewer classic. What does seem to matter is whether or not the Point Layers are visible.

My earlier reply with my Sidebar instant app does not have any point layers. So I wrongly assumed that the problem was ExB. But as @TonghuiMing correctly pointed out, the problem is in the Map Viewer on Android (but not iOS) because it continues to show here:

https://sarco.maps.arcgis.com/apps/instant/basic/index.html?appid=d7e15b494181451685d235e52dd1f52d

Thanks

dcoley

Hello @TonghuiMing - will you be reporting back here when and if an issue is logged and when we can expect a fix?

Otherwise I am going to turn this post into a support case and go from there.

dcoley

Hmm, not sure I agree completely. I have a sidebar instant app here:

https://sarco.maps.arcgis.com/apps/instant/sidebar/index.html?appid=65828fd9b26246cb9a994a3bf460476c

that has grouped layers in its layer list and is summarizing data values per district via FeatureSetbyName in the map$ profile and it doesn't have any problems on Android.

But, we did test Chrome on the iOS 14 for my app and it works just fine, so this is an Android issue for sure with the ExB and needs attention....

TonghuiMing

This is the similar behavior mentioned in this post:

https://community.esri.com/t5/arcgis-experience-builder-questions/experience-builder-not-working-on-motorola-one-g/m-p/1344405#M9090

The behavior for the map itself, on Android devices. It happens outside ExB as well, see this demo - https://jsbin.com/babiwepoqa/2/edit?html,output. I've reached out to the corresponding team to log an issue.

MaureenSpiessl

I am also having similar issues. Hopefully we can figure this out.

Matt-Barrett

Thank you! I guess it's nice to know that it's not just me!

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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