Issues Accessing MDK Application on Android Devices

[#1]

Hello Community,

I am experiencing issues when trying to access an MDK application from a device running the Android operating system.

When I scan the QR code and log in through Mobile Services, I receive the following errors:

 Error during application update, rolling back to previous metadata definitions
Reason: Invalid call to EventHandler.executeAction /pmp_smart_pm/Actions/Service/InitializeOffline.action is not an action

However, when I log in using the same user credentials on a device running iOS, everything works without any problem.

Has anyone faced a similar issue? Could this be related to a specific Android configuration or compatibility?

Any help or guidance would be greatly appreciated.

Thank you!

[Jitendra_Kansal]

@MaximoSanchez Yes, looks like you are referencing to an BTP destination in your mobile destination.

I would like to see the URL you have configured in your BTP destination. Could you please share a screenshot of it? (If there is any personal information, kindly blur it out.)

[MaximoSanchez]

I had to refer to a destination in BTP because if I referred to the cloud connector and used “cloud connector SSO” as the SSO mechanism, I got this error. 
I'll also share the destination I configured. This connection error started occurring after migrating to S/4 HANA. We checked the certificates and they all seem to be there. We don't understand why it won't let us connect the application to the OData service through the cloud connector.

[Jitendra_Kansal]

@MaximoSanchez Could you share how did you configure the ERP_MOA_PM_S4 destination in the mobile services app configuration?

[MaximoSanchez]

Hello! Are you referring to this?

[bill_froelich]

Can you shared the .service for your application.  The one error seems to indicate a need for an additional property in there.

[MaximoSanchez]

Hello! I was able to solve the previous error by modifying the Path Suffix field. In that field I had entered /, but I removed it, deployed again, and now users with Android devices can log in without issues. However, users with iOS devices cannot. The error shown on iOS devices is the following: "Alert: Error during application update, rolling back to previous metadata definitions. Reason: Invalid/Incompatible bundle file." And in the Mobile Services log I see this message: "The request path / is not assigned to a destination. Rejecting request with 404 (not found)." I don’t understand why this issue does not occur on Android devices anymore. Should I enter the service name in the Path Suffix field instead? For example, something like: /sap/opu/odata/... Thanks for your time!

[bill_froelich]

Are you using any metadata extensions in your project you deploy from BAS?

[MaximoSanchez]

Hmm, I don't know what you mean by that. I don't think so. How can I check?
For example, I have a file in Services that contains the metadata, but I consume the odata service from zpm_odata.service.