Closed LeagueRaINi closed 3 years ago
Also, is there any special reason that SetPresence
gets inconsistently called inside/outside the thread safety locks?
Saw that while trying to think of a potential fix for the issue mentioned above
https://github.com/Lachee/discord-rpc-csharp/blob/6f94c2be7b1e3c69ad12b7bf2ab97955c2accf98/DiscordRPC/DiscordRpcClient.cs#L508-L544
This is currently being worked on
This should be fixed now.
Describe the bug When
SkipIdenticalPresence
is false the update presence methods likeUpdateLargeAsset()
,UpdateState()
... will always fail to send because they setCurrentPresence
, it then fails to pass the identical check inSetPresence
https://github.com/Lachee/discord-rpc-csharp/blob/6f94c2be7b1e3c69ad12b7bf2ab97955c2accf98/DiscordRPC/DiscordRpcClient.cs#L480-L481To Reproduce Steps to reproduce the behavior:
SkipIdenticalPresence
to falseUpdateLargeAsset()
,UpdateState()
...Expected behavior Updates
CurrentPresence
and queues the presence update without having to setSkipIdenticalPresence
to falseOther I also just noticed that at the end of
SetPresence
u do this https://github.com/Lachee/discord-rpc-csharp/blob/6f94c2be7b1e3c69ad12b7bf2ab97955c2accf98/DiscordRPC/DiscordRpcClient.cs#L486 which unnecessary clones ifSetPresence
got called withCurrentPresence
as argument as it is the case with the update presence methods https://github.com/Lachee/discord-rpc-csharp/blob/6f94c2be7b1e3c69ad12b7bf2ab97955c2accf98/DiscordRPC/DiscordRpcClient.cs#L495-L506