I'm using MVIKotlin 3.0.1 and the MVIKotlin Time T...
# mvikotlinl
Laurence Muller
07/29/2022, 7:22 PMI'm using MVIKotlin 3.0.1 and the MVIKotlin Time Travel 3.0.0 plugin in Android Studio Electric Eel Canary3.
For some reason when I tap the connect button I get this screen:
Is there a known fix for this? I only run 1 Android studio instance
(and I'm using the Emulator)
a
Arkadii Ivanov
07/29/2022, 7:31 PMIt's the first time I've seen this error. Maybe
adb kill-serverl
Laurence Muller
07/29/2022, 7:32 PMsadly it doesnt
Laurence Muller
07/29/2022, 7:34 PMIt's also interesting that the 2nd time you click the connect button, it just doesn't show any message.
a
Arkadii Ivanov
07/29/2022, 7:35 PMThere is a similar question on SOF - https://stackoverflow.com/questions/34850734/adb-cannot-bind-tcp5037
The time travel feature uses port 6379 by default.
You can try to find the process that uses the port and kill it. Alternatively, you can configure another port for time travel - in both the TimeTravelServer via its constructor and in the plugin settings.
l
Laurence Muller
07/29/2022, 7:38 PMah
Laurence Muller
07/29/2022, 7:41 PMfound the offender
Laurence Muller
07/29/2022, 7:41 PMif you have redis cli installed via homebrew, there is a server running on port 6379:
https://redis.io/docs/manual/cli/
a
Arkadii Ivanov
07/29/2022, 7:52 PMWhat a coincidence! I have chosen the port number completely at random. 😁
l
Laurence Muller
07/29/2022, 7:53 PMhaha yeah, although I dont know how common it is for mobile devs use redis 😅
5 Views