E
egarcia
Guest
Hello Meyrick, Thank you for your time to look at this issue together. I am glad that the project worked just fine after adding the Session Service and calling the new services. Here is summary of the issue and its resolution in case that others run into this issue. The Mobile project was created in Mobile App Builder 9.0 and contained the MobileService_Login, MobileService_Logout and MobileService_Settings entries in Services. The implementation code for these services used SessionLogin.js and SessionLogout.js (the code for these services was inline). When the project was upgraded to use the latest features, a new version of SessionLogin.js and SessionLogout.js was provided (the code for these services use a wrapper code that calls an object with the implementation). However, since the old services were still in used, it was trying to use the new version of the code and would fail with the message: Uncaught TypeError: Cannot read property 'serviceSettings' of undefined progress.mobile.3.0.js:671 To resolve this issue you would either need the following: 1) Old version of the code. 2) Add a new Session Service. Prior to the upgrade, you could have renamed the old implementation files so that the old services would continue working. We have added a note mentioning about this to the upgrade steps: docs.mobile.rollbase.com/.../upgrading-an-existing-mobile-app Since the project was already upgrade the adding a new Session Service was the best approach. To add a new Session Service you could do the following: 1) Add a new Session Service using New- Sesssion Service. 2) Use the upgrade steps "Adding Session Service and Login Page to Upgraded Mobile Apps". These steps are now documented in the upgrade page and also in the wiki: community.progress.com/.../2186.openedge-mobile-white-papers.aspx Option #2, with the white paper, guides you through adding a new Session Service and Login page that can be used as examples. Because you already had a LoginPage in your project it was easier to use that option #1 with your LoginPage and set the SessionService_Settings (Catalog URIs and Service URI) and usage of the Session Service, Login Service and Logout Services. The Session Service needs to be called first, then the Login and Logout Services need to be called (generally from a button), and call then the JSDO Service. The document "Adding Session Service and Login Page to Upgraded Mobile Apps", mentioned above, talks about this. The white paper on how to build a Mobile app from the Phone App template also talks about this: community.progress.com/.../9823.aspx When using the new implementation files, old MobileService_Login and MobileService_Logout are no longer need and would continue to throw the exception. These must be deleted. Thank you and regards.
Continue reading...
Continue reading...