Mobile Device Manager Cannot Be launched from Studio

News Knowledge Base
, , ,
1

Resolution when the Mobile Device Manager from a Studio project opens with the Mobile Testing Template.

When using the template for Mobile Testing from Studio, and launching Mobile Device Manager, the expected configuration windows does not appear. No error message is displayed.

In eventviewer Application logs, the following entries may be present:

Faulting application name: UiPath.MobileAutomation.DeviceInteraction.exe, version: 22.10.1.0, time stamp: 0x63459d34

Faulting module name: MSVCR120_CLR0400.dll, version: 12.0.52519.0, time stamp: 0x5849f912

Exception code: 0xc00000fd

Fault offset: 0x0007e22c

Faulting process id: 0x1ed4

Faulting application start time: 0x01d8edf03f38c993

Faulting application path: C:\Users\xxxxxx\.nuget\packages\uipath.mobileautomation.activities\22.10.1\build\UiPath.MobileAutomation.DeviceInteraction.exe

Faulting module path: C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll

Report Id: 4e112112-d800-482b-9adf-f588761afe71

Faulting package full name:

Faulting package-relative application ID:

Faulting application name: UiPath.MobileAutomation.DeviceInteraction.exe, version: 22.10.1.0, time stamp: 0x63459d34

Faulting module name: clr.dll, version: 4.7.3946.0, time stamp: 0x6247236a

Exception code: 0xc00000fd

Fault offset: 0x00019cf4

Faulting process id: 0xf84

Faulting application start time: 0x01d8ede239c10b15

Faulting application path: C:\Users\xxxxxxx\.nuget\packages\uipath.mobileautomation.activities\22.10.1\build\UiPath.MobileAutomation.DeviceInteraction.exe

Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

Report Id: 07cd59c9-fbae-4917-a092-aa7c4ea3d79d

Faulting package full name:

Faulting package-relative application ID:

Root Cause: The behavior happens if the .NetFramework version is 4.6.2 or lower.


Resolution:

  • The solution is to upgrade .NetFramework to a version higher than 4.6.2.