Hi! I see you're getting a "network request failed" error on the MWS app. I’d like to help you get this sorted out. To start, could you tell me if you’re connected to Wi-Fi or mobile data when this happens? Also, does it happen consistently, or intermittently?

Meanwhile, here’s a simple checklist we can try step-by-step to address this common network error on your Android 10 device and WebKit browser environment:

1. Check Internet Connection
Make sure your device has an active and stable internet connection. Try opening a webpage in your browser to confirm connectivity.

2. Restart the Device
Sometimes, a simple restart can refresh network settings and fix temporary glitches.

3. Clear App Cache and Data
Go to Settings > Apps > MWS App > Storage, then clear cache and, if needed, clear data. This removes potentially corrupted temporary files affecting network requests.

4. Update App and System
Ensure the MWS app and your Android system are up to date. Older versions may have bugs impacting network communication.

5. Check App Permissions
Verify that the app has permission to use mobile data or Wi-Fi. Settings > Apps > MWS App > Permissions > Network access.

6. Disable VPN or Proxy
If you’re using any VPN or proxy, try disabling them temporarily to see if they’re interfering.

7. Try Switching Networks
If on Wi-Fi, try mobile data or vice versa, to rule out network-specific issues.

If you’ve tried these steps already or still face the issue, let me know and we can dive deeper—like examining app logs, advanced network settings, or checking if there are known outages from the service provider. I've also seen that sometimes the NIMC Mobile ID app (related service) suggests simply retrying after a moment if this error appears1 6.

Do any of these match what you’ve tried so far? Let me know!

I have tried all the steps already and the problem is not solved.

Thanks for letting me know you’ve tried the basic steps already. Since the usual fixes didn’t resolve the "network request failed" issue in the MWS app on your Android 10 device, we can consider some more advanced troubleshooting tied to the app or server side.

Here’s what I suggest next:

1. Check for Permission or Token Expiry Issues
Sometimes, the app’s network requests fail because the authentication tokens or permissions expired. Verify if the app requires you to re-login or refresh any credentials. This is common in some MWS-related services where permission renewal resolves request denial errors5.

2. Confirm No Service Outages or Server Issues
Since the app depends on backend servers, ensure there are no downtime or server errors from MWS side. Outages or configuration errors (like database issues) can cause network failures even if your device is fine4. You might check status pages or community forums related to MWS for any ongoing incidents.

3. Look into App-Specific Logs and Clear Reinstall
Uninstall the app completely, clear any leftover data on your device, then reinstall it. Sometimes, installation corruption can cause persistent network failures. Also, if possible, check the app logs (if accessible) for error details.

4. Advanced Network Settings
If your device has any restrictive firewall, VPN, or proxy settings active (sometimes on Android 10, certain data saver or security apps interfere), try temporarily disabling them. Also, check your APN (Access Point Name) settings to confirm mobile data is correctly configured.

5. Contact Support with Logs
If none of these steps work, it may require escalation. Contact MWS app support with details of your device, network environment (Wi-Fi/mobile data), the steps you’ve tried, and any error log info you can gather. They may have backend fixes or patches available.

Would you like a guide on how to collect app logs or assistance un/reinstalling the app thoroughly? Let me know what sounds good to you!

Recent updates or bugs in MWS app?

Thanks for asking about recent updates and known bugs for the MWS app. Here's what I found regarding the MWS: NIMC Personal ID app updates and fixes through 2023 and into 2024:

- The latest version 4.7.1 as of July 27, 2024, included bug fixes aimed at enhancing overall app experience, although specific bug details weren't listed1.
- A notable update on November 13, 2023, version 4.6.1 addressed issues like inaccuracies in date of birth (DOB) and fixed errors related to "wrong ID level" messages in the app9.
- There are no publicly noted ongoing critical bugs for Android version or network failures specifically in these recent updates, but improvements have focused on reliability and identity verification accuracy.

Since you’re still seeing "network request failed" errors despite updates, it might be unrelated to these reported bug fixes and could point back to connectivity, permissions, or server-side issues.

Would you like me to guide you through collecting logs or contacting official MWS app support for a more tailored troubleshooting? Or any other areas you want to explore?

Yes

Great, you want to know about MWS app support problems to see if your network request failure might be related. From what I see, common MWS-related issues and support challenges include:

1. Slow Startup and Service Delays: Some users report MWS taking longer to start during updates or fix applications, which can cause follow-up failures or delays in processing tasks1 8.

2. Inconsistent Access Issues: Administrators sometimes experience inconsistent behaviors such as being unable to view transactions, which might be related to server-side glitches or user permissions2.

3. No Response from MWS Server: Community reports point to server unavailability caused by restarts, downtime, or server overloads affecting responses from MWS3.

4. API Access Denials & Credentials Problems: Some developers face denied access to MWS APIs or issues applying for credentials, which can block network requests involving authentication7 9.

5. User-Related Configuration or Hostname Issues: Changes in hostnames or server configurations sometimes require service restarts to reflect changes properly and avoid communication failures6.

6. Tips for Contacting Support: Developer support tends to be via email due to detailed info sharing, while seller support might include phone/chat options5.

Given your persistent "network request failed" error, it’s possible this is tied either to temporary server unavailability, permission issues, or network restrictions in your environment.

If you want, I can help you prepare the details and logs to send an effective support ticket or suggest ways to monitor MWS server status for outages. Would you like to proceed with that?