Hello , I'm having a problem with a mobile app that , on devices OPPO huaewi and redmi, doesn't pass from the splash screen untill gives error .only on this devices this problem is happening ...any ideia how to solve this ?
Adjust device settings
On OPPO, Huawei, Redmi devices:
Turn off Battery Optimization for your app.
Allow Auto Launch and Run in Background.
Disable MIUI optimization (for Redmi/Xiaomi).
Settings → Additional settings → Developer options → Disable “MIUI optimization”.
Thank for your answer ! I already did this steps and didn't work ..
Hi @Diogo Coelho ,
This issue often occurs on certain Android devices, especially Oppo, Huawei, and Redmi. This happens because of their strict background app restrictions and problems with WebView compatibility.
Here are a few steps you can try to fix it:
Check WebView Version:Go to Settings, then Apps, and tap on Android System WebView. Make sure it’s updated to the latest version from the Play Store.These devices sometimes come with outdated or modified WebView components, which can cause apps to fail at startup.
Clear Cache and Data:Clear the app’s cache and data by going to Settings, then Apps, and selecting [Your App]. After that, relaunch the app.
Verify Permissions:On some Oppo and Huawei devices, the app needs permission to run in the background.Go to Settings, then Battery or App Launch Management. Allow the app to "Run in background" and turn off any automatic management.
Splash Screen Timeout:Check if your app logic relies on asynchronous calls, like user login, network requests, or local storage initialization during the splash screen.
Consider adding debug logs or a try-catch block to see if an error is stopping the transition to the home screen.
Build Version:If you’re using a custom build from OutSystems, rebuild the app with the latest MABS (Mobile Apps Build Service) version. Some older MABS versions had problems with Android 12 and above.
Test with OutSystems Preview App:Open your app using the OutSystems Now or Preview app. If it works there, the problem is likely with your native build setup, not the app logic.
If you can share the Android version and MABS version used to generate the app, it will help identify the root cause.Thanks and Regards,Akshay Deshpande