Jhonathan Ballesteros
Results
3
comments of
Jhonathan Ballesteros
Same here, only happens if you upgrade to version `3.0.0`, tried downgrading to `2.4.3` and everything was working again with the correct invoker.
I have the same problem. The function deploys and works correctly though, but it's annoying to have this message all the time.
For those of you having problems with the implementation on AWS Lambda: The problem is most likely the difference between the runtime you are using to build your deployment package...