IssueTracker

I believe you've been looking into this

        at com.android.tools.idea.gradle.project.sync.idea.SdkSyncUtil.findMatchingSdkForAddon(SdkSyncUtil.kt:175)
        at com.android.tools.idea.gradle.project.sync.idea.SdkSyncUtil.computeSdkReloadingAsNeeded(SdkSyncUtil.kt:127)

hm, in fact let's discuss how we handle SDKs/addons etc. and also bootlclasspath. We have an open issue with not supporting useLibrary which we need to fix.

The issue seems to be in

// Find the path to the android.jar, so we can match this to the sdks and find which one is in use.
  val androidJarPath = bootClasspath.map { path ->
    File(path)
  }.firstOrNull { file ->
    file.name == FN_FRAMEWORK_LIBRARY
  } ?: return null

  // There is no android.jar file in the bootClasspath, we can't find the SDK
  // TODO: Maybe log here, this condition should never happen AFAIK.

  return allAndroidSdks.first { sdk ->
    sdk.rootProvider.getFiles(CLASSES).any { sdkFile ->
      filesEqual(virtualToIoFile(sdkFile), androidJarPath)
    }
  }

i.e. it seems that android.jar from the bootclasspath (as reported by AGP) is not found in any of Android SDKs registered with the IDE.

Al, do you modify bootclasspath for you project in some way? Also, can you please share a small project that reproduces the issue?

Bradley, you made some changes in this area in the past, does this ring a bell?

This is probably caused by https://issuetracker.google.com/238235638. Are you adding a custom SDK? If so, allAndroidSdks will be empty, and even though there is file with name android.jar in bootclasspath, the code above will fail?