Hi,

Just a notice.

I'm having the same problem in PB2019R2Beta  2279  (same build on PB and PS )

- I created a bug report on this.

I also have PB2017R3 installed on the computer.

Regards

Georgios

Hi Winthor,

looks like the .dat files corresponding to migrated data windows are not downloaded to your iOS devices.

Two tests to do:

1) clear PowerServer logs in AEM, enable debug mode and send us server & error logs after the app is started

https://docs.appeon.com/appeon_online_help/pb2017r2/server_configuration_guide_for_net/Logs.html

2) use the Log object

https://docs.appeon.com/appeon_online_help/pb2019/workarounds_and_api_guide/ch01s03s03.html

and write return code for SetTransObject and Retrieve operations

Best,

.m

attached are the screen shots from ios and android.

for reference: url http://119.92.113.203/pbtest

Hi Winthor,

as already suggested

"Kindly give us some more info (like a screenshot) or post the code you are trying to execute."

Or make the server public and let us to execute your app and verify.

Best,

.m

Hi Winthor ;

  If the DWO's appear on Android, then they have to appear on iOS as well. Especially if the App is coming from the same PowerServer URL. Which means that the DWO's were published (deployed) OK to the PS "server" itself.

  The only exceptions to this could be ...

1) iOS App is published to a different URL and the App Profile in the PS Toolkit that deploys to PS is not correct.

2) The Mobile devices have a mismatched version of Appeon Work Space (AWS) on them that does not match the version of PowerServer. They must be the same.

HTH

Regards ... Chris

Hello Winthor,

what version of PS and AWS are you using? What DB?

Kindly give us some more info (like a screenshot) or post the code you are trying to execute.

In principle there is no difference between iOS and Android DW handling.

Best,

.m