Error During Serverless App Execution (FDK 9.4.0) – ENOENT mkdir Issue

App Platform
, , ,
1

Hi Support,

We are encountering the following error when running a serverless app with the onAppInstall event:
Error: ENOENT: no such file or directory, mkdir ‘/tmp/42eca06e-5059-40cd-b584-6563345ebed1’.

We are using FDK version 9.4.0. I’ve attached a screenshot for your reference. Your prompt assistance on this issue would be greatly appreciated.

image
image1920×1020 106 KB

Thanks,
Claret Ivin

2

Hi @Claret_Ivin,

Are you using the new Object store feature and storing and retrieving some files?
If yes, could you please share the code to reproduce the issue at our end?

If you want to reset to troubleshoot the issue, can you delete the “files” folder under /.fdk folder in the app root folder and see if the issue resolves?

Note that this action will delete some local configurations and files stored.

3

Hi Raviraj,

I’m not using the object store feature.

I also tried deleting the files folder under /.fdk, but I’m still encountering the same issue. I’ve shared the Drive link to the code in the chat for your reference.

Thanks,
Claret Ivin

4

I have currently the same issue, every time I try to simulate the onAppInstall event I get the same error message since updating to FDK 9.4.0. I have also deleted the .fdk folder already but that didn’t help.

5

@Claret_Ivin, @chrism, Our team has recognised a path issue that occurs in Windows OS when using the Object Store feature. What you face could be relevant.
I will confirm with our team.

If it’s the same issue, we are working on the fix and will roll out the fix soon.

6

Hi Raviraj,

Thank you for your quick response. We are currently developing an app, and this issue is preventing us from moving forward. We kindly request you to help resolve this as soon as possible so we can proceed without delays.

Thanks,
Claret Ivin

1 Like
7

Hi @Claret_Ivin and @chrism,

Our team has fixed this issue. Please update the FDK to v9.4.1 to get the fix for you.

Thanks!

8

Hello @Raviraj, I can confirm that it works for me now after updating FDK. Thanks for the quick bugfix.

1 Like
9

This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.