Log in to the Tuya Developer Platform.

Select the required SDKs or UI BizBundles of v5.x.x.

Select the required SDKs or BizBundles and build your SDK.

After the build is finished, download the SDK to be integrated.

Extract ios_core_sdk.tar.gz and get the following important files:

• Build: stores the security SDK exclusive to your app. This file is as important as the app key information. Keep the file properly and do not disclose the information in it.
• ThingSmartCryption.podspec: used to reference and integrate with App SDK v5.0.

We recommend that you store both files at a sibling directory as podfile, so they can be referenced easily during subsequent development.

Update CocoaPods to the latest version. For more information about CocoaPods, see CocoaPods Guides.

Add the following code block to the Podfile:

source 'https://github.com/tuya/tuya-private-specs.git'
platform :ios, '11.0'

target 'Your_Project_Name' do
    # Build and get ThingSmartCryption from the Tuya Developer Platform.
    # After the official edition is purchased, rebuild the SDK on the Tuya Developer Platform and integrate it into your project.
    # The dot slash (./) notation represents that the files that are obtained after ios_core_sdk.tar.gz is extracted are put at a sibling directory as podfile.
    # To use another directory, change the path to your desired directory.
    pod "ThingSmartCryption", :path =>'./'
    pod "ThingSmartHomeKit"
end

target 'Your_Extension_Target_Name' do
    # Regarding all extension targets, as long as ThingSmartHomeKit is imported, ThingSmartCryption must be imported too.
    pod "ThingSmartCryption", :path =>'./'
    pod "ThingSmartHomeKit"
end

If your app contains extension targets, such as Siri and Widgets, make sure the Podfile is configured correctly.

In the root directory of your project, run pod update.

Import the domain configuration file.

1. Download ThingSmartCryption.xcframework from the platform and place it in the project directory.

2. Replace the t_cdc.tcfg files in the following folders with the t_cdc.tcfg files provided by PM.

3. Run pod install or pod update to install or update dependencies accordingly.

   

Verify the validity of the custom domain name.

You can use this setting [TuyaSmartSDK sharedInstance].debugMode = YES to enable the SDK debug log feature. After the app starts, search for the log entry read custom domain config in the console to check whether data can be read out from the domain configuration file.

If so, disable the SDK debug log feature, repackage the app, and then upload the package to Apple’s App Store to launch the app.

Choose Target > General to open the project settings, and modify Bundle Identifier to the iOS Bundle ID of the app that is registered on the Tuya Developer Platform.

Add the following content to the PrefixHeader.pch file:

#import <ThingSmartHomeKit/ThingSmartKit.h>

Add the following content to the bridging header file xxx_Bridging-Header.h for a Swift project:

#import <ThingSmartHomeKit/ThingSmartKit.h>

Open the AppDelegate.m file and initialize the SDK in [AppDelegate application:didFinishLaunchingWithOptions:].

Modify the Podfile.

target 'Your_Extension_Target_Name' do
    # 1. Regarding all extension targets, as long as ThingSmartHomeKit is imported, ThingSmartCryption must be imported too.
    # 2. Build and get ThingSmartCryption from the Tuya Developer Platform.
    # After the official edition is purchased, rebuild the SDK on the Tuya Developer Platform and integrate it into your project.
    # The dot slash (./) notation represents that the files that are obtained after ios_core_sdk.tar.gz is extracted are put at a sibling directory as podfile.
    # To use another directory, change the path to your desired directory.
    pod "ThingSmartCryption", :path =>'./'
    pod "ThingSmartHomeKit"
end

post_install do | installer |
     installer.pods_project.targets.each do | target |
        target.build_configurations.each do | config |
            config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO'
        end
    end
end

• Configure Target and import components or SDKs into Target as needed.
• Note that ThingSmartCryption must be imported together with the SDK.

Configure AppGroups.

• Grant permissions on AppGroups.
• Before the SDK is initialized, set the App Groups Name for the SDK.
• Only paid developer accounts can be granted permissions on AppGroups. Therefore, free developer accounts cannot be used to debug widget applications.

Configure the AppKey and AppSecret to initialize the SDK.

Before the SDK is initialized with AppKey, set the App Groups Name.

[ThingSmartSDK sharedInstance].appGroupId = APP_GROUP_NAME;
[[ThingSmartSDK sharedInstance] startWithAppKey:SDK_APPKEY secretKey:SDK_APPSECRET];