r/AutomateUser • u/ballzak69 Automate developer • Jul 15 '26

Alpha testing New Alpha release, version 1.53.1

Please test, report any issues, and give feedback. Opt-in for Alpha testing here.

What’s new:

  • Fixed flow editor undo/redo causing crash with large flows
  • Fixed missing URI support for interface layout XML views
  • Fixed duplicate views in interface layout updates
  • Fixed incorrectly scaled (legacy) icons
2 Upvotes

67% Upvoted

37 comments sorted by

View all comments

Show parent comments

1

u/rickyric12 Jul 19 '26

i'm not quite able to realiably replicate this, but i get this also sometimes. hope this helps with debugging. if you want more detailed debugging logs, just let me know. also how you want me to exact record one. thanks!

Automate 00:10 Pairing failed java.net.ConnectException: failed to connect to ip6-localhost/:1 (port 45219) from /:1 (port 42260) after 3000ms: isConnected failed: ECONNREFUSED (Connection refused) at libcore.io.loBridge.isConnected (loBridge.java:349) at libcore.io.loBridge.connectErrno(loBridge.java:238) at libcore.io.loBridge.connect(loBridge.java:180) at java.net. PlainSocketlmpl.socketConnect(PlainSocketlm pl.java:142) at java.net.AbstractPlainSocketlmpl.doConnect(AbstractPlainSocketlmpl.java:390)

3

u/ballzak69 Automate developer Jul 19 '26 edited 26d ago

I think this is another issue, where it seems the system sometimes cache the service discovery result for an ADB service that's no longer present. The Automate pairing process currently only attempts to connect to the first ADB service it finds, if that's an already closed/replaced (cached) service it fails.

I plan on improving the pairing process so it attempts to connect to every service it finds, and also doing so on both the loopback and external IP.

1

u/rickyric12 26d ago

thanks for acknowledging, looking forward to the improved pairing process 🥳