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
+39-16Lines changed: 39 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,31 +3,54 @@ title: Home Page Unexpectedly Shown and WebView Reset in Dynamics 365 Field Serv
3
3
description: Helps resolve WebView reset issues in the Dynamics 365 Field Service mobile app.
4
4
author: JonBaker007
5
5
ms.author: jobaker
6
-
ms.reviewer: mhart
7
-
ms.date: 12/12/2024
6
+
ms.reviewer: puneet-singh1
7
+
ms.date: 07/11/2025
8
8
ms.custom: sap:Mobile Application\Application is throwing errors
9
9
---
10
-
# The Field Service mobile app shows the home page unexpectedly and a WebView reset occurs
10
+
# Troubleshoot WebView reset in Dynamics 365 Field Service mobile app
11
11
12
12
This article helps you troubleshoot and resolve issues in the [Dynamics 365 Field Service mobile app](/dynamics365/field-service/mobile/overview), where the home page is unexpectedly displayed, and a WebView reset occurs.
13
13
14
-
## Symptoms
14
+
## What is a WebView reset?
15
15
16
-
The Dynamics 365 Field Service mobile app unexpectedly displays the home page, and a WebView reset occurs.
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
-
## Cause
18
+
## Root cause
19
19
20
-
WebView resets for several reasons. When an Android or iOS device runs low on memory, it proactively closes apps to recover memory. Processes that use large amounts of memory include:
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
-
- Using the camera and uploading large files such as images, videos, audio, PDFs, or other documents.
23
-
- Customizations like PowerApps Component Framework (PCF) controls. For example, using annotations with custom controls.
24
-
- Sharing screen in Microsoft Teams.
25
-
- Running other apps on the device.
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
+
-**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
+
-**Desktop browsers:** WebView resets don't occur, but memory pressure can still be investigated using browser tools.
26
25
27
-
## Resolution
26
+
> [!IMPORTANT]
27
+
> Poor memory management in customizations can negatively impact the app experience.
28
28
29
-
Try the following suggestions to mitigate the issue:
29
+
## Understanding memory pressure
30
30
31
-
- Determine the cause of the reset. Use developer tools to inspect memory usage in the WebView in the app and browser. For example, [Debug JavaScript in mobile app on Android](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code#debug-javascript-in-mobile-apps-on-android) or [Fix memory problems](/microsoft-edge/devtools-guide-chromium/memory-problems/).
32
-
- Take steps to reduce memory usage, such as avoiding screen sharing or closing apps other than the Field Service mobile app that use large amounts of memory.
33
-
- Review [performance considerations when customizing the mobile app](/dynamics365/field-service/mobile/improve-mobile-performance) and take actions to reduce memory usage.
31
+
There are two main causes of memory pressure:
32
+
33
+
1. Memory spike
34
+
35
+
A memory spike occurs when a large object is allocated in the WebView process, causing a sudden increase in memory usage. Common causes include:
36
+
37
+
- Storing Base64-encoded images or videos in variables within [Power Apps component framework](/power-apps/developer/component-framework/overview) controls or web resources.
38
+
- Using JavaScript libraries that import large resource files (for example, font libraries.)
39
+
40
+
If you can reliably reproduce a WebView reset by performing a specific action (like opening a form or control), a memory spike is likely the cause.
41
+
42
+
2. Memory leaks
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 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.
45
+
46
+
## Troubleshooting memory pressure
47
+
48
+
To diagnose and resolve memory pressure issues:
49
+
50
+
- For iOS, use Safari memory analysis tools to check the memory performance of your iOS app module. For more information, see [the Timelines Tab in Web Inspector](https://webkit.org/web-inspector/timelines-tab/).
51
+
- The WebView reset error is specific to iOS applications running WebViews and can only be reproduced within that context. However, code that causes memory pressure on mobile also causes memory pressure buildup on desktop browsers. You can investigate the root cause of a WebView reset by using browser developer tools (such as Microsoft Edge DevTools) to track memory usage and identify issues. For more information, see [Fix memory problems in Microsoft Edge DevTools](/microsoft-edge/devtools-guide-chromium/memory-problems/).
52
+
-[Debug JavaScript code for model-driven apps](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code) to identify problematic scripts or customizations.
53
+
54
+
## More information
55
+
56
+
[Performance considerations when customizing the Dynamics 365 Field Service mobile app](/dynamics365/field-service/mobile/improve-mobile-performance)
0 commit comments