[joserendal]

Hello,

In previous versions of the Smartprocess application for Android it was possible to use the Chrome Remote Debugging Feature (https://developers.google.com/web/tools ... g/webviews) to test and debug our processes when running inside the mobile app.

But with the latest version of the application we're not able to do this any more. Is it only happening to me? How can we debug our processes when running inside the app without this feature? Because sometimes you see strange behaviors that only occur in the mobile app, not in the browser.

Thanks for your help.

Regards

[amosbatto]

Are you using the new PM 3.2 (which was released today)? Which version of the ProcessMaker mobile app?

[joserendal]

Hi Amos,

We are still using Processmaker version 3.1.2 Enterprise Edition. Regarding the mobile app, its the 1.1.0.1 version.

Our mobile device has Android 4.4.4

Chrome Remote Debugging feature worked perfectly in the same device with previous versions of the mobile application.

Thanks for your help.

Regards

[amosbatto]

I just tried debugging and it works with ProcessMaker Mobile App 1.2.0.1 in Android 6, connected to ProcessMaker 3.1.2 Enterprise, using Chrome 50 in Debian Linux and it works. You should upgrade the mobile app to 1.2.0.1 and see if that fixes it.

debugAndroidPM3.1.2.png (212.08 KiB) Viewed 6199 times

[joserendal]

Hi Ammos,

I have updated the application to the last version, as you mentioned, and tested in two different devices (one with Android 4.4.4 and other with Android 5).

My browser recognizes them in the chrome://inspect tab, and if I open a normal tab in the chrome browser I can inspect it. But when I open a form in the mobile application it does not show anything.
If I use version 1.0.8.0 of the application, it allows me to debug remotely our Dynaforms.

Any idea? Maybe its a windows problem or something?

Thanks for your help.

Regards

[amosbatto]

Have you tried it with version 1.2.0.1 of the ProcessMaker mobile app? If it doesn't work with version 1.2.0.1, then you should file a bug report about it at http://bugs.processmaker.com