Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin does not working in some orgs #16

Open
carlosabella opened this issue Mar 28, 2017 · 4 comments
Open

Plugin does not working in some orgs #16

carlosabella opened this issue Mar 28, 2017 · 4 comments

Comments

@carlosabella
Copy link

Hi there,

I have some orgs working perfectly with the plugin but I have one that I am getting this error:

[Ljava.lang.StackTraceElement;@3ef42a

Could you please help me?

Thanks!

@ChuckJonas
Copy link
Owner

ChuckJonas commented Mar 28, 2017

is that the full error? What actions are you taking when the error is thrown? What OS are you running? What type of ORG are you trying to connect to?

@jamessimone
Copy link

jamessimone commented Jun 16, 2017

@ChuckJonas because my apex completion / go to definition was still not working following your latest release, I spent some time monitoring the VS code output for your extension. The thing that was killing me? While my two team members had never had the code completion working correctly, I had - and it had made developing a breeze. I wanted that breeze back.

I am wondering if the above stack trace is at all similar to the one that I was seeing - a persistent null pointer exception being thrown by tooling-force. It turns out that the parser was throwing an exception for a class that we had added perhaps a month and a half ago with a method named "set." Now that I have updated that method's name, auto-complete is once more working like a charm. I would advise anybody having an issue with the code completion to take a stroll through the output for Apex Autocomplete and see if any of the classes in your org are having an issue being scanned.

I made neowit/tooling-force.com#28

@ChuckJonas
Copy link
Owner

@jamessimone good work figuring that one out (crazy bug). Unfortunately, this extension has started to get more unreliable for me as well and I haven't had the time to really dig into it

@jamessimone
Copy link

@ChuckJonas I wouldn't worry about it too much. We're all busy. The plugin works fine on my work computer and intermittently on my home PC ... perhaps I'll get the chance this weekend to investigate what the story is with my own desktop. Your contributions are more than appreciated, regardless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants