# HarmonyOS Integration

# 1. Obtain Credentials

WARNING

To integrate the SDK, you must first create an application in the FinClip platform and bind a Mini-Program, then obtain the exclusive SDK KEY and SDK SECRET for each application. These parameters can be filled in during the SDK integration process. When opening a Mini-Program, the SDK will automatically initialize and verify whether the SDK KEY, SDK SECRET, and BundleID(Application ID) are correct. You can click here to view how to obtain the required SDK KEY and SDK SECRET. Please ensure that the parameters filled in during SDK integration are correct; otherwise, it may cause the Mini-Program to fail to open.

# 2. Import SDK

Please Note

Note: DevEco Studio must be upgraded to at least version 5.0.3.300, and the mobile system version must be upgraded to at least 3.0.0.22, corresponding to HarmonyOS version: 5.0.0 (12).

# 2.1 Configure SDK

# 2.1.1 Through oh-package.json5 Dependency

Note that the following code needs to be added to the elements in app/products in build-profile.json5 under the root directory of the HarmonyOS project.

"buildOption": {  
  "strictMode": {  
    "useNormalizedOHMUrl": true  
  }  
}
# 2.1.1.1 Online Dependency
  1. Create a .ohpmrc file in the project root directory and add the following content:
registry=https://ohpm.openharmony.cn/ohpm/
@finclip:registry=https://ohpm.finogeeks.com/repos/ohpm
  1. Add dependencies to the dependencies field in the project's oh-package.json5:
"@finclip/sdk": "latest"
  1. Execute ohpm install.
# 2.1.1.2 Local Dependency
  1. The SDK can be downloaded from click here (opens new window), then place the SDK files into the directory within the Host-App project, such as the har directory. The following code paths are for reference only and need to be modified according to the actual directory.

  2. Add dependencies to the dependencies field in the project's oh-package.json5:

"@finclip/sdk": "file:../har/FinClipSDK.har",
"@finclip/contact-sdk": "file:../har/FinClipContactSDK.har",
"@finclip/calendar-sdk": "file:../har/FinClipCalendarSDK.har",
"@finclip/clipboard-sdk": "file:../har/FinClipClipboardSDK.har",
"@finclip/bluetooth-sdk": "file:../har/FinClipBluetoothSDK.har"
  1. Add the following code to the oh-package.json5 file in the project root directory:
"overrides": {
  "@finclip/sdk-core": "file:./har/FinClipSDKCore.har"
}

# 2.1.2 Configuration in module.json5

TIP

If starting without Ability, this step can be skipped.

Due to restrictions on HarmonyOS, shared packages cannot register Abilities, so the Host-App needs to register Abilities for use by the FinClip SDK. Reference code for registration is provided below, which can be modified according to HarmonyOS documentation (opens new window).

{  
  "name": "AppletAbility",
  "srcEntry": "./ets/appletAbility/AppletAbility.ets",
  "description": "$string:EntryAbility_desc",  
  "icon": "$media:app_icon",  
  "launchType": "specified", 
  "label": "$string:EntryAbility_label",  
  "startWindowIcon": "$media:app_icon",  
  "startWindowBackground": "$color:start_window_background",  
  "exported": true,  
  "removeMissionAfterTerminate": true
}

# Key Field Description

Field Description
name Custom Ability name, used during SDK initialization
srcEntry Default ets file can be retained, and can be modified according to the business logic of the Host-App
launchType It is recommended to use specified, which allows multiple Mini-Programs to be opened simultaneously without repeated creation. For more details, refer to HarmonyOS documentation (opens new window)
removeMissionAfterTerminate Setting to true ensures that stopped Mini-Programs do not appear in the task list after stopping.

# Specific Configuration Method for launchType: "specified"

  1. In module.json5, configure ./ets/myabilitystage/MyAbilityStage.ts in module.srcEntry. The filename and location can be customized. The following instructions will use this path as an example.
  2. The content of MyAbilityStage.ts can refer to the following code:
import AbilityStage from '@ohos.app.ability.AbilityStage';  
  
export default class MyAbilityStage extends AbilityStage {  
  onCreate() {  
    // Application's HAP initializes operations for this Module when loaded for the first time  
  }  
  
  onAcceptWant(want): string {  
    if (want.abilityName === 'AppletAbility') { // Custom Ability name configured by the host
      // The returned string key identifies custom concatenated string content  
      // Here, you can get some data at startup via want.parameters.request, it is recommended to use sign as the unique identifier for the Mini-Program
      return `ControlModule_AppletAbilityInstance_${want.parameters.request.sign}`;  
    }  
  
    return '';  
  }  
}

# Ability Reference Code

import { FinAppClient } from '@finclip/sdk';
import UIAbility from '@ohos.app.ability.UIAbility';
import window from '@ohos.window';

export default class AppletAbility extends UIAbility {
  onCreate() {

  }

  onDestroy() {
  }

  async onWindowStageCreate(windowStage: window.WindowStage) {
    const client = FinAppClient.getInstance()
    await client?.initContext(this.context, windowStage, this.launchWant.parameters)
  }


  async onWindowStageDestroy() {
  }

  onForeground() {
  }

  onBackground() {
  }
}

# 2.2 Permissions Involved in the SDK

If you integrate all SDKs, the permissions involved include: storage, camera, recording, reading phone status, location, Bluetooth, contacts. These permissions are triggered only when calling the corresponding APIs and components.

Permission Permission Name Involved API
Network Request ohos.permission.INTERNET request, uploadFile, downloadFile, etc.
Location ohos.permission.APPROXIMATELY_LOCATION, ohos.permission.LOCATION, ohos.permission.LOCATION_IN_BACKGROUND getLocation, startLocationUpdate, startLocationUpdateBackground, etc.
Network Information ohos.permission.GET_NETWORK_INFO, ohos.permission.GET_WIFI_INFO, ohos.permission.SET_WIFI_INFO getSystemInfo, getNetworkInfo, etc.
Bluetooth Information ohos.permission.ACCESS_BLUETOOTH getSystemInfo, Bluetooth-related APIs, etc.
Media ohos.permission.WRITE_IMAGEVIDEO, ohos.permission.MICROPHONE, ohos.permission.CAMERA saveImageToPhotosAlbum, Camera-related APIs, etc.
Sensors ohos.permission.ACCELEROMETER, ohos.permission.GYROSCOPE, ohos.permission.VIBRATE enableAccelerometer, enableDeviceMotion, enableGyroscope, enableCompass, vibrateShort, vibrateLong, etc.
Contacts ohos.permission.WRITE_CONTACTS, ohos.permission.READ_CONTACTS addPhoneContact, etc.
Privacy Window ohos.permission.PRIVACY_WINDOW setVisualEffectOnCapture, etc.
Background Playback ohos.permission.KEEP_BACKGROUND_RUNNING BackgroundAudioManager, etc.
Clipboard ohos.permission.READ_PASTEBOARD getClipboardData
Calendar ohos.permission.READ_CALENDAR, ohos.permission.WRITE_CALENDAR addPhoneCalendar, addPhoneRepeatCalendar

The permissions involved in each SDK are as follows (you can choose to integrate based on actual needs):

Permissions involved in the core SDK:

Permission Permission Name Involved API
Network Request ohos.permission.INTERNET request, uploadFile, downloadFile, etc.
Location ohos.permission.APPROXIMATELY_LOCATION, ohos.permission.LOCATION, ohos.permission.LOCATION_IN_BACKGROUND getLocation, startLocationUpdate, startLocationUpdateBackground, etc.
Network Information ohos.permission.GET_NETWORK_INFO, ohos.permission.GET_WIFI_INFO, ohos.permission.SET_WIFI_INFO getSystemInfo, getNetworkInfo, etc.
Media ohos.permission.MICROPHONE, ohos.permission.CAMERA Camera-related APIs, etc.
Sensors ohos.permission.ACCELEROMETER, ohos.permission.GYROSCOPE, ohos.permission.VIBRATE enableAccelerometer, enableDeviceMotion, enableGyroscope, enableCompass, vibrateShort, vibrateLong, etc.
Privacy Window ohos.permission.PRIVACY_WINDOW setVisualEffectOnCapture, etc.
Background Playback ohos.permission.KEEP_BACKGROUND_RUNNING BackgroundAudioManager, etc.

Note

When recording video, the system will access camera and microphone permissions sequentially.

Permissions involved in the extended Bluetooth SDK:

Permission Permission Name Involved API
Bluetooth Information ohos.permission.ACCESS_BLUETOOTH getSystemInfo, Bluetooth-related APIs, etc.

Permissions involved in the extended Contacts SDK:

