Mapping and GIS Solutions Community

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Thanks Eric and Zach.  On my device I have followed your steps.  I am using a R12i so no sign-in is necessary.  With no internet connection, TMM still attempts to open a webview window and freezes.  

I have sent a screen recording and log files from both apps to Duncan-Parnell support as they work on the issue.

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Thanks Eric and Zach.  On my device I have followed your steps.  I am using a R12i so no sign-in is necessary.  With no internet connection, TMM still attempts to open a webview window and freezes.  

I have sent a screen recording and log files from both apps to Duncan-Parnell support as they work on the issue.

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Thanks Eric and Zach.  On my device I have followed your steps.  I am using a R12i so no sign-in is necessary.  With no internet connection, TMM still attempts to open a webview window and freezes.  

I have sent a screen recording and log files from both apps to Duncan-Parnell support as they work on the issue.

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Thanks Eric.  I can rule out another receiver being the problem and provide some clarification.  When I open TMM I am unable to select a receiver because the app attempts to open an external browser (webview) right away and freezes.  Sometimes it is possible to close the webview and continue, but not consistent.

Thanks Eric and Zach.  On my device I have followed your steps.  I am using a R12i so no sign-in is necessary.  With no internet connection, TMM still attempts to open a webview window and freezes.  

I have sent a screen recording and log files from both apps to Duncan-Parnell support as they work on the issue.

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?

Hi All,

I'll reach out to you directly @Neil Winn, and will update the group with any results. I have had some interaction with Support about this issue, so will try to close the loop.

Best regards,

Mark.

Thanks Eric.  I can rule out another receiver being the problem and provide some clarification.  When I open TMM I am unable to select a receiver because the app attempts to open an external browser (webview) right away and freezes.  Sometimes it is possible to close the webview and continue, but not consistent.

Thanks Eric and Zach.  On my device I have followed your steps.  I am using a R12i so no sign-in is necessary.  With no internet connection, TMM still attempts to open a webview window and freezes.  

I have sent a screen recording and log files from both apps to Duncan-Parnell support as they work on the issue.

Following what Zach said, you can try this to get out of the looping/crashing.

1. Go into your bluetooth setting and forget all Trimble GNSS devices
2. Uninstall Mobile Manager and Field maps
3. Reinstall moible manager and field maps
4. Connect to Trimble GNSS receiver via bluetooth
5. Run TMM, connect to Trimble GNSS and configure your GNSS Settings.  Leave running
6. Run Esri field maps, go into profile, and configure location provider and profile.https://www.youtube.com/watch?v=myTRdNGtG8c&list=PLUKFLYkxejVaHKQbbfnqvr-Ev0Xk_jw7g&index=12
7. If you still have issues make sure you get both esri and trimble log files and send to Duncan.

I'm working through Duncan-Parnell support on this issue and it is being reported to Trimble engineering, but it seemed reasonable to also post here to see if you are experiencing problems.  With the most recent update to Trimble Mobile Manager and ESRI Field Maps on Android, we have multiple users attempting to use the WebSocket connection (selecting Trimble Mobile Manager as the Provider in ESRI Field Maps) the screen flashes multiple times back/forth resulting in a crash of the TMM app.  As of this morning I cannot exactly replicate, but I feel like I'm seeing the root of the problem.  Trimble Mobile Manager now does a check for connectivity using the device browser before fully opening.  I expect this is some kind of authentication process.  What I can repeat now is to turn off connectivity (WiFi and cellular data) always results in the Trimble Mobile Manager app crashing on Android devices.  Sometimes it is possible to close the webview browser and use the TMM app for configuration, but not always.  If this is intentional, I find this almost as problematic as when Trimble briefly required a Trimble login to use Trimble Mobile Manager.  Our offline users will absolutely not be able to rely on it.  

App versions:  TMM 2025.23.12, ESRI Field Maps 25.3.1

Any thoughts from you out there?  Can anybody replicate?  Am I missing something?