測試應用程式內更新
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
本導覽說明如何在應用程式中測試應用程式內更新。
使用內部應用程式分享功能進行測試
如要使用內部應用程式分享功能測試應用程式內更新,請執行下列步驟:
確認測試裝置已透過內部應用程式分享網址安裝應用程式,且該應用程式版本可支援應用程式內更新。
按照「Play 管理中心」的操作說明在內部分享應用程式。
上傳應用程式版本,所用版本代碼須高於安裝在測試裝置上的應用程式。
在測試裝置上,按一下更新版應用程式的內部應用程式分享連結,但「不要」安裝點按連結後顯示在 Play 商店頁面中的應用程式。
從裝置的應用程式導覽匣或主畫面中開啟應用程式。您的應用程式現在應該可以進行更新了,您可以測試應用程式內更新的實作情形。
疑難排解
本節針對在測試時,應用程式內更新可能無法如預期運作的情形,提供一些可能的解決方案:
應用程式內更新僅適用於擁有該應用程式的使用者帳戶。請先確認您使用的帳戶已從 Google Play 下載應用程式至少一次,再透過該帳戶測試應用程式內更新。
確認要用來測試應用程式內更新的應用程式,其應用程式 ID 和簽署金鑰與 Google Play 提供的版本相同。
Google Play 只能更新版本代碼更高的應用程式。請確認您要測試的應用程式版本代碼低於要更新的版本代碼。
將應用程式上傳至內部應用程式分享時,系統不支援 inAppUpdatePriority
欄位。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-27 (世界標準時間)。
[[["容易理解","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-07-27 (世界標準時間)。"],[],[],null,["# Test in-app updates\n\nThis guide describes how to test [in-app\nupdates](/guide/playcore/in-app-updates) in your app.\n\nTest with internal app sharing\n------------------------------\n\nUse [internal app\nsharing](https://support.google.com/googleplay/android-developer/answer/9844679)\nto test in-app updates by performing the following steps:\n\n1. Make sure your test device has a version of your app installed that supports\n in-app updates and was installed using an internal app sharing URL.\n\n2. Follow the Play Console instructions to\n [share your app internally](https://support.google.com/googleplay/android-developer/answer/9844679).\n Upload a version of your app that uses a version code that is higher than the\n one you already have installed on the test device.\n\n3. On the test device, click the internal app sharing link for the updated\n version of your app but *do not* install the app from the Play Store page\n that appears after you click the link.\n\n4. Open the app from the device's app drawer or home screen. The update should\n now be available to your app, and you can test your implementation of in-app\n updates.\n\nTroubleshoot\n------------\n\nThis section describes some possible solutions to situations where in-app\nupdates might not work as expected during testing:\n\n- In-app updates are only available to user accounts that own the app. Make\n sure the account that you're using has downloaded your app from Google Play at\n least once before using the account to test in-app updates.\n\n- Make sure that the app that you are using to test in-app updates has the same\n [application ID](/studio/build/configure-app-module#set_the_application_id) and [signing\n key](/studio/publish/app-signing) as the version available from Google Play.\n\n- Google Play can only update an app to a higher version code. Make sure that\n the app that you are testing has a lower version code than the update version\n code.\n\n- The `inAppUpdatePriority` field is not supported when uploading your app to internal app sharing."]]