[[["容易理解","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,["# Android Studio Giraffe | 2022.3.1 (July 2023)\n\nThe following are new features in Android Studio Giraffe.\n\nUse Live Edit to update composables in real time\n------------------------------------------------\n\nLive Edit lets you update composables in emulators and physical devices in real\ntime. Edit composables and see the UI changes on the running device without\nre-deploying your app. This capability minimizes context switches between\nwriting and building your app, letting you focus on writing code longer without\ninterruption. To try Live Edit, use AGP 8.1 or higher and Compose 1.3.0 or\nhigher.\n\nTo learn more, see the [Live Edit documentation](/studio/run#live-edit).\n\nNew UI preview\n--------------\n\nAndroid Studio Giraffe introduces support for the\n[new UI theme](https://www.jetbrains.com/help/idea/new-ui.html)\nfrom IntelliJ. To opt in to this option, go to\n**Android Studio \\\u003e Settings \\\u003e Appearance \\& Behavior**.\n\nThe redesigned theme aims to reduce visual complexity, provide easier access to\nessential features, and disclose complex features as needed --- resulting in\na modern, cleaner look and feel. The key changes are:\n\n- Simplified main toolbar with new **VCS** , **Project** , and **Run** widgets\n- Tool windows have a new layout\n- New Light and Dark color themes with improved contrast and consistent color palettes\n- New icon set for improved legibility\n\nFor a full list of changes, see the\n[IntelliJ new UI documentation](https://www.jetbrains.com/help/idea/new-ui.html).\n\nIf you'd like to provide feedback on the new UI in Android Studio,\n[file a bug](https://issuetracker.google.com/issues/new?component=192708&template=1777729).\n\nNew API support for Compose Animation Preview\n---------------------------------------------\n\n[Compose Animation Preview](/develop/ui/compose/tooling/animation-preview)\nnow also supports\n[`animate*AsState`](/jetpack/compose/animation#animate-as-state),\n[`CrossFade`](/jetpack/compose/animation#crossfade),\n[`rememberInfiniteTransition`](/jetpack/compose/animation#rememberinfinitetransition),\nand [`AnimatedContent`](/jetpack/compose/animation#animatedcontent)\n(in addition to\n[`updateTransition`](/jetpack/compose/animation#updateTransition) and\n[`AnimatedVisibility`](/jetpack/compose/animation#animatedvisibility)). To use\nthese additional APIs with Compose Animation Preview, upgrade to Android Studio\nGiraffe Canary 3 and Compose 1.4.0-alpha04 or higher.\n\nSupport for Grammatical Inflection API\n--------------------------------------\n\nAndroid Studio Giraffe Canary 7 introduces support for the\n[Grammatical Inflection API](/about/versions/14/features#grammatical-inflection)\n(available as of Android 14 Developer Preview 1).\n\nThis new feature lets you personalize the UI for your users by adding\ntranslations inflected based on your user's grammatical gender when required.\nYou can add grammatically masculine, feminine, or neutral translations. When no\ngrammatically inflected translation is provided for a string, Android displays\nthe default translation for the language.\n\nView and manage processes in the Device Explorer\n------------------------------------------------\n\nAndroid Studio Giraffe includes an updated Device Explorer, known as the Device\nFile Explorer in previous versions of Android Studio. In the Device Explorer,\nfiles and related actions are located in the **Files** tab. In the new\n**Processes** tab, view a list of debuggable processes for the connected device.\nFrom there you can also select a process and perform a kill\n,\nforce-stop\n,\nor attach the debugger to a given process\n.\n| **Note:** The options to kill, force-stop, or attach the debugger to a process have moved from Logcat to the Device Explorer.\n\nNew Android SDK Upgrade Assistant\n---------------------------------\n\nStarting with Android Studio Giraffe, see the steps required to upgrade the\n[`targetSdkVersion`](/guide/topics/manifest/uses-sdk-element#target), or\nthe API level that your app targets, directly in the Studio IDE. The Android SDK\nUpgrade Assistant pulls documentation directly into its tool window, so you\ndon't have to jump back and forth between your browser and the IDE.\n\nThe Android SDK Upgrade Assistant helps you save time and effort when updating\nthe `targetSdkVersion`:\n\n- For each migration step, it highlights the major breaking changes and how to address them.\n- It filters the full list of changes to only show steps relevant to your app.\n\n| **Important:** Starting August 31, 2023, all apps must target Android 12 (API level 33) or higher to be submitted to Google Play for review and remain discoverable for all Google Play users. Configuring your app to target a recent API level ensures that users benefit from security and performance improvements while your app can still run on lower Android versions (down to the specified `minSdkVersion`). To learn more, see the [Google Play target API level requirement](/google/play/requirements/target-sdk).\n\nTo open the Android SDK Upgrade Assistant, go to\n**Tools \\\u003e Android SDK Upgrade Assistant** . In the **Assistant** panel, select\nthe API level that you want to upgrade to for guidance. For the best experience,\nyou should upgrade `targetSdkVersion` values one level at a time.\n\nTo help us create the best experience for you,\n[submit feedback and bugs](https://issuetracker.google.com/issues/new?component=1267157&template=1750462).\n\nEnhanced diagnostic tools and bug reporting\n-------------------------------------------\n\nAndroid Studio Giraffe Canary 8 introduces new diagnostic tools that make it\neasier to report bugs with relevant log files attached. To use the new\ndiagnostic report generator, follow these steps:\n\n1. To launch the tool, click **Help \\\u003e Collect Logs and Diagnostic Data**. A dialog appears that lets you choose which files to include.\n2. Check or un-check specific files to include in your diagnostic report. Click a specific file in the menu to see a preview of it.\n3. When you're ready to export the diagnostic report, agree to the terms and click **Create**.\n4. Select the location where you want to save the diagnostic report zip file and click **Save**.\n\nAs part of this enhancement, the bug reporting template\n(**Help \\\u003e Submit feedback**) has also been updated to emphasize the importance\nof attaching log files. If you file a bug, be sure to attach logs because they\nhelp us isolate the issue and are an essential first step to our debugging\nprocess.\n\nMake selected modules toolbar button\n------------------------------------\n\nStarting with Android Studio Giraffe Canary 10, build only the current module\nyou're working on by selecting the **Make Selected Modules** build option in the toolbar. This new option lets you\ncheck that the code you just wrote compiles without building more than needed.\nAlternatively, build your entire project by clicking the arrow next to the build\nbutton and selecting **Make Project**.\n\nDownload info during sync\n-------------------------\n\nThe **Sync** tool window now includes a summary of time spent downloading\ndependencies and a detailed view of downloads per repository. This view updates\nlive as sync takes place. You can use this information to determine whether\nunexpected dependency downloads are negatively impacting your sync performance.\nSince Gradle resolves dependencies by searching through each repository in the\ndeclared order, it's important to list the repository that hosts most\ndependencies at the top of the repository configuration list. Additionally, if\nyou see a high number of failed requests for a specific repository, it could\nindicate that the repository should be removed or moved lower in your repository\nconfiguration.\n| **Note:** Download information is only available if your project uses Gradle version 7.3 or higher.\n\nThis download info is also available during builds in the **Build** tool window\nand\n[Build Analyzer](/studio/build/build-analyzer#download-impact)."]]