また、Android Studio では、SDK 作成者からのメモがエディタに直接表示されるようになり、時間を節約できます。推奨バージョンまたはバージョン範囲が利用可能な場合、Android Studio にはクイック修正も含まれます。
また、特定の SDK バージョンに既知のセキュリティの脆弱性がある場合、Android Studio に警告が表示されます。この情報は、アプリ開発中にこれらの問題を検出して対処し、ベスト プラクティスに沿って対応するのに役立ちます。
センサーの機能と値のモック
Android Studio に新しいセンサーパネルが追加されました。これにより、心拍センサーなどの特定のセンサー機能が搭載されているデバイスと搭載されていないデバイスをシミュレートしたり、これらのセンサーに特定のテスト値を設定したりできるようになりました。このパネルを使用して、アプリが異なるセンサー機能を備えたデバイスをどのように処理するかをテストします。このパネルは、特に Wear OS デバイスで健康＆フィットネス アプリをテストする場合に役立ちます。
[[["わかりやすい","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 UTC。"],[],[],null,["# Android Studio Ladybug Feature Drop | 2024.2.2 (January 2025)\n\nThe following are new features in Android Studio Ladybug Feature Drop.\n\nWear Tiles Animation Preview\n----------------------------\n\n[Android Studio Ladybug Canary 2+](/studio/preview)\nnow supports Wear Tile Animation Previews, making it easier than ever to inspect\nand debug your [tile animations](/training/wearables/tiles/animations)\ndirectly within the IDE. This feature builds upon the\n[Wear Tiles Preview](/training/wearables/tiles/preview)\nsupport introduced in Android Studio Koala.\n\nTo get started:\n\n1. Update to Android Studio Ladybug Canary 2 or higher.\n2. Add tiles and tooling libraries:\n 1. Add the dependencies to your app-level `build.gradle.kts` file: \n\n ```kotlin\n # Required for the previews\n debugImplementation(libs.androidx.tiles.tooling)\n implementation(libs.androidx.tiles.tooling.preview)\n # Dependencies needed to build the tiles\n implementation(libs.androidx.tiles)\n implementation(libs.androidx.protolayout)\n implementation(libs.androidx.protolayout.material)\n \n ```\n 2. `libs.versions.toml` file: \n\n ```toml\n [versions]\n tiles = \"1.5.0-alpha01\"\n protolayout = \"1.3.0-alpha01\"\n [libraries]\n androidx-tiles-tooling = { group = \"androidx.wear.tiles\", name = \"tiles-tooling\", version.ref = \"tiles\" }\n androidx-tiles-tooling-preview = { group = \"androidx.wear.tiles\", name = \"tiles-tooling-preview\", version.ref = \"tiles\" }\n androidx-tiles = { group = \"androidx.wear.tiles\", name = \"tiles\", version.ref = \"tiles\" }\n androidx-protolayout = { group = \"androidx.wear.protolayout\", name = \"protolayout-proto\", version.ref = \"protolayout\" }\n androidx-protolayout-material= { group = \"androidx.wear.protolayout\", name = \"protolayout-material\", version.ref = \"protolayout\" }\n androidx-protolayout-expression= { group = \"androidx.wear.protolayout\", name = \"protolayout-expression\", version.ref = \"protolayout\" }\n \n ```\n3. Set up Previews for your Tiles Services. Refer to the [tiles preview guide](/training/wearables/tiles/preview) for detailed instructions. If your tiles include animations, the [Animation\n Preview](/develop/ui/compose/tooling/animation-preview) will automatically appear, allowing you to inspect and debug them.\n\nThis enhancement streamlines your Wear Tile development workflow by providing\na visual and interactive way to fine-tune your tile animations within\nAndroid Studio.\n\nMotion Editor deprecation\n-------------------------\n\nIn the upcoming release, we will be deprecating the\n[Motion Editor](/studio/write/motion-editor) as part of our ongoing transition\nfrom XML to [Jetpack Compose](/compose). Compose offers a more modern and\nefficient approach to building animations, and we encourage developers to start\nusing [Compose Animation Preview](/develop/ui/compose/tooling/animation-preview)\nfor new projects.\n\nNew Gemini in Android Studio features\n-------------------------------------\n\nAndroid Studio Ladybug Feature Drop introduces a number of new Code Editor\nfeatures that use Gemini to help you be more productive. To use these\nfeatures, enable sharing code context with Gemini in your current\nproject.\n\nUse the following links to learn more about these features:\n\n- [Gemini code\n transforms](/studio/preview/gemini/ai-code-completion#gemini-code-transforms)\n- [Generate documentation](/studio/preview/gemini/organize#gen-doc)\n- [Rename with Gemini](/studio/preview/gemini/organize#rename)\n- [Rethink variable names](/studio/preview/gemini/organize#rethink-vars)\n- [Commit message generation](/studio/preview/gemini/organize#suggest-commits)\n\nGoogle Play SDK Index integration\n---------------------------------\n\nThe Android Studio [Google Play SDK Index\nintegration](/build/dependencies#sdk-insights) now includes warnings from\nthe [Google Play SDK Console](https://android-developers.googleblog.com/2024/05/build-better-safer-sdks-google-play-sdk-console.html).\nThis gives you a complete view of any potential version or policy issues in your\ndependencies before submitting your app to the Google Play Console.\n\nAndroid Studio now also displays notes from SDK authors directly in the editor\nto save you time. When a recommended version or version range is available,\nAndroid Studio will also include a quick fix:\n\nAndroid Studio also displays warnings when a specific SDK version has\nknown security vulnerabilities. This information helps you discover and address\nthese issues during app development so you can\nfollow [best practices](/guide/practices/sdk-best-practices).\n\nMock sensor capabilities and values\n-----------------------------------\n\nAndroid Studio now includes a new sensor panel, which lets you simulate a device\nhaving or not having specific sensor capabilities, such as a heart rate sensor,\nas well as set specific test values for these sensors. Use this panel to test\nhow your app handles devices that have different sensor capabilities. This panel\nis useful for testing [health and fitness apps](/health-and-fitness), especially\non Wear OS devices.\nThe **Wear Health Services** panel, available in the emulator.\n\nTo open and use the panel, do the following:\n\n1. Create or open an [Android Virtual Device (AVD)](/studio/run/managing-avds) and [run your app on the emulator](/studio/run/emulator#avd).\n2. In the emulator panel, select **Wear Health Services** . The **Wear Health Services** panel opens, showing a list of sensors that are available on different Android-powered devices.\n\nAfter the panel opens, you can do the following:\n\n- Toggle among **Standard capabilities** , **All capabilities** (default), or **Custom** . Select **Apply** to send the current list of capabilities to the emulated device, and select **Reset** to restore the list of capabilities to their default on-off values.\n- Trigger different user events after you select the **Trigger events** drop-down button. From here, you can **Trigger auto pause/resume** of fitness activities, **Trigger sleep events** by the user, and **Trigger golf shots** that the user takes on a golf course or mini-golf course.\n- Override sensor values, after you begin an exercise in an app that's installed on the emulator. After you enter new values for different exercise metrics, select **Apply** to sync these values with the emulator. This is useful for testing how your app handles different exercise conditions and users' fitness tendencies.\n\nApp Links Assistant: JSON generation and web issue fixes\n--------------------------------------------------------\n\nTo implement App Links, developers need to publish a Digital Asset Links JSON\nfile on their websites to verify ownership of the domain. When the App Links\nAssistant identifies failed web checks, it now creates a JSON file which can fix\nthose failures. This JSON file can be downloaded by the user and subsequently\nuploaded to the respective website to resolve the web check failures.\n\nIn cases where a JSON file already exists, users have the ability to compare the\nexisting and newly-generated JSON files to identify differences.\n\nTo open the App Links Assistant navigate to **Tools \\\u003e App Link Assistant** from\nthe main menu bar.\n\nNotification when run configuration is missing build step\n---------------------------------------------------------\n\nAndroid Studio Ladybug Feature Drop Patch 1 and higher informs you if the\nactive run configuration is missing a \"Gradle-aware Make\" step. If the run\nconfiguration is missing that step, you were probably impacted by a\n[known issue](/studio/known-issues#run-config-missing-gradle) that was\nintroduced in Ladybug Feature Drop Canary 9. To fix this, you can manually\nadd the \"Gradle-aware Make\" step in the \"Before launch\" section of the\nrun configuration settings. You can get there by clicking on\n**Run/Debug Configurations \\\u003e Edit Configurations**."]]
[Wear ヘルスサービス] パネルが開き、さまざまな Android デバイスで利用可能なセンサーのリストが表示されます。