iOS
Last updated
Last updated
This generation of SDK is deprecated and is no longer supported. Information about the current version can be found here.
Please perform the following actions to integrate your application with devtodev system:
add the application to the Space using the wizard for adding application
download the latest version of devtodev SDK or install via CocoaPods
integrate SDK into your application. The integration may be whether partial or including all the possibilities.
CocoaPods is the easiest way to add devtodev into your iOS project.
Firstly, install CocoaPods using
Create a file in your Xcode project called Podfile and add the following:
Run
in your Xcode project directory. CocoaPods should download and install the devtodev library, and create a new Xcode workspace. Open this workspace in Xcode.
Download the latest version of devtodev SDK from the GitHub repository.
Include devtodev.framework dependency:
Link against the embedded framework:
Add devtodev.framework to the Linked Frameworks and Libraries section.
For the correct SDK functioning add the following frameworks:
Security.framework (Optional)
UIKit.framework (Optional)
UserNotifications (Optional)
StoreKit.framework
AdSupport.framework
Add init method into didFinishLaunchingWithOptions method of your AppDelegate.m
If the application you integrate SDK in is a part of a cross-platform project, then the user data initialization is required. Since the analytics of cross-platform projects is based on an unique user (unlike the usual projects where it is based on device identifiers), you have to:
Set the unique cross-platform user identifier (it will be used for cross-platform project data collection).
Actualize the user data. Mostly it is about game applications where the player has a game level as a characteristic. For such projects, you need to set the current player level.
We recommend you set the user identifier before SDK initialization, otherwise the user identifier from the previous session will be used since the SDK initialization moment till the setUserID method call.
If your cross-platform application is supposed to be used without cross-platform authorization, don't use the setUserID method or use the empty string ("") as the user identifier. SDK will assign the unique identifier to the user. This identifier will be used until the real cross-platform identifier is assigned to the user.
If your application allows user to re-login (changing the user during the working session of application), then the setUserID and setCurrentLevel methods should be called just after the authorization. You don't need to call the SDK initialization one more time.
To enable the debug mode and make SDK notifications displayed in the console use this method: