// Integrate TUISearchpod 'TUISearch'
pod instal.TUILogin of TUICore to log in to TUIKit. Initialization is implemented inside the login API by default, and no additional call to the initialization API is required.TUILogin.login(SDKAppID, userID: userID, userSig: userSig) {// Login succeededprint("login succeeded")} fail: { code, desc in// Login failedprint("login failed, \\(code): \\(desc)")}
[TUILogin login:SDKAPPID userID:userID userSig:userSig succ:^{// Login succeeded} fail:^(int code, NSString *msg) {// Login failed}];

// initlet searchBar = TUISearchBar()// self.containerView is your own viewself.containerView.addSubview(searchBar)
// initTUISearchBar *searchBar = [[TUISearchBar alloc] init];// self.containerView is your own view[self.containerView addSubview:searchBar];
createCustomMessage:desc:extension API to create and send a custom message, and specify the text to search in the desc parameter.createCustomMessage API to create a custom message, a binary data stream is saved locally, and the custom message cannot be searched.desc parameter, the custom message will also be pushed offline, and the content specified in the desc parameter will be displayed in the notification bar.disablePush parameter in V2TIMOfflinePushInfo of the sendMessage API to disable it.desc parameter in V2TIMOfflinePushInfo to specify the pushed content.fileName parameter as the searched content when creating a file message. If fileName is not set, the system gets the filename from filePath and saves it to both the local device and the server.Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback