Create of a Jetpack Compose project

Help/Discuss
1 
A problem occurred configuring root project 'MyApp'.
> Could not resolve all files for configuration ':classpath'.
   > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.0.
     Required by:
         project : > org.jetbrains.kotlin.android:org.jetbrains.kotlin.android.gradle.plugin:1.9.0
      > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.0.
         > Could not get resource 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.9.0/kotlin-gradle-plugin-1.9.0.pom'.
            > Could not GET 'https://repo.maven.apache.org/maven2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.9.0/kotlin-gradle-plugin-1.9.0.pom'.
               > The server may not support the client's requested TLS protocol versions: (TLSv1.2, TLSv1.3). You may need to configure the client to allow other protocols to be used. For more on this, please refer to https://docs.gradle.org/8.2/userguide/build_environment.html#sec:gradle_system_properties in the Gradle documentation.
                  > PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
      > Could not resolve org.jetbrains.kotlin:kotlin-gradle-plugin:1.9.0.
         > Could not get resource 'https://plugins.gradle.org/m2/org/jetbrains/kotlin/kotlin-gradle-plugin/1.9.0/kotlin-gradle-plugin-1.9.0.pom'.
            > Could not GET 'https://plugins-artifacts.gradle.org/org.jetbrains.kotlin/kotlin-gradle-plugin/1.9.0/45276b09ffbbb8034fbd04708f90f7e31b70d68ae023b2cfb3c11d886e77d836/kotlin-gradle-plugin-1.9.0.pom'.
               > PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

i can’t create a jetpack compose project in android studio, when the packages are in download this error appears.

2

Try running Gradle with a different JDK.
Such HTTPS errors most often are due to corrupt JDK, or missing certificates in the trust store or similar.
It could also be caused by a man-in-the-middle attack actually, but this is rather unlikely.