[BUG] client.ClearPresence(); dont work

[UrbanSide]

Describe the bug
A clear and concise description of what the bug is.
This code dont work,activity continues to hang for about a minute

                client.SetPresence(null);
                client.ClearPresence();

[RegorForgot]

I am also having the same issue

[UrbanSide]

I am also having the same issue

Forget it, the ticket has been open for almost a year now. Look for another library.

[Lachee]

wow rude, dont tell people to use other libraries within the help of this one.

Your issue is invalid anyways, please follow the issue templates next time. Dont know the bug, or what you are expecting.
"This code dont work" is not very descriptive. I am unable to reproduce this issue, so any help you can provide is more than welcomed.

I will help however, to get this finally ticked away.

• Starters, doing both SetPresence and ClearPresence here is redundant, as they both set it to null.
• ClearPresence works on my end, please provide code to replicate your issue.
• Ensure you are not later setting the presence elsewhere.
• Enable the logs and share them here so i can validate the code is actually sending the clear

[RegorForgot]

I am unable to reproduce this issue, so any help you can provide is more than welcomed.

Hi, sorry as I just saw these comments now 10 months later. If it is worth anything, I had kept using this library since I think it is quite a good one. The way that this bug had occured is the following:

1. Load a rich presence using this package
2. Start another rich presence (for example Spotify)
3. Deactivate the rich presence from this package
4. Deactivate the other rich rpesence
5. The rich presence from this package will "ghost" and keep staying on.

It's an edge case, definitely but some use cases, such as mine, had it more often.

In any case, I had also found that this wasn't even local to the rich presences from this package only! Even other rich presences, during the time, had ghosting issues. I think since the time that Discord had updated their rich presences, this issue has mostly subsided and I haven't noticed it happening with any presence (including attempting to force it).