Technical Error getting Metadata

[peyenelson]

Anybody getting this error? Just started happening out of the blue as of yesterday (4.18.24).
Help!

[peyenelson]

This is the generated error info:

main.6818e34cc61932b9.js:1 Uncaught TypeError: Cannot read properties of null (reading 'fields') at Function.value (main.6818e34cc61932b9.js:1:5704679) at main.6818e34cc61932b9.js:1:5701778 at Array.map (<anonymous>) at main.6818e34cc61932b9.js:1:5701659 at f.invoke (polyfills.72b665462a35e4da.js:1:7652) at Object.onInvoke (main.6818e34cc61932b9.js:1:8862221) at f.invoke (polyfills.72b665462a35e4da.js:1:7592) at f.run (polyfills.72b665462a35e4da.js:1:2727) at l.value (main.6818e34cc61932b9.js:1:8862679) at i.value (main.6818e34cc61932b9.js:1:5701461)

  | value | @ | main.6818e34cc61932b9.js:1 -- | -- | -- | --   | (anonymous) | @ | main.6818e34cc61932b9.js:1   | (anonymous) | @ | main.6818e34cc61932b9.js:1   | f.invoke | @ | polyfills.72b665462a35e4da.js:1   | onInvoke | @ | main.6818e34cc61932b9.js:1   | f.invoke | @ | polyfills.72b665462a35e4da.js:1   | f.run | @ | polyfills.72b665462a35e4da.js:1   | value | @ | main.6818e34cc61932b9.js:1   | value | @ | main.6818e34cc61932b9.js:1   | (anonymous) | @ | main.6818e34cc61932b9.js:1   | emit | @ | node:events:517   | emit | @ | C:\Users\CSS\AppData…vParserStream.js:45   | endReadableNT | @ | node:internal/streams/readable:1368   | processTicksAndRejections | @ | node:internal/process/task_queues:82

[n-ellison]

Was there a response to this? I'm getting the same error.

[peyenelson]

sigh...none.
I have come to rely on the dataloader too much I think.
uggh.

[peyenelson]

I was able to get the App to work by rolling back Java to 8.04.01 and installing the newest version of the dataloader.

[hman-23]

Same issue. Happened exactly after updating Java to 8. I deleted both and reinstalled them, as well as going back to Java 7, no luck. If anyone has fixed it, it'd be gold to hear.

[hman-23]

https://github.com/bullhorn/dataloader-app/releases/tag/v2.11.3

I found the fix. They figured out the issue after the Java update and rolled out a new version with the fix.