Installation

Getting Started / iOS

Adding the MOVE SDK

Using Cocoapods

CocoaPods is a dependency manager for Swift and Objective-C Cocoa projects. Check out their homepage for more details.

If your project already uses CocoaPods, then add the dependency to your Podfile:

pod 'DolphinMoveSDK'

Run the following command from the terminal:

$ pod install

See also Troubleshooting.

Health Kit Extension

Vesrion 2.15 and above:

In order to allow the Steps service to collect HealthKit data an additional framework is needed.

Make sure to use the DolphinMoveSDKHealth framework with the same version number.

pod 'DolphinMoveSDKHealth'

Swift Package Manager

Add the package with the URL:

https://github.com/dolphin-technologies/MOVE-iOS-Packages

Add the frameworks to the project:

• Go to the General tab of your target settings

• Click the + button under the Frameworks, Libraries, and Embedded Content heading

• Click Add Other and then Add Package Dependency

DolphinMoveSDK added to Libraries.

Version 2.15 and above:

If you are using the steps feature with health kit synchronization, in order to sync data with your AppleWatch or other devices, you also need to embed DolphinMoveSDKHealth. This will use HealthKit, which must be supported by your app's provisioning and requires user permissions, see Permission Handling.

Manual Installation

If you need to install the Framework manually you will have to extract the download link for the zip from the latest Swift Package. If you want to use a specific version refer to the tags in the repository.

1. Download and extract the latest Move SDK XCFramework

2. Add the frameworks to the project ()

   • Go to the General tab of your target settings

   • Click the + button under the Frameworks, Libraries, and Embedded Content heading

   • Click Add Other and then Add Files

   • Choose the Move XCFramework file and click Open

3. Change the Embed option next to the framework to Do Not Embed

Important Notes

For versions bellow 2.3:

When exporting your application archive make sure the manageAppVersionAndBuildNumber option is set to false, otherwise the version numbers of all frameworks (including MoveSDK) included in your application will be overwritten. This can cause issues with migration code since the correct version number is lost.

When building with Fastlane this is done by adding export options to your gym export command, see following code snippet:

gym(
	...
	export_options: {
		manageAppVersionAndBuildNumber: false,
		...
	}
	...
)