Permission Permission Name Involved API
Contacts ohos.permission.WRITE_CONTACTS, ohos.permission.READ_CONTACTS addPhoneContact, etc.

Permissions involved in the extended Clipboard SDK:

Permission Permission Name Involved API
Clipboard ohos.permission.READ_PASTEBOARD getClipboardData

Permissions involved in the extended Calendar SDK:

Permission Permission Name Involved API
Calendar ohos.permission.READ_CALENDAR, ohos.permission.WRITE_CALENDAR addPhoneCalendar, addPhoneRepeatCalendar

Permissions involved in the extended Baidu Map SDK:

Permission Permission Name Involved API
Location ohos.permission.APPROXIMATELY_LOCATION, ohos.permission.LOCATION, ohos.permission.LOCATION_IN_BACKGROUND Map component, chooseLocation, choosePoi, etc.

Permissions involved in the extended Amap SDK:

Permission Permission Name Involved API
Location ohos.permission.APPROXIMATELY_LOCATION, ohos.permission.LOCATION, ohos.permission.LOCATION_IN_BACKGROUND, ohos.permission.KEEP_BACKGROUND_RUNNING Map component, chooseLocation, choosePoi, etc.

Permissions involved in the extended Album SDK:

Permission Permission Name Involved API
Media ohos.permission.WRITE_IMAGEVIDEO saveImageToPhotosAlbum related APIs, etc.

Permissions involved in the extended Live Streaming SDK:

Permission Permission Name Involved API
Media ohos.permission.MICROPHONE, ohos.permission.CAMERA live-pusher component

Permission Configuration Method

Add corresponding permissions to module.requestPermissions in the module.json5 file; otherwise, functions may not work properly. Refer to the following code:

"requestPermissions": [  
  {  
    "name": "ohos.permission.INTERNET"  // Network permission; if not configured, SDK startup will fail
  },  
  {  
    "name" : "ohos.permission.APPROXIMATELY_LOCATION",  
    "usedScene": {
      "when":"inuse"  
    }  
  }  
],

# 3. SDK Initialization

We strongly recommend initializing the SDK in the onWindowStageCreate method of the EntryAbility (the entry Ability of the Host-App). The parameters required for initializing the SDK are as follows (SDK initialization only needs to be called once, and repeated calls should be avoided):

# 3.1 Configuration Information for the Mini-Program Framework

Supports configuring multiple server information entries, allowing Mini-Programs from different environments to be opened simultaneously. The configuration parameters are as follows:

import { IFinAppConfig } from '@finclip/sdk';

const finStoreConfigs: IFinAppConfig.IStoreConfig[] = [
	{  
	  apiServer: 'Address of Server 1',  
	  sdkKey: 'SDK Key Information',  
	  sdkSecret: 'SDK Secret Information',
	  apmServer: 'Data Reporting Server Address for Server 1',
	  cryptType: 'Encryption Method'
	},
	{  
	  apiServer: 'Address of Server 2',  
	  sdkKey: 'SDK Key Information',  
	  sdkSecret: 'SDK Secret Information',
	  apmServer: 'Data Reporting Server Address for Server 2',
	  cryptType: 'Encryption Method'
	}
]

# 3.2 Initialize the SDK

Call the initialization interface to initialize the SDK:

import { FinAppClient,IFinAppConfig } from '@finclip/finclip-sdk';

const finAppConfig: IFinAppConfig.IFinAppConfig = {  
  finStoreConfigs
}

const startMode: IFinAppStartMode = {
  startMode: EAppletStartMode.Ability,
  uiContext: this.getUIContext()
}

const client = FinAppClient.init(  
  finAppConfig,  
  context:this.context,  
  entryInfo:'AppletAbility',  
  startMode
)

The SDK will launch a separate Ability to run the Mini-Program.

Example code:

import { FinAppClient,IFinAppConfig } from '@finclip/finclip-sdk';

const finAppConfig: IFinAppConfig.IFinAppConfig = {  
  finStoreConfigs
}

const startMode: IFinAppStartMode = {
  startMode: EAppletStartMode.Ability,
  uiContext: this.getUIContext()
}

const client = FinAppClient.init(  
  finAppConfig,  
  context:this.context,  
  entryInfo:'AppletAbility',  
  startMode // This parameter can be omitted if launching the Mini-Program with Ability
)

Minimum supported version: 1.1.0

The SDK uses the Host-App's NavPathStack to open the Mini-Program. For more details, refer to the official documentation (opens new window). Using this method allows skipping step 2.1.2.

Example code:

import { FinAppClient,IFinAppConfig } from '@finclip/finclip-sdk';

const finAppConfig: IFinAppConfig.IFinAppConfig = {  
  finStoreConfigs
}

const startMode: IFinAppStartMode = {
  startMode: EAppletStartMode.Navigation,
  routerState: new NavPathStack(), // This parameter must pass the Host-App's NavPathStack; otherwise, the Mini-Program cannot be opened
  uiContext: this.getUIContext()
}

const client = FinAppClient.init(  
  finAppConfig,  
  context:this.context,  
  entryInfo:'AppletAbility',  // If launching the Mini-Program with Navigation, this parameter can be passed as ''
  startMode
)

Complete page code:

import common from '@ohos.app.ability.common';
import { EAppletStartMode, FinAppClient, IFinAppConfig, IFinAppStartMode } from '@finclip/sdk';

@Entry
@Component
struct Index {
  @State pageInfos: NavPathStack = new NavPathStack()
  context = getContext(this) as common.UIAbilityContext
  client?: FinAppClient
  @State appId: string = ''appId
  @State apiServer: string = 'apiServer'

  initFinAppClient() {
    const finAppConfig: IFinAppConfig.IFinAppConfig = {
      finStoreConfigs: [{
        apiServer: 'apiServer',
        sdkKey: 'sdkKey',
        sdkSecret: 'sdkSecret',
        apmServer: 'apmServer'
      }]
    }
    const startMode: IFinAppStartMode = {
      startMode: EAppletStartMode.Navigation,
      routerState: this.pageInfos,
      uiContext: this.getUIContext()
    }
    this.client = FinAppClient.init(
      finAppConfig,
      this.context,
      '',
      startMode
    )
  }

  async startApplet(appid: string, apiServer: string) {
    await this.client?.startApplet({
      appId: appid,
      apiServer: apiServer,
    })
  }

  @Builder
  PageMap(name: string) {
    // Host-App routing...
  }

  build() {
    Navigation(this.pageInfos) {
      Button('Initialize Mini-Program').onClick(() => {
        this.initFinAppClient()
      })
      Button('Open Mini-Program').onClick(() => {
        this.startApplet(this.appId, this.apiServer)
      })
    }
    .mode(NavigationMode.Stack)
    .id('root')
    .title('Home Page')
    .navDestination(this.PageMap)
  }
}

Minimum supported version: 1.1.0

The SDK opens the Mini-Program in the form of a Page. Since it is implemented based on HarmonyOS's router, there are certain functional limitations, and Huawei's official documentation does not recommend this approach. Refer to the official documentation (opens new window). Using this method allows skipping step 2.1.2.

Example code:

import { FinAppClient,IFinAppConfig } from '@finclip/finclip-sdk';

const finAppConfig: IFinAppConfig.IFinAppConfig = {  
  finStoreConfigs
}

const startMode: IFinAppStartMode = {
  startMode: EAppletStartMode.Router,
  uiContext: this.getUIContext()
}

const client = FinAppClient.init(  
  finAppConfig,  
  context:this.context,  
  entryInfo:'AppletAbility',  // If launching the Mini-Program with Router, this parameter can be passed as ''
  startMode
)

# 3.2.4 Differences Between Navigation and Router Launch Methods

  • For specific routing differences, refer to the official documentation (opens new window).
  • The Router launch method may not behave as expected when opening a Mini-Program within another Mini-Program.
  • The Mini-Program-to-APP scenario does not support launching via Router.

# 3.2.5 Notes

  1. The launch method can only be set during initialization, and the initialization method cannot be called repeatedly to update it. Modifying it may lead to unexpected issues.
  2. Since both Navigation and Router methods run on the Host-App's window, it is recommended to set a full-screen layout for a better experience. Refer to the official documentation (opens new window).

# 4. SDK Usage Examples

# 4.1 Launching a Mini-Program

After publishing a Mini-Program on the platform, we can open it by calling the Mini-Program launch interface in the SDK. The code to launch a Mini-Program is as follows:

client.startApplet({  
  appId: 'Mini-Program appId',  
  apiServer: 'Server address'
})

