on 05-22-2014 2:23 PM
Hello,
we make a app which works fine in the ATE Testenvirement and also in a iPhone but our main Plattform is the The WIndows Mobile Pocket PC.
We use a Motorola MC65 with Windows Mobile 6.1 Professional.
On the Motorola the app crashes in a definite transaction when we close the transaction screen.
Workflow is this: we open a detail screen with a listview -> with double click we pick a object from a collection and starts the transaction -> close the transaction screen -> now a rule decide what will happen (you can see the rule in the picture) -> but the app crashs before something happens.
Could we debug the client or could we create some loggings on the device? We dont know how we could find out why the app crashes. (as information: if the agentry client crashes on this point, we could not end the task from the agentry client with the task manager, we have to restart the Motorola client)
Thanx,
André
Tags edited by: Michael Appleby
Hallo,
now we fixed the problem.
As i told you we start the transaction screen from the detail screen and after ending the gtransaction the screen did not close and the client did not respond anymore.
We fixed the Problem in this way that we do a navigationstep after the transaction step. In this we make the decision which screen should be shown as the next screen an open it. Thats all. In all other Client beside the WinCE Client the Transactionscreen closed and we could see the last detail screen. But on the WinCE Client we nedd the navigation step.
I dont know if this is a bug from the WinCE Agentry Client Version 6.1.4.54024 but this workarpund was the solution for us.
@Jason: we breaking the rule down to separate subrules so the debugging in much better but we loose the reference to the object we used in the main rule, so we keep the active object refernce in a temp attribut at the main object and get the active object with this id in the subrules
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Andre,
What version of the Agentry client are you currently running?
What type of transaction are you running prior to the crash?
This is something where you need to look at all the steps of the action and targeting of subsequent steps. Your rule runs other subactions which also need to be reviewed in trying to determine where the problem is.
I would recommend that you open up a ticket with Support as they can help you better troubleshoot and diagnose the problem.
--Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Agentry Client Version is 6.1.4.54024_ClientWinCE the clients where the app not crashes is the actual iOS-Client from the app store and the 6.1.4.179_ClientWin32.
The Transaction before the client crash is a update Transaction on a Attribut from the picked object.
This is something where you need to look at all the steps of the action and targeting of subsequent steps. Your rule runs other subactions which also need to be reviewed in trying to determine where the problem is.: yes we do this and cant realy find a reason, the problem is thats on the other clients and in the testenvironment everything is fine.
Thanx,
André
Andre,
That is a complicated rule with a lot of different collection searching/iteration techniques in use. I would try breaking it down into smaller test rules to pinpoint which IF branch is causing the crash on WinCE. You may need to approach a particular section in a different way to accomodate WinCE, even though in theory it should work the same on all devices.
Jason Latko - Senior Product Developer at SAP
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.