After integrating Game Kit, connect your device to the computer and enable the adb debugging function, and run adb logcat –v time > log.txt.
You can view the kit log in the log.txt file with the Game Kit tag.
For the updateGameAppInfo API, if the keyword reportData message is printed in the log, it indicates that the delivery of game information was successful.
For example:
4211 4234 I Game Kit : reportData message {"MessageType":3,"SceneID":1,"Description":"Game Start","ImportantLevel":"2","RecommendFps":60,"KeyThread":"render|10001|logic|6665|net|7170"}
When the temperature reported by the device is high, it is recommended that your app implements an optimization solution, such as lowering the image quality by one level. However, pay attention to the frequency of device temperature feedback as adjusting the image quality repeatedly will also affect the gaming experience.
Also, consider the way in which your app adjusts the image quality. According to our findings, user experience may deteriorate when users receive a notice on reducing the frame rate or image quality.
1. Avoid calling the GameKit API in the main thread.
2. Avoid calling the updateGameAppInfo() API too frequently. The recommended calling interval is greater than 10 ms. Otherwise, the second calling will be filtered out.
3. When the updateGameAppInfo() API is called to send messages to the device, only one message is sent each time. Avoid sending multiple messages in combination.
4. For games that involve matching, send the game matching messages at the beginning and end of a game. Pay particularly close attention to the following scenarios:
During the match, when the user switches between the front end and background, or turns the screen off and on again.
The network is disconnected and then reconnected.
The game is switched to the background, and opened again after a long period of time.
Android Studio is supported.
Currently, only EMUI 10.1 and later versions are supported.