Known Issue with SmartCollaboration messages in iOS15+

Expand

Collapse

Advanced SearchOpens new dialog

Enter plus (+) or minus (-) signs in search terms to make a word required or excluded
Search Tips

Search terms

Screen Reader users press enter to select a Filter by product. Filter by product

Screen Reader users press enter to select a Filter by category. Filter by category

Sort by Direction

Answer ID 12083 | Last Review Date 02/17/2022

Environment:

Oracle Field Service (OFS)

OFS Native App, device running iOS 15+

Issue:

There is a known situation within the OFS Native App for iOS. It is specifically for devices running on iOS 15+. The issue manifests when you see a SmartCollaboration push notification and your device is locked. When you unlock your device and open the OFS native app to read the message, you will see the counter indicating that you have a new message but the message will have no content.

This behavior is caused by a change made by Apple which enables by default in iOS15+ an experimental feature called NSURLSession WebSocket. This change is restricting the web socket from reconnecting after a disconnection/idle time.

Resolution:

As an alternative solution, end users can disable NSURLSession WebSocket from iOS settings following the steps below:

Open iOS Settings
Scroll down searching for Safari and tap on Safari
Scroll all the way down and tap on Advanced
Tap on Experimental Features
Scroll down until you see NSURLSession WebSocket (which will be enabled by default)
Disable NSURLSession WebSocket
Either close and reopen the OFS app or uninstall and reinstall it to reflect the changes.

As this problem is related to a third-party product (Apple's iOS 15) we have done a thorough analysis of what (if anything) could be done on our end to avoid this case caused by Apple. Unfortunately, the only way we can avoid it is by either using the previously described workaround that technicians can perform, or by having the field use the browser version instead of the installed iOS application. We understand that these workarounds can be frustrating and not easy to perform, however it is the only option technically possible, until Apple fixes the case.

If you feel this change made by Apple will affect your field negatively, it is highly suggested to avoid having your field updating their devices to iOS15+ until Apple fixes this change.

Was this answer helpful?

Still have questions?

Available Languages for this Answer:

English (US)

Spanish

Portuguese (Brazil)

Loading...

Login

Was this answer helpful?

Still have questions?

Available Languages for this Answer:

Related Answers

Login