The MobileFirst SDK for
watchOS 2 does not support all MobileFirst
features.
Limitations
The optional frameworks that add features to the MobileFirst app are
not provided for watchOS 2 development. Some other features are limited by constraints imposed by
the watchOS 2 or Apple Watch device.
Table 1. watchOS 2 non-supported features| feature |
|
|---|
| openSSL |
not supported |
| JSONStore |
no supported |
| push |
not supported |
| message alerts displayed by the MobileFirst
code |
not supported |
| application-authenticity validation |
not compatible with bitcode, and therefore not supported |
| remote disable/notify |
requires customization (see below) |
| usernames/password security check |
use the pin code security check (see Setting up MobileFirst security for the iPhone app and the watchOS 2 app) |
Remote disable/notify
With the
IBM MobileFirst Platform Operations
Console, you can configure the
IBM MobileFirst Platform Server to disable access (and
return a message) to client applications based on the version they are running (see
Remotely disabling application access to protected resources). Two options provide default UI
alerts:
- when the app is active but a messages is sent: Active and Notifying
- when the app is outdated and access is denied: Access Denied
For watchOS 2:
- To see messages where the app is set to Active and Notifying, a custom
remote disable challenge handler must be implemented and registered. The custom challenge handler
must be initialized with the security check wl_remoteDisableRealm.
- In the case where the access is disabled (Access Denied) the client app
receives an error message in the failure callback or request delegate handler. The developer can
decide how to handle the error, either notifying the user through the UI or writing to the log. In
addition the above method of creating a custom challenge handler can be used.