NPE when trying to retrieve metadata

Issue #948 resolved
Noe Tamez created an issue

Another developer has created a new apex class. When trying to pull in this new apex class with retrieve metadata, I'm getting the following error message:

Error: Unhandled exception: java.lang.NullPointerException.

I've tried going to connections and rebuilding cache. I've tried regenerating the offline table. I can see the new files on server only listing, I just can't pull them in. Originally encountered problem in version 2.0.0.8 and updated to 2.0.1.5 and see same issue.

OS: OSX 10.12.6 Webstorm version 2017.3.5

Comments (9)

  1. Scott Wells repo owner

    Hi, Noe. Sorry for the issue. I can see the line of code where the NPE is occurring but can't see exactly why things are ending up null at that point. Do you mind setting up debug logging for metadata retrieval as documented here:

    http://www.illuminatedcloud.com/support/debuglogging

    then reproducing the issue and sending the new log? Hopefully that will provide more insight into where the null is coming into play. Ideally I'll be able to provide feedback on how to get rid of the null without the need for another build, but if it does require a new build I can create a quickfix for you here in advance of the next release.

  2. Noe Tamez reporter

    Hi Scott. Thanks for the fast response. Here are all the new logs generated with the metadata retrieval logging. Thanks!

  3. Scott Wells repo owner

    Thanks. Unfortunately the log didn't provide the answer so I'm spinning a new build for you that should resolve it and provide some root cause diagnostics about why it was failing before. I'll attach it here very shortly with instructions on how to install it.

  4. Scott Wells repo owner

    Okay, download this build and install it using Settings>Plugins>Install plugin from disk. After the IDE restarts with the new build, please repeat the retrieval operation and let me know whether it succeeds or not. If you don't mind, please attach new logs either way so that I can look for the root cause of the issue and understand it better. Thanks!

  5. Scott Wells repo owner

    Wonderful! And I think I see the underlying issue. It's relatively benign, but I'll look at a full fix in the next build. For now plan to stay on that build until the next official one is released at which point it'll be safe to upgrade.

  6. Scott Wells repo owner

    The fix should have been included in the latest build(s). Please let me know if you still see this after updating.

  7. Log in to comment