Skip to content

Latest commit

 

History

History
64 lines (40 loc) · 2.54 KB

CONFIGKEY.md

File metadata and controls

64 lines (40 loc) · 2.54 KB

Common function configuration guide

  • [Offline push function](#Offline push function)

  • [Map function](#Map function)

Offline push function

Currently using the integrated solution.

Client configuration

1. Use Getui (https://getui.com/) in mainland China

Configure iOS in the integration guide of Getui.

iOS platform configuration: Make the corresponding iOS configuration according to its documentation. Then find the following files in the code and modify the corresponding iOS side key:

  fileprivate let kGtAppId = ""
  fileprivate let kGtAppKey = ""
  fileprivate let kGtAppSecret = ""

2. Use FCM (Firebase Cloud Messaging) in overseas regions

According to the integration guide of FCM, replace the following files:

Offline push banner settings

The current SDK design is that the display content of the push banner is directly controlled by the client. When sending a message, set the input parameter offlinePushInfo:

  let offlinePushInfo = OfflinePushInfo(
  title: "Fill in the title",
  desc: "Fill in the description, such as the message content",
  );
  // If you do not customize offlinePushInfo, the title defaults to the app name, and the desc defaults to "You have received a new message"

According to actual needs, complete the corresponding client and server configurations to enable the offline push function.

Map function

Configuration guide

Need to configure the corresponding AMap Key. Please refer to AMap Document for details. The code in the project needs to modify the following Key:

  fileprivate let webKey = "your-web-key"
  fileprivate let webServerKey = "your-web-server-key"

Once the configuration is complete, you can enable the map function.