Scenario 1: Independent Use of the Push Service
Scenario 2: Integrated with IM Service, Also Need to Push Service
Integrate products such as Chat, CallKit, RoomKit, and LiveKit. The Push service is required to make offline messages reachable. Refer to the "Chat Interaction - Manufacturer Configuration & Quick Connection" documentation guide to complete the configuration and access process. Scenario 3: Require Device-Level Login-Free Push in the Case of Mixed Use of IM and Push
Integrate products such as Chat, CallKit, RoomKit, and LiveKit. Before users log in to the IM account, device-level login-free push can be achieved; after users log in to the IM account, userID push can also be specified.
2. After logging in to the IM account, please refer to registerPush to complete the push registration, so as to achieve the push for the specified userID. If you log in using the login interface provided by TUILogin in the TUICore component, the plug-in will automatically perceive and register the push service. Manual invocation is not required. If you do not use the interface provided by TUILogin, please call this API after successful IM log-in and set the appKey parameter to null. Notes:
1. RegistrationID is the unique identifier of the push reception device. This ID is automatically generated when the push service is successfully registered and will change if the device is uninstalled and reinstalled.
2. Do not use the RegistrationID obtained through getRegistrationID for IM account login. This will break the authenticity of the registrationID and cause a feature exception.