Transfer Android Studio project from Windows to Mac
This page tracks known issues with Android Studio Dolphin | 2021.3.1 and Android Gradle plugin 7.3.0. If you experience an issue not already included here, please report a bug. Show
Upgrade to preview: Each release of Android Studio and the Android Gradle plugin aims to improve stability and performance, and add new features. To experience the benefits of upcoming releases now, download and install Android Studio Preview. Known Issues with Android StudioThis section describes known issues that exist in the latest stable version of Android Studio. Error when rendering Compose PreviewStarting with Android Studio Chipmunk, if
you're seeing If you're seeing If you're seeing Error when using different passwords for key and keystoreStarting with version 4.2, Android Studio now runs on JDK 11. This update causes an underlying behavior change related to signing keys. When you navigate to Build > Generate Signed Bundle / APK and attempt to configure app signing for an app bundle or an APK, entering different passwords for the key and keystore may result in the following error:
To work around this issue, enter the same password for both the key and keystore. Android Studio doesn’t start after installing version 4.2Studio tries to import previous .vmoptions and sanitize them to work with the garbage collector used by JDK 11. If that process fails, the IDE may not start for certain users who set custom VM options in the .vmoptions file. To work around this issue, we recommend commenting out custom options in .vmoptions (using the “#” character). The .vmoptions file can be found in the following locations: Windows
macOS
Linux
If Studio still doesn't start after trying this workaround, see Studio doesn't start after upgrade below. Apps using Database Inspector crash on Android 11 emulatorApps using the Database Inspector may crash when running on the Android 11 emulator, with an error like the following appearing in logcat:
To fix this issue, upgrade your Android 11 emulator to version 9 or higher by navigating to Tools > SDK Manager. In the SDK Platforms tab, check the box labeled Show Package Details and select revision 9 or higher of the Android 11 emulator. Studio doesn't start after upgradeIf Studio doesn't start after an upgrade, the problem may be due to an invalid Android Studio configuration imported from a previous version of Android Studio or an incompatible plugin. As a workaround, try deleting (or renaming, for backup purposes) the directory below, depending on the Android Studio version and operating system, and start Android Studio again. This will reset Android Studio to its default state, with all third-party plugins removed. For Android Studio 4.1 and later:
For Android Studio 4.0 and earlier:
Note that the configuration directory for Canary and Beta releases of Android Studio is Compilation issue in Kotlin multiplatform projectsCompilation errors may arise in Kotlin MPP code due to missing symbols. Upgrading your Kotlin plugin to version 1.4 should resolve this issue. Key mapping conflicts on LinuxOn Linux, certain keyboard shortcuts conflict with default Linux keyboard shortcuts and those of popular window managers, such as KDE and GNOME. These conflicting keyboard shortcuts may not work as expected in Android Studio. More information about this issue (including potential workarounds) can be found in IntelliJ's bug tracker. Small UI text on Chrome OSOn Chrome OS, text might appear much smaller than in previous releases. To work around this issue, do the following:
Code editingThis section describes known issues related to the code editor. Frozen keyboard input - "iBus" problems on LinuxThere are some known interactions between the iBus daemon on Linux and Android Studio. In some scenarios, the IDE stops responding to keyboard input or starts inputting random characters. This bug is triggered by some missing synchronization between iBus and XLib + AWT, and has already been reported upstream to JetBrains and iBus. There are three current workarounds for this issue:
Project configurationThis section describes known issues related to project configuration and Gradle sync. Gradle Sync Failed: Broken PipeThe issue is that the Gradle daemon is trying to use IPv4 instead of IPv6.
"peer not authenticated" errors from Gradle sync or SDK ManagerThe root
cause of these errors is a missing certificate in
DeployingThis section describes known issues related to deploying your app to a connected device. [Mac OS
only] Incremental updates are not applied due to an issue with Gradle file watching on projects saved under |