Troubleshooting guide¶
This explains the problems that may occur when using RTT4U and their solutions.
Missing google-services.json file Error¶
If you see an error indicating that the google-services.json file is missing in the console terminal, please add the google-services.json file to the Assets/ path.
Setting Android target API level¶
Make sure to check if the Resolve was successful after setting it in the Player Settings menu as shown below.
| Before | After |
|---|---|
 |  |
Remove HiveUnityPlayerGameActivity file¶
The HiveUnityPlayerGameActivity file below is only used in Unity version 2023.
If you are using a version of Unity below 2023, please remove the HiveUnityPlayerGameActivity file.
Scene Unspecified error¶
If the Scene is unspecified in RTT Player Settings or Build Settings, an error message like the one below will be displayed in the console terminal. Please specify the Scene in the respective menu and save it.
| RTT 플레이어 설정 | 빌드 설정 |
|---|---|
 |  |
marketConnect failure¶
If you are not logged into the PlayStore in the emulator or if re-verification is required, marketConnect will fail and display an error message like the one below. 
Please check your account information and reconnect.
Other build issues¶
When you perform Build RTT Client, a buildReport.log file will be created. You can check the file creation path using the methods below.
- Select 'Check RTT Client Project Path' from the RTT4U editor menu
- Copy the path printed in the editor console log and navigate to that path
If the log content of the buildReport.log file is as below, it means that the apk creation and processing were successful. 
If the build fails, you can check the corresponding error message in the Unity Editor. For more details, refer to the buildReport.log log file created in the path described above.