nowinandroid
nowinandroid copied to clipboard
[Bug]: Failed Build
Is there an existing issue for this?
- [X] I have searched the existing issues
Is there a StackOverflow question about this issue?
- [X] I have searched StackOverflow
What happened?
Can't seem to build this with following output
Android Studio Version:
Android Studio Dolphin | 2021.3.1
Build #AI-213.7172.25.2113.9014738, built on September 1, 2022 Runtime version: 11.0.13+0-b1751.21-8125866 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Relevant logcat output
Build file 'D:\ProgramData\Projects\Android\nowinandroid\build.gradle.kts' line: 32
Error resolving plugin [id: 'com.android.application', version: '7.3.1', apply: false]
> A problem occurred configuring project ':build-logic:convention'.
> Could not resolve all files for configuration ':build-logic:convention:classpath'.
> Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.6.21.
Required by:
project :build-logic:convention > org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:2.3.3 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:2.3.3 > org.jetbrains.kotlin:kotlin-gradle-plugin:1.6.21
project :build-logic:convention > org.gradle.kotlin.kotlin-dsl:org.gradle.kotlin.kotlin-dsl.gradle.plugin:2.3.3 > org.gradle.kotlin:gradle-kotlin-dsl-plugins:2.3.3 > org.jetbrains.kotlin:kotlin-sam-with-receiver:1.6.21
> Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin-api:1.6.21.
> Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/1.6.21/kotlin-gradle-plugin-api-1.6.21.pom'.
> Could not HEAD 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin-api/1.6.21/kotlin-gradle-plugin-api-1.6.21.pom'.
> Connect to plugins.gradle.org:443 [plugins.gradle.org/104.18.191.9, plugins.gradle.org/104.18.190.9] failed: Connection timed out: connect
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
The sudden success of the construction may be due to network reason
Was it due to a temporal network issue? If so, could you close the bug?
Looks like a network issue. Feel free to reopen if this isn't the root cause.