messager | convenient way to handle messages | Chat library

1. It sounds strange, but the fix is adding work manager dependency 2.7.0+ : implementation "androidx.work:work-runtime:2.7.0"

2. You have to update dependencies that should support Android 12 braking changes (I had to update some third parties). Check that on github and documentation pages

3. Also, some libraries are using permission that is required for Android 12. Please check the documentation for this permission

4. Also, check google's issue tracker for google's library-specific issues related to Android 12

Maybe I missed something, but all this helped me to migrate. Good luck :)

You need to return the same subscriber object to start and stop it:

check some google examples here.

here is a sketch (adapt for your class):

Depending on your IDE, you might have to stop the java application running.

Eclipse: Top bar -> Debugging/Run tools -> Red Square (This might have a number showing how many instances are running at the same time)

Intellij:

How to prevent multiple bots running at the same time (Intellij Only):

• Disable the "Allow Multiple Instances" in your run options.

You don't have to get the GuildMember object, you can just ban the user by id from GuildMemberManager which can be found from the reaction object via reaction.message.guild.members

So instead of using user.ban() you can use

When requiring the event file, you never defined client therefore when you call client.channels in the event handler, it doesn't actually know what client is.

To fix this issue, when executing the function, define client before the args.
Example:

You could do this way:

Rabbit starts resend last not processed message without any delay

That's how redelivery works: it re-push the same message again and again, until you ack it manually or drop altogether. There is no delay in between redeliveries just because an new message is not pulled from the queue until something is done with this one.

I can't define infinity attempt amount in options maxAttempts

Have you tried an Integer.MAX_VALUE? Pretty decent number of attempts.

The other way is to use a Delayed Exchange: https://docs.spring.io/spring-amqp/docs/current/reference/html/#delayed-message-exchange.

You can configure that retry with a RepublishMessageRecoverer to publish into a your original queue back after some attempts are exhausted: https://docs.spring.io/spring-amqp/docs/current/reference/html/#async-listeners

You can specify the generic argument by type annotating dtoResult

test device is 'Mediapad M5 lite 10' EMUI 8.0.0

Due to system limitations, Apps on devices whose EMUI version is earlier than 10.0 cannot be enabled in the background, and the data Message depends on the EMUI version, so you are advised to use whose emui is greater than 10.0 phone to test.