If you need to pass startup parameters when launching a Mini-Program, you can call an interface that supports passing startup parameters, as shown below:

client.startApplet({  
  appId: 'Mini-Program appId',  
  apiServer: 'Server address', 
  startParams: {  
	path:'/pages/index/index',
    query: "aaa=test&bbb=123"  
  }  
})

# 5. Map Integration

Currently, the HarmonyOS SDK uses Huawei's Map Kit for map-related functionality. When using features such as openLocation, chooseLocation, or the Map Component, the integrator must enable map services and configure the project according to the documentation (opens new window) for the map to display correctly.

If a third-party map SDK is not used, the default HarmonyOS system map will be used.

# 5.1 Baidu Map

Supported from version 1.2.3, based on Baidu Map SDK 1.2.8 Integration Method:

"@finclip/baidu-map-sdk": "latest" 

Interface Definition:

class FinAppletBaiduMap {
  /**
   * Initialize the Baidu Map SDK and register components
   * @param api_key API key obtained from the platform
   */
  static init(api_key: string)

  /**
   * Set the coordinate type to be used
   * @param coordType Map coordinate system
   */
  static setBDMapCoordinateType(coordType: CoordType)

  /**
   * Get the currently used coordinate type
   */
  static getBDMapCoordinateType():CoordType

  /**
   * Register components
   */
  static registerComponent()
}

Sample Code:

# 5.1.1 Quick Start

import { FinAppletBaiduMap } from '@finclip/baidu-map-sdk';

// This will initialize the Baidu Map SDK and register map components
FinAppletBaiduMap.init('api_key')

# 5.1.2 Register Components Only

import { FinAppletBaiduMap } from '@finclip/baidu-map-sdk';

// If the Baidu Map has already been initialized in the project, you can just register the map components
FinAppletBaiduMap.registerComponent()

# 5.1.3 Modify Coordinate System

The CoordType provided by the Map SDK is exported from @bdmap/base. For specific definitions, refer to Baidu Map Documentation (opens new window)

import { FinAppletBaiduMap, CoordType } from '@finclip/gd-map-sdk';

// You can use the API to modify the Baidu Map coordinate system
FinAppletBaiduMap.setBDMapCoordinateType(CoordType.GCJ02)

# 5.2 AMap (Gaode Map)

Supported starting from version 1.4.2, based on AMap SDK 2.2.8

Integration Method:

"@finclip/gd-map-sdk": "latest" 

Interface Definition:

class FinAppletGDMap {
  /**
   * Initialize the AMap SDK and register components
   * @param api_key API key obtained from the platform
   */
  static init(api_key: string)
  
  /**
   * Update whether the app displays a privacy pop-up window, and whether the pop-up contains the AMap SDK privacy agreement content. Note: Must be called before instantiating AMapLocationManager.
   * @param showStatus Privacy pop-up status
   * @param containStatus Contains AMap SDK privacy agreement status
   * @param context: Context
   */
  static updateLocationPrivacyShow(showStatus: AMapPrivacyShowStatus, containStatus: AMapPrivacyInfoStatus, context: Context)

  /**
   * Update the user's authorization of the AMap SDK privacy agreement. Note: Must be called before instantiating AMapLocationManager.
   * @param agreeStatus User authorization of the AMap SDK privacy agreement status
   */
  static updateLocationPrivacyAgree(agreeStatus: AMapPrivacyAgreeStatus, context: Context)

  /**
   * Update privacy compliance status, needs to be completed before initializing the map
   * @param containStatus: Whether the privacy policy includes the AMap Open Platform privacy policy
   * @param showStatus: Whether the privacy policy is displayed in a pop-up window to inform users
   * @param context: Context
   */
  static updateSearchPrivacyShow(showStatus: AMapPrivacyShowStatus, containStatus: AMapPrivacyInfoStatus, context: Context)

  /**
   * Update the agreed privacy status, needs to be completed before initializing the map
   * @param agreeStatus: Whether the privacy policy has obtained user consent
   * @param context: Context
   */
  static updateSearchPrivacyAgree(agreeStatus: AMapPrivacyAgreeStatus, context: Context)

  /**
   * Register components
   */
  static registerComponent()
}

Sample Code:

# 5.2.1 Update Privacy Agreement Status

If the AMap privacy agreement has already been updated, this step can be skipped.

