Its in "C:\Documents and Settings\root\Local Settings\Application Data\MonoDevelop-3.0\Logs\"
Here is what I've found: ERROR [2012-08-13 09:50:08Z]: Error in device tracker System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult) at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace --- at MonoDevelop.MonoDroid.AdbClient.EndReadResponseWithLength(IAsyncResult ar) at MonoDevelop.MonoDroid.AdbOperation.OnGotResponseWithLength(IAsyncResult ar) ERROR [2012-08-13 09:50:35Z]: Error in device tracker System.IO.IOException: Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request. ---> System.Net.Sockets.SocketException: The I/O operation has been ted because of either a thread exit or an application request at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult) at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) at MonoDevelop.MonoDroid.AdbClient.EndGetStatus(IAsyncResult ar) at MonoDevelop.MonoDroid.AdbOperation.OnGotStatus(IAsyncResult ar) ERROR [2012-08-13 09:51:42Z]: Error in device tracker System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:5037 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Connect(EndPoint remoteEP) at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP) at System.Net.Sockets.TcpClient.Connect(IPAddress address, Int32 port) at MonoDevelop.MonoDroid.AdbClient.Connect() at MonoDevelop.MonoDroid.AdbOperation.BeginConnect() ERROR [2012-08-13 09:53:57Z]: Failed to install package ERROR [2012-08-13 09:56:51Z]: Failed to install package ERROR [2012-08-13 10:02:10Z]: Failed to install package Last three lines are the only indication of a failure. Is there any possibility to increase logging verbosity? BTW, another "Error in device tracker" log indicates another one issue I often see: MD is very unstable in detecting running simulator. It can detect it sometimes after MD restart, sometimes after adb restart. All this could be related to the fact, that MD runs in virtual machine, but simulator runs on host ubuntu and adb connection is done via ssh port forwarding. Let me know if I can do any more testing, because now it makes debugging very annoying. Igor On Tue, Aug 14, 2012 at 12:26 AM, Jonathan Pryor <j...@xamarin.com> wrote: > On Aug 13, 2012, at 2:16 AM, Igor Russkih <iruss...@gmail.com> wrote: > > I'm getting in trouble trying to Run/Debug application from the MD > (3.0.3). > > > > It basically says: > > > > Installing 'xxx-Signed' > > pkg: /data/local/tmp/xxx-Signed.apk > > > > 579 KB/s (2848292 bytes in 4.796s) > > > > Failed to install package > > > > > > But logcat shows that package was installed! > > It's a sign that we need more information. :-) > > If you're on OS X, please provide the contents of your > $HOME/Library/Logs/MonoDevelop-3.0/AndroidTools-DATE.log file. Something > "weird" is going on there... > > Windows should have a similar log file somewhere, but I don't know where... > > - Jon > > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
