CSJ has made major changes to the SDK initialization method in version 3450, supporting both synchronous initialization and asynchronous initialization, and the asynchronous initialization API supported in TTAdConfig.Builder will no longer take effect. After optimization, there is no significant difference in time consumption between synchronous initialization and asynchronous initialization. The latter puts part of the initialization logic in the child thread. If developers use the asynchronous initialization method, please note that they need to request advertisements after the success callback.
Add initialization interface
Important note: If you are accessing the CSJ Pro version of the SDK, you can only use asynchronous initialization. At the same time, the obfuscation rules should be adjusted simultaneously
CSJ SDK initialization API: This API must be called in the main thread, and the CSJ will execute the initialization operation in the child thread.
Initialization error code caused by local execution API error
CSJ SDK initialization method: The API is adjusted to be called in the main thread, and the initialization operation will be executed in the main thread.
Expired & invalid API
Note: AppId is required. If the appid is sent through the server, you need to make a judgment if it is not empty before initialization.
-Need to set isCanUseLocation() before overriding getTTLocation()
-You need to set isCanUsePhoneState() before overriding getDevImei()
Construct TTAdManager object
The TTAdManager object is the entry interface of the entire SDK, which can be used for advertisement acquisition, permission request, version number acquisition, etc.
TTAdManger interface description
Online Customer Service24/7 Online Customer Service BotManual customer service, weekdays 10~ 12 o'clock/14~ 19 o'clock