{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 等我变得足够好 的问题《Xamarin.UITest DeviceAgentException: Failed to ins》','https://www.manongdao.com/q-539368.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
How do I solve this error that occurs when running Xamarin.UITest on an iOS Device?
It happens on both the iOS Simulator and a physical iOS device.
SetUp : Calabash.XDB.Core.Exceptions.DeviceAgentException : Failed to install DeviceAgent: ApplicationName='/var/folders/5m/3712cp7j2k928k6z3fgszfyw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/93c12f73043a2d14eea9d417ab080eb4/bin/iOSDeviceManager', CommandLine='install -d fcbb5006c892e39f1f675a3f6804ce3688c3b8d1 -a /var/folders/5m/3712cp7j2k928k6z3fgszfyw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/93c12f73043a2d14eea9d417ab080eb4/ipa/DeviceAgent-Runner.app', CurrentDirectory='', Native error= Cannot find the specified file
----> System.ComponentModel.Win32Exception : ApplicationName='/var/folders/5m/3712cp7j2k928k6z3fgszfyw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/93c12f73043a2d14eea9d417ab080eb4/bin/iOSDeviceManager', CommandLine='install -d fcbb5006c892e39f1f675a3f6804ce3688c3b8d1 -a /var/folders/5m/3712cp7j2k928k6z3fgszfyw0000gp/T/xdb/DeviceAgent.iOS.Dependencies/93c12f73043a2d14eea9d417ab080eb4/ipa/DeviceAgent-Runner.app', CurrentDirectory='', Native error= Cannot find the specified file
I had this issue happen to me before as well, it was caused by a corrupt file in that folder. Navigate to that directory: '/var/folders/5m/3712cp7j2k928k6z3fgszfyw0000gp/T/' and delete the folder 'xdb'. This should resolve the issue.
FYI: The UITest team is aware of this and they have a fix in version 2.0.1.