Hi Dave,



Thank you for your bringing this issue to our attention.

We have reproduced this and I've added it to our backlog. Our developers will solve the incorrect direction in the Debug mode.



Thank you,

Kate

Excellent - thanks!

Any news when this will be fixed? And also, is there any workaround so we can still debug the controller? 

Hi Tomic,

Thank you for your questions.

You can use the next workaround:

1) please find in your log file the Method_Entry where the controller is called and copy an ID of the class from this entry; it begins with '01p...';

2) paste this ID to the Code_Unit_Started entry at the beginning of your log file instead of the page's ID which begins with '066...';

3) save the changes in the log file;

4) start debugging from this log file.

Please let us know if this workaround help to solve the issue.

Our developers will work on solving this issue in a frame of improving the Apex Retrospective Debugger functionality that is planned in one of next versions of the IDE.

Thank you,

Kate

That seems to work for my test case. So nice to have this feature again!! 

Hi Dave,

Thank you for your comment. We are glad that this works for you.

I'll keep you updated when the issue will be solved in The Welkin Suite IDE.

Best Regards,

Kate

Hi Guys,

I want to inform you that the issue related to debugging the log file with an Apex controller is solved in Spire R6 version of The Welkin Suite IDE.

Please let us know if this issue would be reproduced for you.

Thank you,

Kate

Hiya Kate. Looks good now - thank you!!

Hi Dave,

Thank you for your feedback!

In this case, I'll close the current topic.

If you have any other questions or suggestions, please contact us.

Regards,

Kate