Product Information
Cloud Build Service: Build a client with specific SDK versions
One of the hidden gems of SAP Mobile Services is the Cloud Build Service, it allows our customers to easily build their branded client (Mobile Development Kit, SAP Asset Manager) with their custom branding and settings using latest SAP SDKs in the cloud, without having to install any developer tooling whatsoever. Once the build is successfully created, the binaries (apk/ipa) can be distributed over-the-air or downloaded for direct install or distribution via MDM tool of your choice.
One of the challenges our customers had was not having an option to choose an SDK version before creating their client. The Cloud Build Service would always build with the default SDK version. This was not quite helpful for them as they still wanted to build a client with the same version as they had tested their application earlier.
Good news is – with the recent release of SAP Mobile Services (Cloud Foundry only), Cloud Build Service now allows you to select an specific SDK version while creating a Mobile Development Kit client (standard/customized) or SAP Asset Manager client.
SDK options available for Mobile Development kit client type, these versions will be updated with the future releases
SDK options available for SAP Asset Manager client type, these versions will be updated with the future releases
Please note that
- this feature enhancement is available in SAP Mobile Services Cloud Foundry Environment only.
- Typically, we’ll only support the latest patch of a given release.
- MDK may show additional versions needed for specific SAP Asset Manager build configuration.
You can find more details on how to use Cloud Build service to build your Mobile development kit client in this tutorial.
I am looking forward to your feedback/comments.
Jitendra
Hi Jitendra Kansal
I tired to create a custom client with Asset Manager settings. But when it comes to the build process I always run into the same error:
EPERM: operation not permitted, copyfile '/mnt/workspace/SAMPROJECT/MDK_SDK/SAPPROJECT/app/App_Resources_Merge/Android/src/main/AndroidManifest.xml' -> '/mnt/workspace/SAMPROJECT/MDK_SDK/SAMPROJECT/platforms/android/app/src/debug/AndroidManifest.xml'
When I do the same on my local computer the build process succeeds. Any ideas why copying the AndroidManifest.xml fails?
Regards, Andreas
I see you have opened it as a new question, let's follow up there.
In my opinion, on Cloud Build Service, while creating a Mobile Development Kit client (standard/custom), it would be more useful to have the possibility to be able to select all versions of the specific version of the SDK (or at least for the last 2 main releases).
It has already happened that a SDK version (even the most recent) has a major bug, so sometimes you prefer to stay with the previous SDK version.
In other cases, however, you just need to integrate permissions into AndroidManifest.xml or info.plist and we don't want to retest the release update.
I open a Customer Influence request on SAP Influence:
https://influence.sap.com/sap/ino/#/idea/302628
Folk, please vote if it helps.