authtoken | Auth token from HTTP request headers | Authentication library

It appears that the option you'll want to use to target the WS connect/disconnect event is connectionCallback (see full list of WebSocketLink options here).

Take a look at lines 620-635 of the WebSocketLink source and you can see that the provided connectionCallback is called both for GQL_CONNECTION_ERROR and GQL_CONNECTION_ACK received message types. Therefore, you should be able to target both events using this callback.

I haven't used Apollo's WebSocketLink yet myself, so I am unable to confirm that this will work fully as expected. Additionally, the behavior to fetch all missing chat messages upon reconnect is something you may need to build yourself as it doesn't appear to be part of the default reconnect behavior (will depend on server implementation; see Apollo Server docs). Conversely, it does appear that WebSocketLink will forward all unsent messages to the server upon reconnect by default.

The problem lies in 3rd party section of INSTALLED APPS.

'alluth.socialaccount'

it is a typo, it should be

'allauth.socialaccount',, pay attention to alluth -> allauth

The error seems to be in the webpack package. This answer should help: Django Webpack Loader: "Assets" KeyError?

Pass completion handler of main function and status code to fetchAllUsers and call it there after it's own completion handler

completionHandler(response.response!.statusCode) was being executed before self.fetchAllUsers closure because it was waiting for api response to complete. completionHandler(response.response!.statusCode) was destroying self.fetchAllUsers closure before it is executed, so I called completionHandler(response.response!.statusCode) inside self.fetchAllUsers after it's closure

I'm new to javascript and typescript and frontend frameworks .

After many attempts for this problem in stackoverflow an also reading the docs ,I found nothing so i decided to do more debugging and i understand Vuex actions only take one arguments so another arguments values becomes undefined

You're using assign for reference/pointer types: @property retain, assign, copy, nonatomic in Objective-C

They should probably be declared copy, because this is a kind of value object, I think.

No exceptions were caught because no exceptions were thrown. Throwing/catching exceptions for control flow is not common in Objective-C

You don't need to write explicit setter functions for @properties

You should prefer to use BOOL type instead of Boolean, with values of YES/NO instead of true/false.

You should return instancetype not id from init, at least in reasonably modern Objective C

Consider making an initialiser that takes all the properties (initWithRoomName:clientID:) and make them read only once set

You don't need to declare -(id) init in your header since it gets that from NSObject

Thanks @so-cal-cheesehead you are correct the API was faulty

You can try this:

1. Add the X-Forwarded-For to the "HTTP Request Headers" (goto the API-Gateway configuration -> Resources -> Method Request).
2. Add a Template with Content-Type: application/json (Resources -> Integration Request -> "Mapping Templates")
3. Add a Mapping to the template

The first thing to note is that an instance of Exception which is not also an instance of RuntimeException is a checked exception. Thus, the only way the for a method to throw a generic Exception is for the method signature to contain "throws Exception" or "throws Throwable".

So.. why are you getting this error? You are stubbing the postForEntity method which throws RestClientException, and Exception is not an instance of RestClientException. Thus, your stubbing is invalid.

If you want to stub the method such that the catch block for the generic case is entered, you will need to throw a RuntimeException, which is unchecked, and therefore not subject to the "throws" restriction.

That said, it would be probably be wiser to simply catch only the RestClientException in the original method. If there is some RuntimeException you want to catch, then you would hopefully already be aware of what that is and catch it specifically.