IssueTracker

Still hitting this problem.

Android Studio Flamingo | 2022.2.1 Canary 5 Build #AI-222.4345.14.2221.9178080, built on October 14, 2022 Runtime version: 17.0.4.1+0-17.0.4.1b469.62-9127311 aarch64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 12.6 GC: G1 Young Generation, G1 Old Generation Memory: 8192M Cores: 10 Registry: external.system.auto.import.disabled=true ide.text.editor.with.preview.show.floating.toolbar=false

Non-Bundled Plugins: idea.plugin.protoeditor (222.4345.14) com.jetbrains.kmm (0.3.4(222-1.7.20-198-IJ)-184)

previously, i was able to work around this by toggling the jdk, it didn't work this time.

But what worked was to rebuild idea.

rm -rf .idea
git checkout .idea

Thank you for this report, definitely, an issue that was reported many times 238369462, 213131387, 188852471 , etc.. about unable to resolve project symbols in the IDE after a successful sync due to a corrupted jdk.table, be able to manually fix it after deleting the table or using a different JDK.

This issue was strictly linked to having a jdk.table entry with a valid homePath but corrupted roots like classPath and sourcePath. Those roots are using absolute path meaning that when updating AS via IntelliJ Toolbox, those aren't properly updated keeping a reference to the old path, for this reason, was more easily reproducible when installing AS via IntelliJ Toolbox due that potentially two different versions of AS may use the same jdk.table file if they are on the same release channel.

<jdk version="2">
   <name value="Embedded JDK" />
   ...
   <homePath value="$APPLICATION_HOME_DIR$/jbr/Contents/Home" />
     <roots>
       <classPath>
          <root url="jrt:///Users/me/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-1/222.4345.14.2221.9252092/Android Studio Preview.app/Contents/jbr/Contents/Home!/java.base" type="simple" />

In any case, this will be fixed on Android Studio F Beta 1 release after having a new mechanism responsible of guarantee that our jdk.table entry used for the project sync is always valid. Please let us know after validate the changes in the described version, thank you.

Thanks for fixing this. Do you happen to know if and when this will be backported to IntelliJ?

This particular fix was applied just on AS because we didn't want to change the current behaviour of IntelliJ, given there exist some internal differences in how JDKs are handling by each IDE. More in particular IntelliJ allow to modify the Project JDK directly by the user but also provides a way to remove a jdk.table entry.

In any case, if you faced the same issue on IntelliJ then the best will be to report this on their end.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Giraffe Canary 1 (2022.3.1.1)
• Android Gradle Plugin 8.1.0

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!