Web on Mobile Issues
There are a couple of users who are reporting issues with using my Web app on a mobile device. Issues like the map disappearing or flashing multiple times when navigating it. They are on supported browser and OS versions. The documentation says that they cannot provide exact hardware requirements, so does anyone have any similar experiences they can share of what worked or didn't? I'm assuming it's a performance issue, but I can't replicate it on any of my devices. I don't think my app is particularly demanding (no 3D or anything). I have 8GB of memory, have you seen performance issues while having 4 or 6GB? The documentation says 4GB is recommended for 3D support, so it seems like 4GB should be fine for 2D.
-
may be related to a known issue described here:
"There are reports of VertiGIS and Esri apps based on Maps SDK for JavaScript crashing on older devices with a map lockup or blank map. Most often this is accompanied by a WebGL error. This is not specifically a VertiGIS issue; non-VertiGIS apps based on the Maps SDK for JavaScript are experiencing this as well. From our investigation, this appears to be related to later versions of the Maps SDK for JavaScript requiring additional resources. In general, when an older device comes close to being at resource capacity, the WebGL context lost error is the browser throwing out the WebGL context in self-preservation, to ensure it does not reach resource saturation and crash. We have worked with several customers to help them tweak their applications to be below the resource thresholds, but there may be some apps and devices that continue to exhibit this behavior. "
I'm asking support if they have any best practices to tweak my applications.
0 -
Any update on this, I have users on Google Pixel devices that are struggling to open an application that opens perfectly fine on an iOS device.
1 -
I think this is worthy of a bump. If VertiGIS Studio Web is used as a public facing map for applications, there are users that do not always have WebGL enabled on their browsers appropriately. Can we get a downgraded or compatibility version for those that don't have the ability to enable or don't know how to enable WebGL?
0 -
I haven't heard anyone having this issue lately. Back when I was troubleshooting it, it was helpful to have them go to https://get.webgl.org/webgl2/ to see if WebGL was indeed the problem or not. FC_Basson's solution about changing the chrome or edge flags for the graphics backend here did help some of my users.
0
Please sign in to leave a comment.
Comments
4 comments