上傳應用程式至 Play 管理中心
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
簽署應用程式發布版本後，下一步是將應用程式上傳至 Google Play 進行檢查、測試及發布。在開始之前，請務必遵守下列規定：
符合上述規定後，請將應用程式上傳到 Play 管理中心。
這個頁面也會說明如何在上傳後測試及更新應用程式套件。
使用「最新版本和套件」檢查 APK
如果您將應用程式上傳為 Android App Bundle，Play 管理中心會自動為應用程式支援的所有裝置設定產生分割 APK 和多重 APK。您可以在 Play 管理中心的「最新版本和套件」頁面中，使用「最新套件」部分查看 Google Play 產生的所有 APK 成果，檢查相關資料 (例如支援的裝置和 APK 大小縮減)，並下載產生的 APK 在本機進行部署和測試。
如要查看應用程式套件的詳細資料，請參閱 Play 管理中心的說明主題
使用「最新版本和套件」檢查應用程式版本。
內部測試應用程式
您可以透過下列幾種方式在內部分享應用程式以供測試：
每個工具的優點各有不同，因此請使用最適合您的團隊的工具。
透過 Firebase 應用程式發布功能，您可以部署任何類型的版本，並提供給使用者清單。這是利用持續整合系統發布版本的好做法，也能讓測試人員存取特定版本來測試。
與 Alpha 版或 Beta 版測試群組相比，Play 管理中心內部測試群組的部署速度更快，且提供訂閱、應用程式內購和廣告等服務。這也需要在 Play 管理中心經過簽署與縮減，因此最接近透過 Play 商店發布給使用者的體驗。此外，您可以申請延後 Play 商店審查程序，以免需要等待審核完成才能發布。不過，您必須先完成審核程序，才能將應用程式全面提供給 Play 商店使用者。
更新應用程式套件
將應用程式上傳至 Play 管理中心後，您必須在基本模組中包含更高的版本代碼，然後建構並上傳新的應用程式套件更新應用程式。Google Play 接著會使用新的版本代碼產生新版 APK，並視需要提供給使用者。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。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,["# Upload your app to the Play Console\n\nAfter you [sign the release version of your\napp](/studio/publish/app-signing#sign-apk), the next step is to upload it to\nGoogle Play to inspect, test, and publish your app. Before you get started, you\nmust meet the following requirements:\n\n- If you haven't already done so, [enroll in Play App Signing](/studio/publish/app-signing#enroll), which is the mandatory way to\n upload and sign all new apps since August 2021.\n\n- Ensure that your app meets Google Play's size requirements.\n Google Play supports a cumulative total download size of 4 GB. This size\n includes all modules and install-time asset packs. To learn more, read\n [Google Play maximum size limits](https://support.google.com/googleplay/android-developer/answer/9859372#size_limits).\n\nAfter you've met the preceding requirements, [upload your app to the Play\nConsole](https://support.google.com/googleplay/android-developer/answer/7159011)\n.\n\nThis page also describes how you can test and update your app bundle after it's\nbeen uploaded.\n\nInspect APKs using Latest releases and bundles\n----------------------------------------------\n\nIf you upload your app as an Android App Bundle, the Play\nConsole automatically generates split APKs and multi-APKs for all device\nconfigurations your app supports. In the Play Console, you can use the\n\"Latest bundles\" section in the \"Latest releases and bundles\" page to see all\nAPK artifacts that Google Play generates, inspect\ndata such as supported devices and APK size savings, and download generated APKs\nto deploy and test locally.\n\nTo see more details about your app bundle, see the Play Console help topic\n\n[Inspect app versions with Latest releases and bundles](https://support.google.com/googleplay/android-developer/answer/9006925).\n\nTest your app internally\n------------------------\n\nThere are several ways to share your app internally for testing:\n\n- Upload and distribute your app internally using [Firebase App\n Distribution](https://firebase.com/docs/app-distribution).\n- Upload and distribute your app internally using [Play Console's internal app\n sharing tool](https://play.google.com/console/internal-app-sharing).\n\nEach of these offers slightly different benefits, so use the one that works best\nfor your team.\n\n- Firebase app distribution lets you deploy any kind of build and distribute it\n to a list of users. This can be a good way of distributing builds from a\n continuous integration system so that testers can access specific builds for\n testing.\n\n- Play console internal track is faster to deploy compared to the alpha or beta\n tracks and gives you access to services such as Subscriptions, In-App\n purchases, and ads. This also goes through Play Console signing and shrinking\n so is the closest to what is distributed to end users through the play\n store. It is possible to defer the Play Store review until later to avoid\n having to wait for review to complete. However, the review is required\n before you can fully distribute your app to end-users through the Play Store.\n\nUpdate your app bundle\n----------------------\n\nTo update your app after you upload it to the Play Console, you need to increase\nthe version code included in the base module, then build and upload a new app\nbundle. Google Play then generates updated APKs with new version codes and\nserves them to users as needed."]]
