163
Views
4
Comments
Solved
Unable to debug Producer (and "Selected Entry Module" not saving)
Question
Application Type
Reactive
Service Studio Version
11.54.15 (Build 62559)

 I've read other related threads and tried all the suggestions available to me (am a Citizen Developer and have no ability to configure anything enterprise-wide in Service Center): 

  • My dependencies are all updated
  • I have set Service Studio to use one connection per Request in the debugger
  • I set the Producer Module's debug entry point to the consumer module and initiate debugging in the Consumer Module

I still cannot step into Producer and view the breakpoints. Anything else I might try? 


Also, I noticed that the selected Entry module in my Producer Module never Saves. It always reverts back to "This Module". Is that intentional or is the selected entry module supposed to persist between sessions/saves? 


Thanks!

2021-09-06 15-09-53
Dorine Boudry
 
MVP
Solution

Hi gardensurfer,

 the fact that it reverts to "this module" is normal, it just means you have to explicitly choose the right consumer every time you test.

as for the debugging, you don't start debugging in the consumer, but in the producer. 

So choose the consumer from the dropdown in the producer debug pane, and start debug right there in that same producer debug pane.

It sounds like what you are doing now, is only starting debugging in the consumer, not the producer, and so if you don't have any breakpoints in the consumer, no debugging at all will happen.

If your consumer is the direct consumer of your producer, and has a home screen defined, that should start up when you kick off debugging from your producer, because you chose the right consumer in it's debug pane.

Dorine

2022-08-04 19-07-57
gardensurfer

Thank you. That was exactly the guidance I needed and it worked to start the Debugger from the Producer module. I did note (for anyone else who may be trying to troubleshoot similar issues) that the "Open in browser" checkbox - when checked - still did not open my Chrome (v114.0.5735.198 (Official Build) (arm64) browser. But if I manually opened my browser and pasted in the URL of the Entry module home page after starting the debugger in the Producer, it allowed me to debug, stopping at Breakpoints in the Producer module as I'd wanted. 

UserImage.jpg
Anjali Choudhary

@gardensurfer 

Try

In Edit menu, under Preferences, check the Use One Connection per Request in Debugger option. 

Or Don't close the Chrome window and click the Start Debugging button again. 

Thanks


2021-09-06 15-09-53
Dorine Boudry
 
MVP
Solution

Hi gardensurfer,

 the fact that it reverts to "this module" is normal, it just means you have to explicitly choose the right consumer every time you test.

as for the debugging, you don't start debugging in the consumer, but in the producer. 

So choose the consumer from the dropdown in the producer debug pane, and start debug right there in that same producer debug pane.

It sounds like what you are doing now, is only starting debugging in the consumer, not the producer, and so if you don't have any breakpoints in the consumer, no debugging at all will happen.

If your consumer is the direct consumer of your producer, and has a home screen defined, that should start up when you kick off debugging from your producer, because you chose the right consumer in it's debug pane.

Dorine

2022-08-04 19-07-57
gardensurfer

Thank you. That was exactly the guidance I needed and it worked to start the Debugger from the Producer module. I did note (for anyone else who may be trying to troubleshoot similar issues) that the "Open in browser" checkbox - when checked - still did not open my Chrome (v114.0.5735.198 (Official Build) (arm64) browser. But if I manually opened my browser and pasted in the URL of the Entry module home page after starting the debugger in the Producer, it allowed me to debug, stopping at Breakpoints in the Producer module as I'd wanted. 

UserImage.jpg
sofi_nik

Hello everyone! Regarding the above issue even with the fixes still no able to debug to the consumer (also relatively new to the platform :) ).. if you any other suggestions that would be extremely helpful since not able to work properly atm.. thank you in advance!

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.