7

I'm working through the steps from Get Started with the ISV Customer Debugger and trying to get the Apex Debugger to set breakpoints for code from the managed package.

I've logged into the subscriber org from the LMA app where the originating user has the "View and Debug Managed Apex" system permission.

enter image description here
Dragging the debugging session details into Eclipse appears to have worked. It's worth observing that this process was extremely slow and it appears to lockup the originating browser processes while attempts are made to pull down all the orgs metadata. But it did eventually finish.

In Eclipse I went through the steps to Set Up a Debug Configuration. Again, this appeared to work as I got what appears to be a debugging session.

enter image description here

enter image description here

However, any attempt to set an actual breakpoint in Eclipse fails as the options are disabled.

Trying "Enable/Disable Breakpoint" results in an Information message.

Breakpoint options

The chosen operation is not enabled

The chosen operation is not enabled

After which that option is grayed out.

enter image description here

Playing with the Tooling API I can see ApexDebuggerSession records with the Status of Active.

How do I get a breakpoint on Apex from my managed package?

I'm using:

  • v4.6.3 of the Eclipse IDE
  • v38.0.0.20170110588 of the Force.com IDE Debugger plugin
  • v38.0.0.201701101558 of the Force.com IDE plugin

I've also got v39.6.0.v20170406-0039 of the Force.com IDE (Pilot) plugin

Improve this question
10
  • Is there something showing up in the Eclipse .log file?
    – Gunnar
    Commented May 10, 2017 at 11:16
  • @Gunnar I was monitoring ...\workspace\.metadata\.plugins\com.salesforce.ide.core\force-ide.log. There were a number of Metadata API errors prior to trying to create the breakpoint. All around trying to pull details from packages that belong to other parties. There was nothing when trying to create the breakpoint. Do I need to adjust the logging level?
    – Daniel Ballinger
    Commented May 10, 2017 at 19:23
  • Can you please check the ...\workspace\.metadata\.log file for any output? I just want to make sure that you don't run into the Neon.3 Equinox resolver issue (bugs.eclipse.org/514149).
    – Gunnar
    Commented May 11, 2017 at 8:19
  • Also, I see that you have the Pilot plug-in. Did you install both into the same Eclipse version?
    – Gunnar
    Commented May 11, 2017 at 8:21
  • @Gunnar I've got both the pilot plugin and normal plugin installed in the same version. I'll try removing the pilot plugin then check the output in the log you mentioned.
    – Daniel Ballinger
    Commented May 17, 2017 at 21:19

1 Answer 1

Reset to default
2

The error message "The chosen operation is not enabled." usually comes up when there is something broken in an Eclipse installation. There are multiple ways to debug this. For example, one way is to go the the host OSGi console and look at the installed bundles/plug-ins. Anything in state "INSTALLED" indicates an issue.

Another option is to look at the Eclipse log file (in .metadata/.log) or the Eclipse Error Log view. It logs resolution errors during startup.

As a note, you should not run both plug-ins (Force.com IDE plugin "classic" and the Salesforce DX version "Force.com IDE (Pilot)") in the same Eclipse instance. There will be dependency issues.

Improve this answer
1
  • I removed the "Force.com IDE (Pilot)" plugin. That change alone appeared to be enough to get the debugger going as I could toggle the break points and then hit them and step through the code. Thanks for your help.
    – Daniel Ballinger
    Commented May 18, 2017 at 23:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .