Sst v3 {"body":"sst dev is not running"}

1

Trying to get up and running with v3 for the first time. But I don’t seem to get anything hitting my lambda functions, they won’t log anything to the console and so on. So I set up a very simple one that responds with {statusCode: 200, body: "Connected"}. When I run under npx sst dev and try to GET it, all I get is:

{"body":"sst dev is not running"}

If I disable dev mode as follows:

        const httpApi = new sst.aws.ApiGatewayV2("MyApi");
        httpApi.route("GET /", {
            handler: "packages/functions/src/connect.main",
            dev: false
        });

It does work!

Wondering if its an IAM permissions thing, but the IAM user used for deployment has full AdministratorAcces set up on AWS.

Why is the live function feature not working?

1 Like
2

Seems to be a problem with 3.3.x which changed the bridge to appsync.

Works fine on 3.2.76.

I noticed there was this issue created today Auth component does not work in dev mode (Live) · Issue #5034 · sst/sst · GitHub, and also a few people having this same problem on discourse, so its not just me.

Rollback to 3.2.76 will work around the problem until something can be fixed on 3.3.x.