Apify.getInput() returns null when apify token is set in env on local

[oodoow]

Describe the bug
when working on local with apify token in enviroment variables in launch.json in VS Code like this:
"env": {
"APIFY_TOKEN": "........"
}

then await Apify.getInput() returns null

Expected behavior
await Apify.getInput() returns input from \apify_storage\key_value_stores\default\INPUT.json

System information:

• OS: "Windows 10"
• Node.js version : "v16.9.1"
• Apify SDK version: "^2.0.7"

[B4nan]

Sounds like something with your vscode, not really a bug in the Apify SDK. Apparently the env vars are not present on runtime, we can't do anything about that.

edit: seeing your conversation on discord now, I guess I misunderstood (would be less confusing if you dont talk about vscode when describing reproductions...).

[adiled]

Explicitly setting env var APIFY_LOCAL_STORAGE_DIR to the directory worked for me, the default may not be acting up, happens.

[oodoow]

Thanks, with APIFY_LOCAL_STORAGE_DIR it works as expected. Still I think this should be fixed.

[B4nan]

As said above, if you provide just the token, it should work with the platform, not with your local storage. In other words, this behaves as expected, just got this confirmed.

[adiled]

Yes, the frizz between bootstrapping local env vs platform env may be causing this and probably other gotchas, and having gone through a trial today, some of it can be streamlined via doc touchups.

[oodoow]

So I always need to provide APIFY_LOCAL_STORAGE_DIR as well with the token to make it work on local otherwise it is apparently using default storage on the platform. Did not know that, thanks a lot.

[mnmkng]

I suggest this https://sdk.apify.com/docs/guides/environment-variables#combinations-of-apify_local_storage_dir-and-apify_token and this https://sdk.apify.com/docs/guides/result-storage