0
votes

Connection to the layout renderer failed. This may be caused by misconfiguration of Java"

When i tried to run Xamarin and start developing app, opening layout files gives me the error:

> java.net.ConnectException: Connection timed out: connect  at
> java.net.DualStackPlainSocketImpl.connect0(Native Method)     at
> java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
>   at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>   at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>   at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>   at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)   at
> java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)    at
> java.net.Socket.connect(Socket.java:589)  at
> java.net.Socket.connect(Socket.java:538)  at
> java.net.Socket.<init>(Socket.java:434)   at
> java.net.Socket.<init>(Socket.java:211)   at
> mono.android.HostProcessConnection.Connect(HostProcessConnection.java:23)
>   at mono.android.AndroidDesignerHost.run(AndroidDesignerHost.java:54)
>   at mono.android.AndroidDesignerHost.main(AndroidDesignerHost.java:43)

JDK Path

xamarin android java misconfiguration connection exception

2
What's your question? - Donald Duck
xamarin android layout rendering problem. don't show layout designer. its give this exception. - AH Rasel
xamarin android java misconfiguration. but my JDK setup correctly. I also try using 32-bit JDK. it's also same problem - AH Rasel
@DonaldDuck i am already added a screnshot of my visual studio project - AH Rasel
@​AHRaselAhamed Please edit your question to include that information. I also recommend you read the help center and edit your question accordingly to get better answers. - Donald Duck

2 Answers

0
votes

Just Check if your JDK and your JRE are of the same Version if not that could be the reason for this problem

You can find your JRE in your JDK folder

0
votes

I fixed the problem. it was the problem with Android SDK. after the update, Android SDK to latest version problem was solved.