meet.google.com api
Meet Google Play's target API level requirementWhen you upload an APK, it needs to meet Google Plays target API level requirements. New apps and app updates must target Android 10 (API level 29) or higher; except for Wear OS apps, which must target API level 28 or higher. Show
Starting in August 2021, new apps will need to:
Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11. Existing apps that are not receiving updates are unaffected and can continue to be downloaded from the Play Store. Wear OS apps must continue to target API level 28 or higher. The switch to Android App Bundle delivery will also impact instant experiences using the legacy Instant app ZIP format. From August 2021, new instant experiences and updates to existing instant experiences will be required to publish instant-enabled app bundles. Why target newer SDKs?Every new Android version introduces changes that bring significant security and performance improvements as well as enhance the user experience of Android overall. Some of these changes only apply to apps that explicitly declare support through their targetSdkVersion manifest attribute (also known as the target API level). Configuring your app to target a recent API level ensures that users can benefit from these improvements, while still allowing it to run on older Android versions. Targeting a recent API level also allows your app to take advantage of the platform's latest features to delight your users. Furthermore, as of Android10 (API level 29), users see a warning when starting an app for the first time if the app targets Android 5.1 (API level 22) or lower. This document highlights important points you need to know in updating your target API level to meet the Google Play requirement. Note: If your Gradle file contains manifest entries, you can confirm or change the current value of targetSdkVersion in your app's Gradle file, as described in Configure your build. Alternatively, you can use the android:targetSdkVersion attribute in the manifest file, as described in the documentation for the Migrate from Android 10 (API level 29) to Android 11 (API level 30)
For an exhaustive list of changes introduced in Android 11 (API level 30), see the Behavior Changes page. Migrating from lower than Android 10 (API level 29)Select the version of Android you will be migrating from: Migrate to Android 5 (API level 21)See the respective Behavior Changes page for each of the following releases to ensure your that your app has accounted for changes introduced in these releases:
Continue by following the instructions in the next section. Migrate to Android 6 (API level 23)The following considerations apply to apps targeting Android 6.0 and higher versions of the platform: Runtime Permissions Dangerous permissions are only granted at runtime. Your UI flows must provide affordances for granting these permissions. Wherever possible, ensure your app is prepared to handle rejection of permission requests. For example, if a user declines a request to access the device's GPS, ensure your app has another way to proceed. For an exhaustive list of changes introduced in Android 6.0 (API level 23), see the Behavior Changes page for that version of the platform. Continue by following the instructions in the next section. Migrate to Android 7 (API level 24)The following considerations apply to apps targeting Android 7.0 and higher versions of the platform: Doze and App Standby Design for behaviors described in Optimizing for Doze and App Standby, which encompasses incremental changes introduced across several platform releases. When a device is in Doze and App Standby Mode, the system behaves as follows:
Permission Changes
The system forbids linking to non-NDK libraries. For an exhaustive list of changes introduced in Android 7.0 (API level 24), see the Behavior Changes page for that version of the platform. Continue by following the instructions in the next section. Migrate to Android 8 (API level 26)The following considerations apply to apps targeting Android 8.0 and higher versions of the platform:
For an exhaustive list of changes introduced in Android 8.0 (API level 26), see the Behavior Changes page for that version of the platform. Migrating from Android 8 (API 26) to Android 9 (API 28)
For an exhaustive list of changes introduced in Android 9.0 (API level 28), see behavior changes. Migrating from Android 9 (API level 28) to Android 10 (API level 29)
Continue to update to API 30 by following the instructions in the previous section. Modernizing your appsAs you update the target API level for your apps, consider adopting recent platform features to modernize your apps and delight your users.
Check and update your SDKs and librariesMake sure that your third-party SDK dependencies support API 29: Some SDK providers publish it in their manifest; others will require additional investigation. If you use an SDK that doesn't support API 29, make it a priority to work with the SDK provider to resolve the issue. Additionally, note that your app or game's targetSdkVersion may restrict access to private Android platform libraries; see NDK Apps Linking to Platform Libraries for details. You should also verify any restrictions that may exist in the version of the Android Support Library that you're using. As always, you must ensure compatibility between the major version of Android Support Library and your apps compileSdkVersion. We recommend that you choose a targetSdkVersion smaller than or equal to the Support Librarys major version. We encourage you to update to a recent compatible Support Library in order to take advantage of the latest compatibility features and bug fixes. Test your appAfter you update your app's API level and features as appropriate, you should test some core use cases. The following suggestions are not exhaustive, but aim to guide your testing process. We suggest testing:
Further informationOpt in to emails in the Google Play Console so that we can send you important updates and announcements from Android and Google Play, including our monthly partner newsletter. Previous arrow_back Design to drive conversions Next Support 64-bit architectures arrow_forward Content and code samples on this page are subject to the licenses described in the Content License. Java is a registered trademark of Oracle and/or its affiliates. Last updated 2021-10-12 UTC. [{ "type": "thumb-down", "id": "missingTheInformationINeed", "label":"Missing the information I need" },{ "type": "thumb-down", "id": "tooComplicatedTooManySteps", "label":"Too complicated / too many steps" },{ "type": "thumb-down", "id": "outOfDate", "label":"Out of date" },{ "type": "thumb-down", "id": "samplesCodeIssue", "label":"Samples / code issue" },{ "type": "thumb-down", "id": "otherDown", "label":"Other" }] [{ "type": "thumb-up", "id": "easyToUnderstand", "label":"Easy to understand" },{ "type": "thumb-up", "id": "solvedMyProblem", "label":"Solved my problem" },{ "type": "thumb-up", "id": "otherUp", "label":"Other" }] Video liên quan |