-
Notifications
You must be signed in to change notification settings - Fork 101
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
PingWorker not work #502
Comments
@hannesa2 Changing the keepAlive time to a very short time such as 10 seconds will reproduce this problem very well. My solution is to modify "ExistingWorkPolicy. REPLACE" as "ExistingWorkPolicy. KEEP". I wonder if this is a good solution? Thanks! |
log: 2023-09-19 10:54:24.775 16014-16315 ACLog D MQTT Ping AlarmPingSender start |
Please can you demonstrate your change as a pull request ? Here you have something to read https://issuetracker.google.com/issues/122578012?pli=1 eg.
I'm not sure if it's just a "(Intended Behavior" |
since 4.1 i have noticed this as well but it makes it so that the connection has more losses then i had with 3.5.1 2023-09-29 09:06:22.148 28065-28106 WM-WorkerWrapper com.qbus.ubie I Work [ id=3e113b43-0d60-4a35-8d38-2e20860e8a54, tags={ info.mqtt.android.service.ping.PingWorker } ] was cancelled |
It's a bug for PingWorker. comment |
I was testing the latest version and still facing this issue. As a sample I just ran |
Hello, I'm having the same issue using version 4.0 on Samsung XCover with Android 13 |
Hi, we are having the same issue on version 4.2.4 on Samsung Galaxy tab with Android 11 and on a Pixel 6A with Android 14. |
hello |
This is too easy.
|
|
Cancellation does not mean that it's automatic an error. It's a cancel ! Btw, please consider to move to |
I have the same issue on multiple test devices (new and old). I'm currently testing on a Galaxy S10, Android version 12 and MQTT version 4.2.4. Error message below. Any progress with this issue? BTW, great work supporting this library. 12:39:07.323 I Work [ id=8beff531-e410-4953-8d28-d189953300fc, tags={ info.mqtt.android.service.ping.PingWorker } ] was cancelled |
The issue is still present in 4.3.beta5. Without any interaction. Just opened a connection and did a subscribe.
I cannot currently see that it is causing any problems in use. It just floods the logs. Cheers & thanks for this fork. |
Work [ id=42e1814b-15be-45aa-9fba-293602b236b0, tags={ info.mqtt.android.service.ping.PingWorker } ] was cancelled
java.util.concurrent.CancellationException: Task was cancelled.
at androidx.work.impl.utils.futures.AbstractFuture.cancellationExceptionWithCause(AbstractFuture.java:1184)
at androidx.work.impl.utils.futures.AbstractFuture.getDoneValue(AbstractFuture.java:514)
at androidx.work.impl.utils.futures.AbstractFuture.get(AbstractFuture.java:475)
at androidx.work.impl.WorkerWrapper$2.run(WorkerWrapper.java:317)
at androidx.work.impl.utils.SerialExecutorImpl$Task.run(SerialExecutorImpl.java:96)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
The text was updated successfully, but these errors were encountered: