We noticed that on Android, the full-screen map does not seem to work. There seems to be a flash when you hit fullscreen, but nothing else. No problems on iOS and desktop.
Hello @Matthew Halliday / @Andy C
Just to close this thread and after some investigation (with the help of our native mobile team) we found out that this is caused by the version of the Android System WebView and this is something that is impossible for us to control since it's on the device's software.
You can check the version by searching for it in the Google Play Store:
For instance, we ran tests on several devices with different Android System WebView and here you have some of the results:
In addition, we reported this to Google Issue Tracker.
Cheers,GM
Hi Gonçalo,
- I'm currently running '112.0.5615.135 → doesn't work - ❌' on my main device and signing up for the beta version '114.0.5735.14 → works (beta version) - ✅'.
- I can confirm the above change resolved the issue for me.
- Thank you very much for your assistance!
Kind regards, Matt
Hello @Andy C,
Could you please provide a sample oml where you're facing that "flash"?And could you please give more context? Google Maps or Leaflet? How to reproduce it?
Andy has asked me to provide some further details on his behalf.
Since he posted this issue, we've seen a slight change in the behaviour where the map can now be made full-screen once, and then we can exit full-screen mode. Upon attempting to reenter full-screen mode, we experience a white flash and no change in the map display.
We're unsure what caused the change in behaviour, the only change we made was updating Outsystems_UI to the latest version.
Below is a screen recording of the issue occurring: https://www.dropbox.com/s/4e0no796j51an9u/OSMaps%20Fullscreen%20Issues.mp4?dl=0
The issue only appears to occur for the application versions installed on the device. The full-screen mode works as expected when assessing the map through a web browser or PWA.
I've attched an OML where we experience the issue.
Kind regards,
Matt
Hello @Matthew Halliday
After running several tests using a browser, PWA in Android I got no flash on any scenario.
Just a couple of findings (some won't have any impact):
The issue only appears to occur for the application versions installed on the device. The full-screen mode works as expected when entering full screen on the map through a web browser or PWA.
I've generated another OML (Attached) and removed the layouts. I can still consistently reproduce the issue on the following device types when the app is generated as an APK and then installed on the device via the APK:
- Google Pixel 6,
- Google Pixel 4,
- Samsung Galaxy Tab A.
Unfortunately, I was not able to reproduce the issue you mentioned.I tried with and without Layout on my Xiaomi Mi A3 with a native build (apk), in the mobile browser and Android as PWA and I got no flash/flickering 😶
If you open any other application that uses Google Maps do you get the same behaviour? Because OuSystems Maps only creates an instance of Google MapsWithout replicating I can't help much, sorry.
I've tested roughly 30 different apps which use Google Maps but couldn't find one that uses the full-screen mode via Google Maps.
Can you recommend one for us if you can think of one?
Thank you so much for your assistance with this issue!
Hi @Matthew Halliday
To be honest I'm not aware of any mobile application using fullscreen Maps. Even the Google Maps native application doesn't use that mode unless you're in navigation mode and, Google Maps does not even allow that mode in iOS by design as you can see here:
Independently of this, on another Android phone, I tried the same application I continue not to be able to reproduce the issue and I can't see any flash as you can see in the video attached.
Any update on this topic?
I think the video doesn't try the second attempt at opening the map, which is where the updated issue was (originally, it would not work the first load consistently; later, I think Matt indicates it's the second load).
We are trying to get the most consistency across the software, so in our ideal world, iOS, Android and web all have the same functionality, and there is still some value for our users being able to squeeze the extra real estate on the map. We can make the functionality ourselves that works across all devices, but we feel it is best if our underlying packages fulfil their functionality options. I would hope that iOS intend to support it in the future, allowing us consistency for iOS and Android, and for the time being, we could communicate the exception for our iOS users.
It doesn't appear you can replicate the problem, but the problem demonstrating persists, given a minimum example for us that excludes any logic that could be app-specific. It's strange, maybe, it could be related to other package versions e.g. OutSystem UI.
We were a little uncertain if we should mark this as solved as it's nonetheless outstanding for us and maybe a problem for other users. If it is a problem for other users, and it doesn't seem the function is not broadly used, it could be explicitly removed/communicated the capability is not supported for any devices as a clean resolution to the issue.
Anyway, just some thoughts and if you feel we should still close the issue we can, although the issue persists for us.
Andy
Hi @Andy C
First of all, thank you for the follow-up.
I tried the second time and what I checked was that I was not able to click the full-screen option (there's a backlog item to check that on our end under the code ROU-4234) but never got that flickering.
About the consistency between iOS and Android, there's not much that can be done (only if you implement on your end the fullscreen functionality instead of using the one from Google Maps) since Google Maps native application doesn't use that mode unless you're in navigation mode and, Google Maps does not even allow that mode in iOS by design as you can see in the link I shared earlier.
I would not mark this as solved since you're still being able to reproduce the issue I suppose you tried on different devices and we're ofc interested in trying to understand how to replicate it in order to be able to understand what's happening.
About using other versions of components like OutSystems UI I don't think it would influence, but if you could try to create a simple app with a screen without a Layout nor a theme or any other OutSystems UI dependency it would be great in order to understand if even outside your application and on an isolated environment you can still consistently reproduce that behaviour. If you can do this and provide some feedback afterwards it would be great.
Kind Regards,GM
Andy asked me to replicate the issue in an isolated environment with the details from the last paragraph:
- I've created an isolated personal environment and created a mobile app with everything removed except the map:
- I've removed any elements except the map itself:
- I've also removed all traces of OutSystems UI from the Themes and any CSS:
- I can consistently still reproduce the issue on the Two mobiles and Tablet listed in a previous comment. The example below: https://www.dropbox.com/s/peoixe0gmesnkc9/Map%20fullscreen%20occuring%20with%20MapTestApp.mp4?dl=0
- I've attached the OML file to this comment.
Thank you very much for the quick test. In order to try to reproduce, I just wanted to know if you're testing on a Native build (apk) or as a PWA.
UPDATE: I managed to reproduce the issue on a native build. If I find a fix or workaround I'll get back to you.
Just an update on this. We figured out that this is not an issue on the OutSystems Maps component but on the WebView where specific permission seems to be needed. We already escalated this to the team responsible for that area in order to try to have that addressed.