import { FinAppletGDMap, AMapPrivacyAgreeStatus,  AMapPrivacyInfoStatus,  AMapPrivacyShowStatus } from '@finclip/gd-map-sdk';
FinAppletGDMap.updateLocationPrivacyShow(
  AMapPrivacyShowStatus.DidShow,
  AMapPrivacyInfoStatus.DidContain,
  this.context)
FinAppletGDMap.updateLocationPrivacyAgree(
  AMapPrivacyAgreeStatus.DidAgree,
  this.context
);
// Search SDK privacy policy
FinAppletGDMap.updateSearchPrivacyShow(
  AMapPrivacyShowStatus.DidShow,
  AMapPrivacyInfoStatus.DidContain,
  this.context
);
FinAppletGDMap.updateSearchPrivacyAgree(
  AMapPrivacyAgreeStatus.DidAgree,
  this.context
);

# 5.2.2 Quick Start

import { FinAppletGDMap} from '@finclip/gd-map-sdk';

// This will initialize the AMap SDK and register map components
FinAppletGDMap.init('api_key')

# 5.2.3 Register Components Only

import { FinAppletGDMap } from '@finclip/gd-map-sdk';

// If AMap has already been initialized in the project, you can just register the map components
FinAppletGDMap.registerComponent()

# 6. Extension SDK

Quick integration instructions for using the extension SDK. For detailed usage, refer to the above SDK Integration.

Please Note

Note: When using the extension SDK, ensure that its version number matches the core SDK to avoid unknown issues.

# 6.1 Bluetooth SDK

After version 1.1.4, it was split into an extension SDK

If you need to use Bluetooth functionality in Mini-Programs, you can introduce the Bluetooth extension SDK with quick integration:

"@finclip/bluetooth-sdk": "latest"

Then initialize the Bluetooth extension SDK before initializing the SDK:

import { FinAppletBluetooth } from '@finclip/bluetooth-sdk';

FinAppletBluetooth.init()

# 6.2 Contact Extension SDK

After version 1.1.4, it was split into an extension SDK

If you need to use addPhoneContact to add phone contacts in Mini-Programs, you can introduce the contact SDK with quick integration:

"@finclip/contact-sdk": "latest"

Then initialize the contact extension SDK before initializing the SDK:

import { FinAppletContact } from '@finclip/contact-sdk';

FinAppletContact.init()

# 6.3 Clipboard Extension SDK

After version 1.1.4, it was split into an extension SDK

If you need to use clipboard functionality in Mini-Programs, you can introduce the clipboard SDK with quick integration:

"@finclip/clipboard-sdk": "latest"

Then initialize the clipboard extension SDK before initializing the SDK:

import { FinAppletClipboard } from '@finclip/clipboard-sdk';

FinAppletClipboard.init()

# 6.4 Calendar Extension SDK

Supported after version 1.1.4

If you need to use calendar functionality in Mini-Programs, you can introduce the calendar SDK with quick integration:

"@finclip/calendar-sdk": "latest"

Then initialize the calendar extension SDK before initializing the SDK:

import { FinAppletCalendar } from '@finclip/calendar-sdk';

FinAppletCalendar.init()

# 6.5 Album Extension SDK

Supported after version 1.3.3

If you need to use ACL to save to the album functionality in Mini-Programs, you can introduce the album SDK with quick integration:

"@finclip/album-sdk": "latest"

Then initialize the calendar extension SDK before initializing the SDK:

import { FinAppletAlbum } from '@finclip/album-sdk';

FinAppletAlbum.init()

# 6.6 Live Streaming Extension SDK (live SDK)

Supported after version 1.3.3

If you need to use live streaming functionality in Mini-Programs, you can introduce the live SDK with quick integration:

"@finclip/live-sdk": "latest"

Then initialize the live extension SDK before initializing the SDK:

import { FinAppletLive } from '@finclip/live-sdk';

FinAppletLive.init()

# 6.7 Share Extension SDK

Supported after version 1.3.6

Please Note

When using the share extension SDK, you need to set hideShareAppletMenu in uiConfig to false to display the share button in the more menu.

If you need to use sharing functionality in Mini-Programs, you can introduce the share SDK with quick integration:

"@finclip/share-sdk": "latest"

Then initialize the share extension SDK before initializing the SDK:

import { FinAppletShare } from '@finclip/share-sdk';

FinAppletShare.init('wxAppId','scheme')
© FinClip with ❤ , Since 2017