This message was deleted.
# announcements
s
This message was deleted.
n
dunno, that should work. you're sure the
apply
is in fact the Kotlin stdlib one?
also it may be possible that too much time has passed between when the client is initialized and publish is called, so the connection just times out. a
client.assertConnected
-type call inside the publish method is probably a good idea regardless
p
Yeah, it is. Also tried it with
.also { it.connect() }
which also didn't work.
I just found the error: I created a second mqtt client in my test to fetch the message from the broker. That client had the exact same id (can't be seen here because its under /*configuration*/). Guess its really time to stop working today. Anyway, thanks!
🎉 1
n
my local time is 9:44AM. wish I could say the same 😜
p
fyi, I'll delete the question + thread, since it has no real usage for anyone else.
well, last day of the week (I guess?), so should be reasonable!