Mac OS
Please do the following to integrate your application with devtodev:
- 1.Add the application to the Space using the wizard for adding application.
- 2.Download the latest version of the devtodev.framework from the GitHub repository and add it to 'Linked Frameworks and Libraries' list in the general settings of the project.
- 3.Add init method into didFinishLaunchingWithOptions method of your AppDelegate.mApp ID and Secret key can be found in the application settings (Open "Settings" → "SDK" → "Integration").
1
#import "AppDelegate.h"
2
#import <devtodev/DevToDev.h>
3
@interface AppDelegate ()
4
@end
5
@implementation AppDelegate
6
- (void)applicationDidFinishLaunching:(NSNotification *)aNotification {
7
[DevToDev initWithKey:@"appKey" andSecretKey:@"secretKey"];
8
}
9
@end
Copied!
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 a 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 a 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.
1
/**
2
* Method allows to initialize the user. It applies when SDK initialization or user relogin.
3
* @param String activeUserId - unique cross-platform user identifier (max. 64 symbols)
4
*/
5
[DevToDev setUserID:@"activeUserId"];
6
7
/**
8
* Method sets the current user level. Using this method allows to actualize the SDK user data
9
* in game cross-platform applications.
10
* @param NSUInteger level - number of current game level of the user
11
*/
12
[DevToDev setCurrentLevel:level];
13
14
/**
15
* devtodev App Id and Secret key can be found in the devtodev application
16
* settings page ("Settings" → "SDK" → "Integration")
17
*/
18
[DevToDev initWithKey:applicationId andSecretKey:secretKey];
Copied!
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.
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 a user. This identifier will be used until the real cross-platform identifier assigns to the user.
Debug mode
To enable the debug mode and make SDK notifications displayed in the console, use this method:
1
/**
2
* @param BOOL isActive
3
*/
4
[DevToDev setActiveLog: (BOOL) isActive];
Copied!
Last modified 2yr ago
Export as PDF
Copy link
Contents
Debug mode