on 11-05-2021 8:34 AM
When updating SAM 2010 application with deployed metadata definitions I have error „App update failed, will roll back to previous metadata definitions. Reason: Offline OData Initialization Failed“.
But when I run standard SAM 2010 from APK downloaded from SAP (MOBASSTMGRAND00_0-70005811.APK) application connects fine and retrieves data from backend SAP ERP. That would suggest probably that Mobile services setup (including offline connectivity) is ok and that something is wrong with deployed metadata (I'm using Web IDE)?
I tried suggestions from https://blogs.sap.com/2018/03/15/troubleshooting-tips-for-mobile-development-kit/ (I checked Service URL, Application ID, Destination, refreshed objects in service file) but with no success. Application builds fine and is deployed to BTP successfully but fails to initialize.
Thanks, Igor
The client log file will usually tell you why the failure occurred. If you are on iOS, you can directly download the logs from the device through iTunes/Finder. On Android, you need to make sure log upload is enabled in Mobile Services and upload the log to view it. Direct download of logs is available in MDK 6 and above on Android.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill for info about logging!
Log goes like this: ..Upgrading application to version 7...Default Values found...Branded Settings found...Client Latched Settings Found (lots of those)... and then lot's of "Error: [-10058] Cannot perform the requested operation because the store is not open."
Do you think there is some setting in metadata that I'm missing (I imported original SAM 2010 metadata) or still some parameters in offline configuration are wrong? What baffles me is that original SAM client works.
The "Error: [-10058] Cannot perform the requested operation because the store is not open." is expected while the application is starting up since the page loads but the store is not yet initialized or opened. After opening the page refreshes.
Usually the failure during initialization typically outputs an error about something it is trying to fetch from the backend. If you are not seeing an error in the client log you should check the logs both in Mobile Services and your backend for any other possible logs.
User | Count |
---|---|
75 | |
10 | |
8 | |
4 | |
3 | |
3 | |
2 | |
2 | |
2 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.