Hi,
I have created a Rollbase mobile app and I can test it in desktop web browser and using Rollbase Mobile Native Tester for Android without any problem.
When I try to test it using Rollbase Mobile Native Tester for iOS at iPad Air, I receive error "Session must be instantiated before calling login service" during login to the mobile app.
As the same app can be run in Rollbase Mobile Native Tester for Android successfully, may I know what additional steps are required when using Rollbase Mobile Native Tester for iOS?
Many Thanks in advance!
Cammy
Hi Cammy,
One of the engineers who works with the Native Tester for iOS said that the problem you and egarcia found is fixed in a new version of the Native Tester and that new version is currently being tested.
--Wayne
Hi,
Were you able to get any more information by following egarcia's suggestions above? Can you send us a backup of the app, or provide more details about how it works? For example, what is the authenticationModel (I assume it's Form, but it's worth checking), what is the serviceURI, when does it invoke the SessionService_Session service, and when does it invoke the SessionService_Login service (the names may be different, but they will be something like that, I think -- they appear as Data Sources and are probably called DefaultSession and DefaultSessionLogin).
Regards,
Wayne
Hi,
Were you able to get any more information by following egarcia's suggestions above? Can you send us a backup of the app, or provide more details about how it works? For example, what is the authenticationModel (I assume it's Form, but it's worth checking), what is the serviceURI, when does it invoke the SessionService_Session service, and when does it invoke the SessionService_Login service (the names may be different, but they will be something like that, I think -- they appear as Data Sources and are probably called DefaultSession and DefaultSessionLogin).
Regards,
Wayne
Flag this post as spam/abuse.
Hello,
I took a look at this issue and I was able to reproduce it.
When I added debug messages on success and error for the DefaultSession service, they were not displayed.
I added code to invoke the service using JavaScript so I could add additional debug messages.
I found that that the call to new progress.data.Session() was failing because somehow progress.data was undefined.
I looks like somehow the JavaScript file that contains it is not being loaded.
I worked around this issue by adding a private copy (using new JavaScript file) of progress.jsdo.2.2.js to the project.
After this change the DefaultSession service was instantiate and I was able to login. However, I ran into another issue.
Are you using the Native Tester for iOS so that you can test native services?
Does scanning the QR code from the Test option work for you on iOS?
I hope this helps.
Thanks.
Yes, I am trying to use Native Tester for iOS for testing mobile native services. I just try scanning the QR code from the Test option and I can run the mobile apps at iPad.
Hello,
I took a look at this issue and I was able to reproduce it.
When I added debug messages on success and error for the DefaultSession service, they were not displayed.
I added code to invoke the service using JavaScript so I could add additional debug messages.
I found that that the call to new progress.data.Session() was failing because somehow progress.data was undefined.
I looks like somehow the JavaScript file that contains it is not being loaded.
I worked around this issue by adding a private copy (using new JavaScript file) of progress.jsdo.2.2.js to the project.
After this change the DefaultSession service was instantiate and I was able to login. However, I ran into another issue.
Are you using the Native Tester for iOS so that you can test native services?
Does scanning the QR code from the Test option work for you on iOS?
I hope this helps.
Thanks.
Flag this post as spam/abuse.
Hi Cammy,
One of the engineers who works with the Native Tester for iOS said that the problem you and egarcia found is fixed in a new version of the Native Tester and that new version is currently being tested.
--Wayne
Hi Cammy,
One of the engineers who works with the Native Tester for iOS said that the problem you and egarcia found is fixed in a new version of the Native Tester and that new version is currently being tested.
--Wayne
Flag this post as spam/abuse.