SAP BTP SDK for iOS 7.0 is available
Release announcement: SAP BTP SDK for iOS 7.0 is now available
Santa’s elves were overworked this year, and hence this present comes a little late, but we hope the wait was worth it. Version 7.0 is released!!! 🎉🥳
You can download the SDK and its Assistant from the Software Center or the downloads section on develeopers.sap.com.
This version supports iOS 14+ and Xcode 13.
The new version has all sorts of goodies and I encourage you to read the What’s New document and our updated API reference documentation.
Here are some of the new features provided by the SDK.
Ahh, yesssss. Finally, support for Apple Silicon ARM simulators 😌.
Use the SAP BTP SDK for iOS frameworks on Mac computers with Apple silicon without the need for Rosetta.
Cross Context SSO with OAuth
The cross context SSO feature makes onboarding easier for users by transferring OAuth tokens from an established session to their mobile app built with the SAP BTP SDK for iOS.
For example, a user opens the SSO onboarding URL on their desktop. The user can open the native app, navigate to the QR code scanning screen, and scan the QR code before it expires. If successful, the native app will get onboarded automatically. The user does not have to enter their credentials again.
Here is a video demonstrating the user experience on iPad with an app generated by the SAP BTP Assistant SDK for iOS 7.0
New color palette, typeface, and large title for SAP Fiori for iOS
We are bringing the award-winning typeface 72, explicitly designed for SAP and SAP Fiori, to iOS! Together with a new color palette (
.latest palette version is v6), removing contrast background for specific components (
FUINavigationBar) and enabling large title by default this gives a fresh look and feel. 😎
Administrators can activate or deactivate specific versions of an application in SAP Mobile Services. The SAP BTP SDK for iOS provides
ApplicationVersionObserver in SAPFoundation and
ApplicationVersionStep in SAPFioriFlows to stop the user from onboarding if the version of the application is inactive.
Lock App Based on Timeout in Passcode Policy
Administrators can maintain a
Lock Timeout as part of the passcode policy configuration in SAP Mobile Services. Previously this information was ignored by the SDK. Now the SDK will enforce this setting by calling
ApplicationUIManaging.hideApplicationScreen(completionHandler:)(if implemented by the app) when the user leaves the app in background for longer than the lock timeout allows.
On behalf of the SAP BTP SDK for iOS team I wish you a happy New Year and a great start in 2022 !
Hi Marco, great
right now my client don't want moving forward with changing all navigation bar to white and using big titles, how can prevent this (not using the new v6 color palette) ?
the macos assistant has a bug when I click on file and Install Generator CLI it ask me to grant permission which I granted and after I got an error message, already created an incident for it
also when launching the assistant it freeze for 10 sec before being responsive
thanks and happy new year!
Happy New Year!
In version 7.0, you see the beginning of Fiori for iOS design guidelines changes. Some changes are mandatory for all applications using the Fiori for iOS design to ensure consistency. Some changes are optional and configurable.
Large titles are optional but encouraged and therefore 'on' by default. You can disable large titles by setting `prefersLargeTitles` on UINavigationBar to false (or set `largeTitleDisplayMode` to never on navigationItem of each view controller).
The background color change for the navigation bar is mandatory and cannot be changed. Your client can prepare to adopt such changes and delay the production upgrade to version 7.0 until then.
I asked one of our experts to review your incident regarding the Assistant. We changed the Assistant macOS application to be a sandboxed application, and the Assistant no longer has access to the entire file system. I recommend checking if you have actual permission to copy files to folder "/usr/local/bin". If not, you can copy the files to a different location by pressing the option key, selecting "Install Tools" or "Install Generator CLI", and selecting a folder to which you have permission to copy files.
The team is looking actively into reducing the time of unresponsiveness during the Assistant startup.
On behalf of the team, I apologize for any inconvenience.
Hi Marco, thanks, ok no problem ...
No problem for the nav bar color, I understand consistency is super important in design and totally agree 🙂
I know it would be a major effort for your teams, but it would be nice to see the iPad companion app and the experience Fiori design guideline site reflecting these new UI changes (all screenshots)
For sapcpsdk-proxygenerator, what I don't understand is that I have installed almost all past macos update (6.x.x) and install the CLI without any permissions problems, how comes the permission problems only occurs with SDK 7 ?
currently the folder permission of my /usr/local/bin is drwxr-xr-x
I always used the CLI generator vs the macos app itself, one thing that is not clear is when I install a new version of the assistant app, do I need to explicitly go to file and install the CLI generator ?
Also is there a way to know which version the CLI generator I have under my /usr/local/bin
it would be nice to have a CLI option something like sapcpsdk-proxygenerator --v
for copying, I am not sure to follow your instruction (option key, selecting "Install Tools" ...), where ?
the files have been copied to /Users/Shared/SAPbtpSDKassistantForIOS-Resources/7.0.0/
sorry that's a lot of question
Hi Marco, thanks for the information
I prefer option 2 since the previous version of the Generator CLI was installed there and I would like to keep it there ...
I changed the ownership of the directory to my user with your directive and installed the CLI successfully
However, I am not sure if it's a best practice to do that (usr/local/bin owned by my user vs root)
after I set it back to root with the same command
sudo chown -R root /usr/local/bin
Sorry for coming onto this thread late - I've only just had a chance to look at the 7.x release 🙂
I'm having an issue with the install. Basically the 7.0 assistant won't start - the crash report says:
Happy to share the whole report if that helps the team.
If I revert back to 6.x it runs correctly and with no issue. My guess is that it's a permissions thing maybe? Something that has changed between 6 and 7. Any assistance would be greatly appreciated! I'm using macOS 12.1
This crash is occurring in 7.0 when there is past project that was created in a directory with spaces present in its path. The issue is fixed and will be part of our next patch (7.0.1). We regret the inconvenience caused.
Thanks and Regards,
Thanks so much for the update - will keep an eye out for the 7.0.1 drop. I *should* be able to get past the issue if I changes some of my project paths I guess - will see what happens