Issue
After calling any Nexconn Server API with a new nickname and avatar, why don’t the client’s nickname and avatar update?
-
/v4/auth/access-token/issue -
/v4/user/update
Analysis
Only the name and avatar in push notifications will update.
Push notification nicknames and avatars update
The name and avatarUrl passed when getting or refreshing a Token are only used for mobile remote push notifications. After you request the Nexconn Server API to refresh the Token or update user info, the server receives the new nickname and avatar. Users will see the new nickname in push notifications.
-
Register user: Register a user | Nexconn Documentation
-
Update user info: Update user info | Nexconn Documentation
Client UI components won’t update nicknames and avatars
The nickname and avatar stored in Nexconn’s push service are only used for push notifications. When Nexconn’s client UI components display user info (avatar + name), the data must be provided by the user info provider set by the application. The SDK will request the specified user info from the provider you set.
For clients, refer to: