question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Setting messageSendingQueueSupplier after construction results in messages not being sent

See original GitHub issue

When setting the messageSendingQueueSupplier on a constructed client, messages that are not sent as immediate messages, won’t get sent at all. This includes, for example, join messages. I can reproduce this using something like this:

val builtClient = Client.builder().nick(twitchSettings.appUsername)
    .server().host(TWITCH_SERVER).port(TWITCH_PORT).password(serverPassword).secure(true).then()
            .build()
TwitchSupport.addSupport(builtClient, false)

and later:

    @Handler
    fun onConnected(connectedEvent: ClientConnectionEstablishedEvent) {
        twitchSettings.initialChannels.map { asChannelName(it) }.forEach {
            connectedEvent.client.addChannel(it)
        }
    }

CAP, PING, NICK etc. messages will get sent, but the JOIN messages, or other non-immediate messages, never.

I doubt this is limited to just twitch, but the built-in twitch support requires an already created client. If instead I apply the support manually, with the only difference being providing the queue supplier in the builder, the messages get sent.

I tried debugging the issue, but it seemed like the sending queue (where the joins were) was properly processing the items yet for some reason they never ended up being written to the channel. I might be reading it wrong though.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mbaxcommented, Jan 13, 2019

Resolved in 5.0.1 which is released. I’ve learned a valuable lesson about testing before and after merging changes.

0reactions
kumpelblase2commented, Jan 13, 2019

From my little testing this seems to fix it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

If you have an issue with Messages or FaceTime after setting ...
After setting up your iPhone, you might experience one or more of the following issues: You can't receive iMessages or FaceTime calls.
Read more >
Fix problems sending, receiving or connecting to Messages
If you can't send or receive messages, or have trouble connecting to Messages on web, try the following suggestions below. Fix problems sending...
Read more >
Is iMessage not working? Here's how to fix it on your iPhone ...
If iMessage is switched on and there is no message about activation, check that your phone is set up correctly to receive iMessages:...
Read more >
Why Is My iPhone Not Sending Messages? How to Troubleshoot
Check in your iPhone's Settings app that various messaging options are turned on so that your phone can dispatch texts if iMessage fails....
Read more >
Apple Just Improved Messaging on Your iPhone with 26 New ...
After five edits or 15 minutes, the option will disappear from the quick actions ... Taking back a message you sent is another...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found