Skip to Content
author's profile photo Robin Panneels
0
Robin Panneels

Mobile Development Kit Client - Error with Odata metadata on app update

Posted on Apr 23, 2020 at 07:07 AM 256 Views

Hello experts,

We are trying to get a MDK app running that accesses an OData service on our SAP back-end using mobile services in Cloud Foundry. So, we connected our CF account to the cloud connector and created a destination for our back-end in the CF also.

In Mobile services we created a Hybrid App and connected it to our OData service, see steps below:

When I ping or test the OData service it returns no errors.

At this point I have the feeling that my configuration on Mobile Services side is quite ok. We followed the steps on the tutorials for MDK, so the NEO instance has a destination that points towards the mobile-services on CF. We then follow the steps in following tutorial:

https://developers.sap.com/tutorials/cp-mobile-dev-kit-online-app.html

When we then open the app on the mobile phone we get following issue:

Any idea what might be causing this?

Thanks in advance!

Kind regards,

Robin

2020-04-23-08-53-24-sap-cloud-platform-mobile-serv.png (52.0 kB)
mobile-services-mobile-connectivity-1.png (39.5 kB)
mobile-services-mobile-connectivity-4.png (86.6 kB)
screenshot-20200423-083349-mobile-svcs.jpg (124.0 kB)
2020-04-23-08-38-38-photos.png (63.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    author's profile photo Robin Panneels
    Robin Panneels
    Posted on Jul 17, 2020 at 06:27 PM
    0

    The issue was that in the metadata of the service I used, there was a reference towards another service. So we had two options:

    1. Enable ignoreAllReferences in the CDSL options of the service in the MDK project
    2. Modify the rewrite urls in the destination in Mobile services

    I tested option 1 and this worked for my case

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Jitendra Kansal
    Jitendra Kansal
    Posted on Apr 23, 2020 at 12:07 PM
    0

    Robin Panneels

    Couple of things you can look into:

    1. In Mobile Network trace feature in Mobile Services cockpit > select Log message (header & body) and start recording
    2. Reproduce the issue on client side.
    3. Switch back to MS cockpit, stop recording and check if you find anything relevant in the trace file.

    Are you trying it on MDK public store client (check once if you have already updated it to 4.2.1)? If so, you can connect your Android device to PC and can access ClientLog.txt file via the Android Studio> View menu > Tools Window > Device File Explorer>data>data>com.sap.....>files>ClientLog.txt , there you may find some more info.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Bill Froelich
    Bill Froelich
    Posted on Apr 23, 2020 at 12:16 PM
    0

    Robin,

    I would start by checking the Mobile Services logs for your application to see if there is a more descriptive error message. In Mobile Services go to Analytics > Logs and see if there is more detail related to the error.

    Additionally, I would try accessing your application API url for that destination in the browser to confirm you can retrieve the metadata. So for your example it would be https:// - trial-01-be-odata-redirect.cfapps.eu10.hana.ondemand.com/be.odata.redirect/$metadata?auth=uaa just to verify it is accessible (I would guess it is).

    --Bill

    Add a comment
    10|10000 characters needed characters exceeded