Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with doNextOperation() of ConnectionManager not leading into signalEndOfOperation() #24

Open
JTerminator opened this issue Nov 11, 2024 · 0 comments

Comments

@JTerminator
Copy link

Hi, first of: thank you so much for this project and guide, as someone without any prior kotlin/android experience this project helped me out sooooo much. I would have had to put in so many more hours to get my project done.

So, I was using the ConnectionManager.kt in my project, and had a bunch of trouble with operations not being performed. It took me some time, but I traced back the issue to the fact, that in doNextOperation() the MtuRequest operation did not lead to signalEndOfOperation(). After adding in the line myself, it strated working as expected.

I would imagine that this is only a problem, when queueing operations immediatly after changing the MTU, so it probably not afecting this app directly, but I wanted to let you know anyway. (Just in case someone else might also wanna borrow parts of your code) ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant