Product Information
SAP BTP SDK for iOS 9.1 is now available
Release announcement: SAP BTP SDK for iOS 9.1 can now be downloaded
 |
The new version of SAP BTP SDK for iOS 9.1 is now generally available.
You can download the latest version of the SDK either from the Software Center or the downloads section on develeopers.sap.com |
With this latest release, the SAP BTP SDK for iOS team has brought some exciting new features for you to explore.
In this blog, we will highlight the new upgrade’s offerings. Please visit our documentation and API reference to get a detailed overview of all the features released.
Highlights
Security
App Attest Service
By utilizing Apple’s App Attestation service, one can be confident that their enterprise application is operating on a device trusted by Apple. This service enables app developers to validate that their apps are running on authentic, unaltered devices and are not being impersonated by malicious entities.
The SAP BTP SDK for iOS lets you quickly implement this service, thereby protecting your enterprise application and its users. On detecting a breach, the app developers can now block access to sensitive. Alternatively, if the access risk is too high, you can deny access to the app altogether. Using the SDK will also empower your administrator, who now has a one-stop UI to monitor all the breaches.
Follow https://twitter.com/sapmobile on Twitter for a detailed blog on the topic and how you can test this yourself.
SAP Fiori
New Controls
The new version of the SDK continues to bring more Swift & UI-Kit-based controls, such as an editable table or a timeline. You can continue to choose from an ever-expanding range of thoughtfully designed rules that will enhance your enterprise application’s functionality.
 |
 |
|
| Editable Data Table | Empty State | Timeline |
Figure 1: Fiori Controls
Offline
Performance Enhancement
The new optimized population of entity values comes with significant performance improvements.
Feature Summary
This blog highlights some of the features released with the new version of SAP BTP SDK for iOS – 9.1. For details, please check the important links section.
- Integrate with App Attest Service
- New Fiori Controls
- Offline Performance Enhancement
Important Links
Acknowledgement
A huge kudos to the spectacular team that worked tirelessly, right from conceptualizing the improvements, to defining, designing, building, and eventually delivering them.
great update, I can see in the release note
but how can we generate OData entities to use the new async/await with sapcpsdk-proxygenerator?
I have installed the new CLI and it does not seems to be supported yet
Hi Alexandre Giguere,
you can refer to the new additional parameters of proxygenerator, -offline -async:await for example:
./sapcpsdk-proxygenerator -offline -async:await --metadata /Users/xxxx/Downloads/Metadata/SampleODataV4metadata.xml --proxylibs ./sapcpsdk-resources/ --service Sample4 --prefix Sample4 --destination /Users/xxxx/Downloads/ProxyClass/
Thanks,
Yong.
thanks for sharing, when you say you can refer to:
actually, there is no documentation regarding that, the help page is not up to date
https://help.sap.com/doc/978e4f6c968c4cc5a30f9d324aa4b1d7/Latest/en-US/Documents/Frameworks/SAPOData/index.html
also by running the ./sapcpsdk-proxygenerator CLI, on the terminal, there is no info regarding the new argument (-async:await)
only this
Please specify one of the following service options: -any, -legacy, -offline, -online.
thanks
Hi Alexandre, Yong,
@Alexandre Thank you for raising the issue. We will be sure to include this in our documentation.
@Yon Thank you for providing a response.
Yong Hu & Sandeep Tetali Dattatreya Sitarama
still not yet documented and also it's not true running the default CLI without argument generates proxy classes with async:await by default (mention to me from an incident support), you have to add the argument explicitly and it works, and also running the CLI with --help, it does not show this parameter
thanks
Hi Alexandre,
Thank you for bringing this to our attention. I will look into the documentation update.