How to set Application Version for MDK Client?

[#1]

How can I set  or find the Application Version of an MDK Client?

I am trying to restrict access to only certain compatible MDK Clients compatible with the metadata data deployed. There is a setting in Security to restrict client by Application Version. But I could not find how this can be set for an MDK Client.

 For an Android Build of MDK Client, I tried to set this in app.gradle as suggested in Application Versioning documentation for Android. This succeeded in onboarding the client, but failed later when synching with an error from Mobilink. So that is not the correct approach. 

I suppose there is a correct way to do this with MDK.

[bill_froelich]

When using the Application Versioning in Mobile Services to restrict connections you need to specify the version to match the AppVersion from the MDKProject.json of your client.  When you add this restriction any clients not matching the versions will get an error when trying to onboard.

Alternately you can add logic into your MDK metadata to check the client version using clientAPI.getVersionInfo() and check the "Application Version" and determine how you want to proceed in those scenarios as well.  

[Dinu]

Hmm. That (using AppVersion) did not work for me. Let me try again with more care.

[bill_froelich]

Souble check your version on the Android Device under Settings > App > [your client name] and verify it maches what you expect to see

[Dinu]

I can onboard, I get MOBILINK_COMMUNICATION_ERROR on initialization.

I have a test setup where, metadata packaged with the app is an almost empty project. So DB initialization is triggered after the update. Onboarding and download of update succeeds, but DB initialization fails. 

[Dinu]

I tried onboarding Mobile Services Client (v 25.6.2). With the same result: MOBILINK_COMMUNICATIONS_ERROR. So the error is not because of my special setup. Is this configuration supported by MDK?

[Liev]

Dear Dinu

I am in the same situation now. I was able to install the client but failed to sync.

Been you able to resolve the issue?

Thank you

[Dinu]

No. I could not get this to work with offline odata. Requests to mobilink are not sent with the header required. If this is sent explicitly, it does work. So, my conclusion at the time was that it is not supported.