Installed FDK v9.4.0 and now seeing 'undefined' after 'fdk run'

App Platform
, , , ,
1

I just updated my FDK version to the latest today - v9.4.0. I think I was on 9.3.x previously.

Before that, I was able to start up my app without any issues. Now, after the upgrade, I’m running into all sorts of issues.

  1. When I first try to rerun my app, it starts but when I try to test it at localhost:10001/web/test, I see the following error in console:
To simulate product, app setup, and external events, visit - http://localhost:10001/web/test

Populating test data with events found in the app

Error: ENOENT: no such file or directory, mkdir '/tmp/4...
  1. So then I tried to reinstall NPM completely as administrator in windows CMD:
  • nvm uninstall 18.19.0
  • nvm install 18.19.0
  • nvm use 18.19.0
  1. Then I tried to rerun my app with fdk run. This time, I didn’t get the ENOENT error but instead just undefined when running my app without any other errors. My app is completely not starting now.

How can I fix this? Is this all because of the upgrade? I didn’t see the error previously.

Thanks in advance!

2

I tried to avoid using rm -rf .fdk but that seems to do the trick. It’s starting normally now.

3

Can you please upgrade the FDK to v9.4.1 and try out ?

4

Thanks @Chandiramouli_Ramach, I’ll attempt to upgrade to v9.4.1 later. But in general, when upgrading the FDK version, do we need to remove the .fdk files? I wonder if I should do this everytime so that I don’t run into these sort of issues.

Thanks!