The sdk retries in 403s leading to huge billings.

[emorell96]

Hi,

I thought this issue was already solved but apparently not. In testing I forced the SDK to use the wrong auth key to see what the retry behavior would be and to my surprise you are retrying on all 403s sent by Pubnub creating a huge bill if not careful:

Warning: DateTime: 12/07/2021 01:22:03, Inside SendRequestAndGetJsonResponseHttpClient
Warning: DateTime 12/07/2021 01:22:03 GetTimeWithHttpClient Resp OK
Warning: DateTime 12/07/2021 01:22:03, JSON= {"message":"Forbidden","payload":{"channels":["chanel"]},"error":true,"service":"Access Manager","status":403}
Warning: DateTime 12/07/2021 01:22:03, EXPONENTIAL timerInterval = 7
Warning: DateTime 12/07/2021 01:22:10 MultiplexExceptionHandlerTimerCallback
Warning: DateTime 12/07/2021 01:22:10 MultiplexInternalCallback timetoken = 0
Warning: DateTime 12/07/2021 01:22:10 CheckSocketConnect Entered
Warning: DateTime 12/07/2021 01:22:10 GetTimeWithHttpClient Resp OK
Warning: DateTime 12/07/2021 01:22:10, JSON= {"message":"Forbidden","payload":{"channels":["chanel"]},"error":true,"service":"Access Manager","status":403}
Warning: DateTime 12/07/2021 01:22:10, EXPONENTIAL timerInterval = 15

This is part of the log, I've removed personal information and channel names since I don't want that information on github. But as you can see it keeps retrying on 403s which makes no sense. How can an internal retry logic solve a 403 without being able to acquire keys? This should be left up to the developer.

I thought this was a known issue. I had a support call with Craig Connover when he was helping us build the app, and later with his successor. How come this hasn't been fixed?