mobil ui crash

[johanningmann]

Hi, I playing around with the mobil ui. I installed the app from the android store and just trying to start the demo. The demo runs fine until I accept the login credentials after the login I can see that the visu is building up and then the app crash. No error message or any other information why.


Here the details of my mobil device:

Samsung S8
Model SM-G950F
Android Version 8.0.0


mobil ui version WinCC OA 3.16.2



Do you have an Idea why the app is crashing?

We plan to rollout the app for all our employees, but as along as the app is not stable I see a problem coming up. :dry:


Kind regards
Frank Johanningmann

[Andorhal]

Hello Frank,

demo.etm.at is working perfectly fine on our Android 8.0 devices.

Did you try your own projects?
Did you try to run the demo project locally with ordinary WLAN connection? (you can download the project here)

BR Robert

[johanningmann]

Hi Robert,
I tried my own project and it is the same behaviour. The app message is: WinCC OA UI angehalten

And I tried to new install the app, to empty the cache and to empty the memory, unfortunately without success...


Any further Ideas, as far as I know there is now log for the android devices available, right?


Kind regards,
Frank Johanningmann

[johanningmann]

an another message is: WinCC OA UI bleibt ständig stehen



Kind regards
Frank

[tmalone]

maybe you can show us your config.webclient file?

This is a special version of the config file which is read by the webclient_http.ctl. Remember that a mobile client rarely has a hosts file, so you need specify the event and data lines with IP addresses. That goes into the config.webclient file.

[Gertjan van Schijndel]

Frank Johanningmann wrote:

Any further Ideas, as far as I know there is now log for the android devices available, right?

Instead of starting the project, a long press on the project shows a menu with an option to send logfiles.

[mkoller]

If the app is crashing, you will potentially not get useful information from the PVSS_II.log file.
What you can do is connect the device via USB cable. Allow USB-Debugging on the device (settings).
Then install and run "adb logcat" on your PC, which will show you the device internal log.
(On openSuse Linux this is in the android-tools package)
When the app crashes, you will find additional hints why it crashes - send it to us.

[johanningmann]

Hi,
please find att. the logcat file.


Kind regards https://www.winccoa.com/fileadmin/image ... logcat.txt

[mkoller]

Thanks for the logfile.
Yes, the app is crashing

10-05 20:12:41.262 7243 7243 D WinCC_OA: WCCOAui (57), 2018.10.05 20:12:41.262, Qt, QObject::setParent: Cannot set parent, new parent is in a different thread
--------- beginning of crash
10-05 20:12:41.265 7243 7243 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x4 in tid 7243 (emens.winccoaui)

...
sadly I can not reproduce the problem yet.
We'll investigte further ...

[johanningmann]

Hello Martin,
do you have any update for us?

Mind regards
Frank Johanningmann