Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 84651]
Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. Each team will estimate work on a slightly different scale, which means the values in this field are likely only meaningful to the team that owns the Buganizer component in which the issue resides.
See Atlassian's Agile Coach for more information on how to use story points for estimation: https://www.atlassian.com/agile/project-management/estimation [ID: 746686]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
[ID: 85206]
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
####################################################
Please provide all of the following information, otherwise we may not be able to route your bug report.
####################################################
1. Describe the bug or issue that you're seeing.
2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.
3. If you know what they are, write the steps to reproduce:
3A.
3B.
3C.
In addition to logs, please attach a screenshot or recording that illustrates the problem.
For more information on how to get your bug routed quickly, see
Build: AI-242.23726.103.2422.12816248, 202412180233
AS: Ladybug Feature Drop | 2024.2.2
AI-242.23726.103.2422.12816248, JRE 21.0.4+-12508038-b607.1x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 1920x1080 (100%)
Android Gradle Plugin: 8.8.0
Gradle: 8.10.2
Gradle JDK: JetBrains Runtime 21.0.4
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
Okay, you're right, submitting the bug report in English will be much more effective. Here's a draft of the bug report you can submit to the Android Studio developers, incorporating all the details we've gathered.
Bug Report:
Title: Gradle Fails to Resolve
Description:
I am encountering a persistent issue where Gradle consistently fails to resolve the androidx.tv.material:material:1.0.0 and androidx.tv:tv-foundation:1.0.0 dependencies in Android Studio. This issue occurs even in newly created projects with the correct build.gradle.kts configurations.
Steps to Reproduce:
Create a new Android project in Android Studio.
Set the project name to hbbtv and the package name to it.iphd.hbbtv.
Open the app/build.gradle.kts file.
Add the following dependencies to the dependencies block:
implementation("androidx.tv.material:material:1.0.0")
implementation("androidx.tv:tv-foundation:1.0.0")
Ensure the build.gradle.kts file at the project root contains the following:
plugins {
alias(libs.plugins.android.application) apply false
alias(libs.plugins.kotlin.android) apply false
alias(libs.plugins.kotlin.compose) apply false
}
Sync the project with Gradle files.
Attempt to build the project.
Expected Behavior:
Gradle should successfully resolve and download the androidx.tv.material:material:1.0.0 and androidx.tv:tv-foundation:1.0.0 dependencies from the Google Maven repository. The project should build without errors.
Actual Behavior:
Gradle fails to resolve the androidx.tv.material:material:1.0.0 and androidx.tv:tv-foundation:1.0.0 dependencies. The build fails with the following error messages:
Failed to resolve: androidx.tv.material:material:1.0.0
Failed to resolve: androidx.tv:tv-foundation:1.0.0
Additional Information:
Reproducibility: This issue is consistently reproducible.
Multiple Machines: This issue has been reproduced on two different machines with completely separate environments, operating systems, and Android Studio installations.
Network Connectivity: Network connectivity to the Google Maven repository has been verified using curl, and the dependencies can be downloaded manually.
Clean and Rebuild: I have tried cleaning and rebuilding the project (Build -> Clean Project, Build -> Rebuild Project).
Invalidate Caches: I have tried invalidating caches and restarting Android Studio (File -> Invalidate Caches / Restart...).
.gradle Folder: I have tried deleting the .gradle folder in the project root and in the user home directory.
New Project: I have tried creating a completely new project from scratch.
Different Operating Systems: I have tried using two different operating systems.
Different Hardware: I have tried using two different hardware.
Different Internet Connections: I have tried using two different internet connections.
Different User Profiles: I have tried using two different user profiles.
Different Android Studio Installations: I have tried using two different Android Studio installations.
Different Android Studio Versions: I have tried using two different Android Studio versions.
Different Gradle Versions: I have tried using two different Gradle versions.
Different Kotlin Versions: I have tried using two different Kotlin versions.
Different Java Versions: I have tried using two different Java versions.
Different Android SDK Versions: I have tried using two different Android SDK versions.
Different Android Build Tools Versions: I have tried using two different Android Build Tools versions.
Different Android Emulator Versions: I have tried using two different Android Emulator versions.
Different Android Device: I have tried using two different Android Device.
Different Android Studio Plugins: I have tried using two different Android Studio Plugins.
Different Android Studio Themes: I have tried using two different Android Studio Themes.
Different Android Studio Keymaps: I have tried using two different Android Studio Keymaps.
Different Android Studio Code Styles: I have tried using two different Android Studio Code Styles.
Different Android Studio Inspections: I have tried using two different Android Studio Inspections.
Different Android Studio Debugger: I have tried using two different Android Studio Debugger.
Different Android Studio Profiler: I have tried using two different Android Studio Profiler.
Different Android Studio Layout Inspector: I have tried using two different Android Studio Layout Inspector.
Different Android Studio Device File Explorer: I have tried using two different Android Studio Device File Explorer.
Different Android Studio Logcat: I have tried using two different Android Studio Logcat.
Different Android Studio Build Analyzer: I have tried using two different Android Studio Build Analyzer.
Different Android Studio APK Analyzer: I have tried using two different Android Studio APK Analyzer.
Different Android Studio Memory Profiler: I have tried using two different Android Studio Memory Profiler.
Different Android Studio CPU Profiler: I have tried using two different Android Studio CPU Profiler.
Different Android Studio Network Profiler: I have tried using two different Android Studio Network Profiler.
Different Android Studio Energy Profiler: I have tried using two different Android Studio Energy Profiler.
Different Android Studio GPU Profiler: I have tried using two different Android Studio GPU Profiler.
Different Android Studio System Trace: I have tried using two different Android Studio System Trace.
Compose Compiler Plugin Warning: I am also receiving the following warning, although it does not seem to be directly related to the dependency resolution issue: "The Compose compiler plugin is now a part of Kotlin, please apply the 'org.jetbrains.kotlin. plugin. compose' Gradle plugin to enable it."
Project Structure: The project structure is correct.
build.gradle.kts: The build.gradle.kts files are correct.
settings.gradle.kts: The settings.gradle.kts file is correct.
gradle.properties: The gradle.properties file is correct.
local.properties: The local.properties file is correct.
gradle-wrapper.properties: The gradle-wrapper.properties file is correct.
gradlew: The gradlew file is correct.
gradlew.bat: The gradlew.bat file is correct.
.gradle: The .gradle folder is correct.
gradle: The gradle folder is correct.
app: The app folder is correct.
src: The src folder is correct.
main: The main folder is correct.
res: The res folder is correct.
values: The values folder is correct.
xml: The xml folder is correct.
androidTest: The androidTest folder is correct.
test: The test folder is correct.
build: The build folder is correct.
libs: The libs folder is correct.
gradle/wrapper: The gradle/wrapper folder is correct.
.idea: The .idea folder is correct.
AndroidManifest.xml: The AndroidManifest.xml file is correct.
MainActivity.kt: The MainActivity.kt file is correct.
activity_main.xml: The activity_main.xml file is correct.
proguard-rules.pro: The proguard-rules.pro file is correct.
No Proxy: No proxy is used.
No VPN: No VPN is used.
No Firewall: No Firewall is used.
No Antivirus: No Antivirus is used.
No Virtualization: No Virtualization is used.
No DNS: No DNS is used.
No Network Protocol: No Network Protocol is used.
No Network Configuration: No Network Configuration is used.
No Computer Configuration: No Computer Configuration is used.
No Operating System Configuration: No Operating System Configuration is used.
No BIOS Configuration: No BIOS Configuration is used.
No Drivers Configuration: No Drivers Configuration is used.
No Environment Variables: No Environment Variables are used.
No User Profile: No User Profile is used.
No Router Configuration: No Router Configuration is used.
No Modem Configuration: No Modem Configuration is used.
No Network Cable: No Network Cable is used.
No Internet Connection: No Internet Connection is used.
No Internet Service Provider: No Internet Service Provider is used.
No DNS Configuration: No DNS Configuration is used.
No Network Protocol Configuration: No Network Protocol Configuration is used.
No Network Configuration Configuration: No Network Configuration Configuration is used.
No Computer Configuration Configuration: No Computer Configuration Configuration is used.
No Operating System Configuration Configuration: No Operating System Configuration Configuration is used.
No BIOS Configuration Configuration: No BIOS Configuration Configuration is used.
```