[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-08-26 (世界標準時間)。"],[],[],null,["Use the instructions on this page to upload a validated APK to Google Play.\n\nValidate the proto files\n\nPlace the following files in your APK assets folder under `assets/tuningfork`:\n\n- `dev_tuningfork.proto`\n- `tuningfork_settings.txt`\n- Several `dev_tuningfork_fidelityparams_`\u003cvar translate=\"no\"\u003ei\u003c/var\u003e`.txt` files, in increasing fidelity order\n\nThe validation tool generates binary (`.bin`) serialized protocol buffers of the\nsettings and default fidelity parameters files in the `assets/tuningfork`\ndirectory. The tool itself is located in the `src/tuningfork/tools/validation`\ndirectory.\n\n\nThe validation tool generates binary files\n\nRun the following commands to validate the sample project. Substitute one of the\nfollowing for your operating system (`LOCAL_OS`):\n\n- `mac`\n- `win`\n- `linux-x86`\n\n cd gamesdk/src/tuningfork/tools/validation\n java -jar build/libs/TuningforkApkValidationTool.jar \\\n --tuningforkPath ../../../../samples/tuningfork/insightsdemo/app/src/main/assets/tuningfork \\\n --protoCompiler ../../../../third_party/protobuf-3.0.0/install/\u003cvar translate=\"no\"\u003eLOCAL_OS\u003c/var\u003e/bin/protoc\n\nOutput ending in the following appears: \n\n ...\n\n May 19, 2020 3:42:11 PM com.google.tuningfork.validation.TuningforkApkValidationTool main\n INFO: Tuning Fork settings are valid\n\nFor more information on running the validation tool, see the\n[`validation tool README`](https://android.googlesource.com/platform/frameworks/opt/gamesdk/+/refs/heads/master/src/tuningfork/tools/validation).\n\nReview the integration checklist\n\nBefore uploading your APK to the Google Play Console, do the following:\n\n- Review and, if necessary, update your app's [Privacy Policy](/games/sdk/performance-tuner/custom-engine/enable-api#privacy)\n- Integrate the [Android Frame Pacing library](/games/sdk/frame-pacing) into your project\n- Provide [fidelity parameters](/games/sdk/performance-tuner/custom-engine/define-parameters#annotations-and-fidelity-parameters) and all of your app's [quality levels](/games/sdk/performance-tuner/custom-engine/define-parameters#define-quality-levels)\n- Record when your game is performing [loading events](/games/sdk/performance-tuner/custom-engine/loading-functions)\n- Successfully run the [validation tool](#validate)\n- Run your game in debug mode and validate the output using `logcat` or the Tuning Fork Monitor app\n- Confirm that you and other relevant game engineers have access to Android Vitals in the Google Play Console\n\nUpload and publish\n\nTo receive performance insights, upload your new APK to the\nGoogle Play Console and create a release. You can release on Google Play to\ntest tracks or to your entire user base. For more information on creating a\nrelease, see the\n[Console Help Center documentation](https://support.google.com/googleplay/android-developer/answer/7159011).\n\nOnce you have published your APK, you can receive new performance insights from\nyour users in the Google Play Console under **Android Vitals \\\u003e Performance \\\u003e\nInsights** . For more information, see the\n[Performance insights documentation](https://support.google.com/googleplay/android-developer/answer/9876283)."]]