iOS SDK overview

With the Tealeaf iOS SDK, you can instrument your native and hybrid iOS applications for logging and analysis. It captures device context and user activity, so you can monitor and evaluate the performance of your applications.

The iOS SDK was designed for simple implementation: it uses standard iOS classes and user interface controls to track user interface events. Even without the framework, Tealeaf can monitor the traffic between your application and your server. With the framework, you get unprecedented insight into the performance of your application.

📘

Note:

For a quick and easy implementation of the Tealeaf SDK in your iOS applications, see the Quick start guide for iOS applications.

Requirements for iOS environments

To develop iOS applications effectively with iOS SDK, follow these system and software requirements:

• Mac OS X 12.x (or later)
• Xcode 13 (or later)

📘

Note:

Apple no longer supports armv6 devices. The framework is compatible with armv7 (or later) devices.

• iOS bitcode is enabled in the iOS SDK and is built in 64-bit with the latest Xcode version for the xcframework library for the following architectures: arm64 and x86_64. By Apple standards, you are not required to turn in x86_64 versions that are used only for simulator testing.
• Consult the Apple iOS Dev Center for the most recent iOS technical documentation and tools.
  Acoustic Tealeaf client frameworks do not support the forwarding of application data to third-party systems. Application data must be forwarded to the server that hosts the native application.
  Tealeaf has passed all Apple Store and Google Play Store regulations. If you encounter an issue with the Tealeaf library that is related to required scanning for Apple Store and Google Play Store, you can work directly with your Tealeaf services representative to resolve the issue.

Supported operating systems

• iOS 12.0 (or later)
• Single window (full screen) iPadOS apps are now supported. Multi-window iPadOS apps are not fully supported in this release. Multi-window iPadOS, and UIScene are not fully supported at this time. The SDK will still capture data on a multi-window iPadOS app (or an app that uses SwiftUI or UIScene), but Session Replay might not work correctly. The recorded data can still be used for analytics and diagnostics.

Supported frameworks

The SDK can be integrated with iOS apps developed with the following frameworks.

Impact on device resources

In benchmark tests, the iOS SDK has the following effects on resources of the visitor's device:

• 2 to 3% more memory consumption

📘

Note:

If the server is unreachable, the SDK saves data to memory until the server is reachable. By default, the SDK will store up to 512,000 bytes to the device memory. If the cache grows larger than 512,000 bytes, the oldest data is truncated from cache and is deleted. The cache size is managed through the CachedFileMaxBytesSize setting in EOCoreAdvancedConfig.json.

• Minimal effect on battery life

📘

Note:

According to Apple, the API used to retrieve the battery level from the device can be out of sync with the value that displays on the device. The value is also updated in 5% increments only. See http://www.iphonedevsdk.com/forum/iphone-sdk-development/14301-battery-level.htmlfor more information.

Environmental data

The framework automatically handles environmental data that is captured when the framework initializes, typically when your application starts, and at regular time intervals during execution. It also provides support for your application to report environmental data that needs special privacy attention or requires special frameworks.

Environmental data can be distributed among multiple hits.

• Data that is captured when the framework initializes generally appears in one of the first hits of a session.
• Data that is captured at regular time intervals appears along with events. Multiple values can be submitted in a single hit where the number of events is low.
• Data that is captured by your application (location and carrier information) can appear at any time, independently or in hits with the other types of environmental data. Multiple values for a single hit can be submitted if your application makes multiple calls to the framework.

Captured at initialization

These values are captured one time per launch of your application when the framework initializes.

Environment data is collected based on a timer. Environment data related to initialization can be, but is not always, submitted on the first hit of the session. As environment data is passed through the framework, it is prioritized based on its logging level. The order that it is posted to the server and even whether it is posted to the server depends on the following.

• Budgets for in-memory and local storage caches
• Network packet size
• The send level for the type of network available to the application

📘

Note:

Data is not posted to the server in the order that it was captured.

Captured during execution

These values are captured at a regular time interval you can set for each logging level with TimeBetweenSnapshots in TLFLevelsConfiguration.plist

📘

Note:

According to Apple, the API used to retrieve the battery level from the device is not always in sync with the value that displays on the device. In addition, the value is updated only in 5% increments. See http://www.iphonedevsdk.com/forum/iphone-sdk-development/14301-battery-level.html for more information.

Guidelines, tips, and best practices

Apply the following tips to your application development and integration of the Acoustic Tealeaf iOS SDK:

• Use the killswitch to control logging of the iOS application
• Add IDs for all UI controls that you want to capture
• Apply privacy masking or blocking of all sensitive customer data through the iOS SDK
• Due to the way JSON messages are captured and transmitted, force a submission of all queued messages before you allow users of your mobile native application to open a web view. If this step is not done, hits can appear to be out of order during replay in Acoustic Tealeaf.
• In some cases, you might want to call TLFApplicationHelper's enableTealeafFramework conditionally. For example, you might want to conditionally make this call when you want to:
  Enable Tealeaf on a range of operating system versions.
  Enable Tealeaf only on iPhones.
  Enable Tealeaf only on iPads.
  Enable Tealeaf on both iPhones and iPads.
  For sample code, refer to the CXA ApplicationisValidOSVersionAndPlatform method in the AppDelegate.m file.

Here are some sample code examples:
Operating system versions

NSOperatingSystemVersion minVer = (NSOperatingSystemVersion)

{11, 0, 0};
NSOperatingSystemVersion maxVer = (NSOperatingSystemVersion){14, 0, 0};
NSOperatingSystemVersion skipVers[2] = {{11, 0, 0}
,{12, 1, 1}};

Devices

if( (currentUIIdiom == UIUserInterfaceIdiomPhone) || (currentUIIdiom == UIUserInterfaceIdiomPad) )

You can use the above code samples to get the version and device lists from your server, or if you find a better way or other improvements, contact Acoustic.