34
Views
7
Comments
Solved
Debugger not working in Client Actions
Application Type
Mobile
Service Studio Version
11.10.3 (Build 36711)
Platform Version
11.10.0 (Build 22422)

Hi All,

Im getting a problem when I try to debug my mobile app, it seems that are two different versions between public and personal area, what is estranged because I can't publish in the personal area. What happend is that all breakpoints in the client actions are not working and only in the Server Actions.

That happen only when I'm debugging with USB/Android connected, So with Chrome debugg mode works fine.

Any idea why this strange behavior?

MicrosoftTeamsimage2.png

Rank: #2768
Solution

Hello everyone,

My client got a response from the Outsystems support team about this case and is now resolved with the steps below:


OutSystems Support Team

We were analyzing recent reports of the behavior reported in point 1 and that seems to be related to a change introduced in Service Studio 11.10.1. This is currently under investigation and we would like to politely ask you attempt the following workaround to unlock the situation:

1.    Download Service Studio 11.10.0 and install it 

2.    Open the Service Studio Preferences and Disable the Auto-Update:

3.    Test again the behavior 

Thanks for helping.

Cheers

Champion
Rank: #99

Hi,

That never happened to me, but I found at least two topic similar to yours (the first one seems more similar). Maybe you can take a look and see if they can help you:

https://www.outsystems.com/forums/discussion/32953/mobile-debugging-android-ios-not-working/

https://www.outsystems.com/forums/discussion/32377/debugger-is-not-working/


Hope this can help you.


Best regards,

Ricardo M Pereira

Rank: #295

Hi Alan,

You can take a look at the below documentation which is showing how to troubleshoot debugger connection issues:

https://success.outsystems.com/Documentation/11/Developing_an_Application/Troubleshooting_Applications/Debugging_Applications/Troubleshoot_Debugger_Connection_Issues

Hope this will help, Thanks :)

Rank: #2768
Solution

Hello everyone,

My client got a response from the Outsystems support team about this case and is now resolved with the steps below:


OutSystems Support Team

We were analyzing recent reports of the behavior reported in point 1 and that seems to be related to a change introduced in Service Studio 11.10.1. This is currently under investigation and we would like to politely ask you attempt the following workaround to unlock the situation:

1.    Download Service Studio 11.10.0 and install it 

2.    Open the Service Studio Preferences and Disable the Auto-Update:

3.    Test again the behavior 

Thanks for helping.

Cheers