I m using MVIKotlin 3 0 1 and the MVIKotlin Time Travel 3 0 kotlinlang #mvikotlin

Channels

100daysofkotlin

100daysofkotlin-2021

algolialibraries

android-architecture

android-databinding

androidgithubprojects

androidx-xprocessing

arrow-contributors

beepiz-libraries

cincinnati-user-group

codemash-precompiler

codingconventions

competitive-programming

competitivecoding

compose-android

compose-desktop

compose-ui-showcase

connect-audit-events

cscenter-course-2016

domain-driven-design

effective-kotlin

effectivekotlin

embedded-kotlin

event21-community-content

fb-internal-demo

fluid-libraries

framework-elide

getting-started

github-workflows-kt

graviton-browser

image-processing

intellij-plugins

intellij-tricks

introduce-yourself

java-to-kotlin-refactoring

jhipster-kotlin

jvm-ir-backend-feedback

k2-early-adopters

kotest-contributors

kotlin-by-example

kotlin-data-storage

kotlin-foundation

kotlin-in-action

kotlin-multiplatform-contest

kotlin-pakistan

kotlinforbeginners

kotlingforbeginners

kotlinprogrammers

kotlintest-devs

kotlinultimatechallenge

kotlinx-datetime

lambdaworld_cadiz

language-evolution

language-proposals

leedskotlinusergroup

library-development

machinelearningbawas

myndocs-oauth2-server

navigation-architecture-component

ohio-kotlin-users

pattern-matching

pocketgitclient

practical-functional-programming

prozis-android-backup

python-contributors

realworldkotlin

refactoring-to-kotlin

refreshversions

russian-kotlinasfirst

skia-wasm-interop-temp

sofl-user-group

spring-security

squarelibraries

stayhungrystayfoolish

strife-discord-lib

swagger-gradle-codegen

swiss-user-group

tricity-kotlin-user-group

Title

l

Laurence Muller

07/29/2022, 7:22 PM

I'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 PM

It's the first time I've seen this error. Maybe

adb kill-server

will help?

l

Laurence Muller

07/29/2022, 7:32 PM

sadly it doesnt

It'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 PM

There 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 PM

ah

found the offender

if 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 PM

What a coincidence! I have chosen the port number completely at random. 😁

l

Laurence Muller

07/29/2022, 7:53 PM

haha yeah, although I dont know how common it is for mobile devs use redis 😅

2 Views

#mvikotlin Join Slack