[Bug] Client tried to subscribe to deleted exit

Bugs & Features
1

I think some logic is broken around the exits. When you remove an exit you see the client send

{"id":31,"method":"call.core.char.XXX.ctrl.deleteExit","params":{"exitId":"YYY"}}

but after that the client will keep spamming

{"id":32,"method":"subscribe.core.exit.YYY.details"}

and getting access denied errors.

1 Like
2

Oh, exits too? Yes, there is a client bug behind that.
We have a similar issue when someone deletes a character.

It can both be dealt with on ResClient level, preventing subscription of deleted cached items. But it is also a bug in the app where it keeps listening to that deleted item even after deletion.

But thanks for making me aware! :slight_smile:

1 Like
3

I found the client bug.
I moved the report to a separate topic. Thanks again! :grin:

1 Like