Latest versions of Chrome and Edge browsers seems to no longer allow native access that significantly limits testing options of mobile applications.Is there a work around for that?
Thank you
OutSystems support recommended this solution. It worked almost perfectly smooth.
The incident reported is a know issue reported in RPM-4491. To fix it, you need to access Factory Configuration (Install it if you have not done it before), then go to Platform Configurations and set the IndexedDB for Local Storage data on PWAs/Browsers to Enabled: After doing so you will need to apply the settings to your factory, you can follow the guide found here.As we believe this will fix the issue, and since there are no further actions on the support side, we will tentatively set this case as solved. Nevertheless, should you have any further questions regarding this, please do not hesitate to contact us.
We are running our application as a DETACHED service. We use the browser to run a local copy of the mobile application for testing purposes. This process has now been reporting that we cannot write to local storage. I assume it is the same issue being discussed here but I am not sure how or even if we can use the above recommendation to setup our DETACHED applications.
We are able to perform basic maintenance in the server application by compiling C# code and the mobile application by manually modifying the React .JS files (We cannot "compile" the mobile application).
Is there some way we can still fix whatever is necessary to solve this issue?
Hi,
I will ask around at OutSystems. But I believe there has never been an official statement or documentation that Edge browser is supported for mobile testing. Obviously for Chrome it should work.
https://success.outsystems.com/documentation/11/setup_and_maintain_your_outsystems_infrastructure/setting_up_outsystems/outsystems_system_requirements/
But are you using a specific plugin for accessing local storage on your mobile device, that could explain the error message also?
Regards,
Daniel
It seems like a recent update for all Chromium based browsers. Chrome 119.0.6045.105 has this limitation. Previous version was working fine. No additional plugins or extension.
Hi Mykola,
I'm running Chrome version 119.0.6045.106 and I can still access mobile apps with no issue. Is it possible that you're still using an old platform version, from before the switch from WebSQL to IndexedDB?
Edit: That might indeed be the case. It looks like Chrome recently removed support for WebSQL. Source: https://developer.chrome.com/blog/deprecating-web-sql/
Great article! We have Version 11.19.0 .
What version was this switch introduced? Do we have to do something on the app itself to use indexedDB?