Thank you for creating a great package, I’m looking forward to using it! I’m sure this is due to a misunderstanding on my part, but I’ve been unable to get it working in an app deployed using Vapor. No connection IDs or channels are being written to the DynamoDB table.
I can see that Handler::subscribe() is called from the VaporHandle command, which is invoked via an API Gateway event. But for an API Gateway event to be fired, a message needs to be sent to the API, which doesn’t happen unless the command is invoked. Am I missing a point at which Handler::handleMessage() is being called without the VaporHandle command having to be invoked beforehand?
Thank you for creating a great package, I’m looking forward to using it! I’m sure this is due to a misunderstanding on my part, but I’ve been unable to get it working in an app deployed using Vapor. No connection IDs or channels are being written to the DynamoDB table.
I can see that
Handler::subscribe()
is called from the VaporHandle command, which is invoked via an API Gateway event. But for an API Gateway event to be fired, a message needs to be sent to the API, which doesn’t happen unless the command is invoked. Am I missing a point at whichHandler::handleMessage()
is being called without the VaporHandle command having to be invoked beforehand?