You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/field-service/mobile-app/webview-reset.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Helps resolve WebView reset issues in the Dynamics 365 Field Servic
4
4
author: JonBaker007
5
5
ms.author: jobaker
6
6
ms.reviewer: puneet-singh1
7
-
ms.date: 07/09/2025
7
+
ms.date: 07/10/2025
8
8
ms.custom: sap:Mobile Application\Application is throwing errors
9
9
---
10
10
# Troubleshoot WebView reset in Dynamics 365 Field Service mobile app
@@ -13,13 +13,13 @@ This article helps you troubleshoot and resolve issues in the [Dynamics 365 Fiel
13
13
14
14
## What is a WebView reset?
15
15
16
-
A WebView reset in the Dynamics 365 Field Service mobile app typically indicates that the app module is consuming too much memory. This is often triggered by activities that cause memory pressure on the WebView process. [Model-driven applications in Power Apps](/power-apps/maker/model-driven-apps/model-driven-app-overview), such as Dynamics 365 Field Service, run as web applications inside a WebView on the mobile client. As a result, they're subject to the memory management policies of the mobile operating system.
16
+
A WebView reset in the Dynamics 365 Field Service mobile app typically indicates that the app module consumes too much memory. It's often triggered by activities that cause memory pressure on the WebView process. [Model-driven applications in Power Apps](/power-apps/maker/model-driven-apps/model-driven-app-overview), such as Dynamics 365 Field Service, run as web applications inside a WebView on the mobile client. As a result, they're subject to the memory management policies of the mobile operating system.
17
17
18
18
## Root cause
19
19
20
20
A WebView reset occurs when the mobile operating system terminates an application process that exceeds its memory limits. The threshold for "too much memory" varies by device and operating system, so the issue might not always be reproducible.
21
21
22
-
-**iOS:** The WebView reset error occurs only on iOS because WebViews run in separate processes that can be terminated independently from the main app. If the WebView process exceeds the operating system memory threshold, it's terminated. The app detects this, restarts the WebView, and displays a reset message to the user.
22
+
-**iOS:** The WebView reset error occurs only on iOS because WebViews run in separate processes that can be terminated independently from the main app. If the WebView process exceeds the operating system memory threshold, it's terminated. The app detects this issue, restarts the WebView, and displays a reset message to the user.
23
23
-**Android:** The WebView runs within the main application process. If memory limits are exceeded, the entire app process is terminated, resulting in a crash.
24
24
-**Desktop browsers:** WebView resets don't occur, but memory pressure can still be investigated using browser tools.
25
25
@@ -41,7 +41,7 @@ There are two main causes of memory pressure:
41
41
42
42
2. Memory leaks
43
43
44
-
A memory leak occurs when memory allocated within the WebView process isn't released because of lingering references, such as event listeners or objects that aren't properly cleaned up. This prevents the garbage collector from reclaiming the memory, causing memory usage to gradually increase over time. For example, adding event listeners to the window object in JavaScript without removing them when navigating away can lead to leaks. If WebView resets occur randomly and aren't tied to a specific action, it's likely due to a memory leak from previous activities.
44
+
A memory leak occurs when memory allocated within the WebView process isn't released because of lingering references, such as event listeners or objects that aren't properly cleaned up. This issue prevents the garbage collector from reclaiming the memory, causing memory usage to gradually increase over time. For example, adding event listeners to the window object in JavaScript without removing them when navigating away can lead to leaks. If WebView resets occur randomly and aren't tied to a specific action, it's likely due to a memory leak from previous activities.
0 commit comments