When running lambda, chrome needs to recompiled with the same os distribution lambda uses.
This makes it problematic to run the jsreport.Local. It could maybe work, but it sounds to me like a bad idea even to try it.
I would probably instead run jsreport as extra lambda function. We have a tutorial for it here https://jsreport.net/learn/aws-lambda-serverless
And then invoke the extra reporting lambda function from your c# lambda function.
Have you considered this approach?
Hi @jan_blaha I had the same issue mentioned above.
I fixed the problem using jsreport.Binary@2.6.2-beta2 on Windows, but I need to fix the issue on OSX, do you have any estimated release date for @2.6.2-beta2 on OSX?
Thank you for the reply. This is most likely the issue we were facing.
We noticed it took a really long time to start the jsReport server manually so we moved the virtual machine to another host with less load and that solved the problem. So we figued it was some kind of timeout. It's good to know that the property exist and that we can adjust it if needed.
This issue ended up being resolved for a different reason that I can't quite explain why. By upgrading from version 2.2.6 of the .NET Core Hosting Bundle on the affected machine to version 2.2.7, we resolved this.