Have you added junit as a test dependency? Ok, the latter was my fault - oversaw the option "set classpath of module". And now it magically worked - so it was entirely my fault!
No problem, glad you figured it out. Am I missing something? Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in. Linked pull requests. Go to File - Other settings - Default settings on default settings dialog. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
Who owns this outage? Web Expand child menu Expand. Must Learn Expand child menu Expand. Big Data Expand child menu Expand. Live Project Expand child menu Expand. AI Expand child menu Expand. Toggle Menu Close. Search for: Search. Known Issues with Android Studio This section describes known issues that exist in the latest stable version of Android Studio. Error when using different passwords for key and keystore Starting with version 4.
Studio doesn't start after upgrade If 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.
For Android Studio 4. Compilation issue in Kotlin multiplatform projects Compilation errors may arise in Kotlin MPP code due to missing symbols. Near the top of the window, click Revert. Click OK. You should now see the missing buttons in the toolbar. Select Use custom font. Increase the font size. Code editing This section describes known issues related to the code editor. Frozen keyboard input - "iBus" problems on Linux There are some known interactions between the iBus daemon on Linux and Android Studio.
There are three current workarounds for this issue: Workaround 1: Force iBus into synchronous mode. Note that if you restart the daemon while Android Studio is running for example, by running ibus-daemon -rd , you effectively disable the input methods for all other applications and may also crash Android Studio's JVM with a segmentation fault.
Ubuntu To check your shortcut bindings, run ibus-setup on the command line to open the IBus Preferences window. Under Keyboard Shortcuts , check the Next input method. Project configuration This section describes known issues related to project configuration and Gradle sync.
To resolve these errors, proceed as follows: If you're behind a proxy, try to connect directly. If the direct connection works, then in order to connect via the proxy you may need to use keytool to add the proxy server's certificate to the cacerts file.
Re-install a supported, unmodified JDK. If you see an alert that System software from developer "Intel Corporation Apps" was blocked from loading , click Allow : For more information and workarounds, see this Apple webpage and issue Android Studio incorrectly force stops the app When using Android Studio 4. Jobs and alarms that are scheduled to run in the background are canceled Issue The force stop event is recorded in logcat Issue Apply Changes This section describes known issues that are related to Apply Changes.
New app name not applied If you rename your app and then try to apply that change, the updated name might not be reflected.
Issue in Android Runtime throws error If you're using a device that runs Android 8. Your app runs in the same process as another app using a shared android:sharedUserId and android:process.
When Apply Changes fails due to this issue, Android Studio displays the following message: Changes were not applied. Debugging and testing This section describes known issues related to debugging and testing your app. JUnit tests missing resources in classpath when run from Android Studio If you have specific resource folders in your Java modules, then those resources won't be found when running tests from the IDE. Workaround 2: Update your build script to manually copy resources into the build folder.
See comment 13 for more information. Running JUnit tests may compile the code twice When creating a new project, the template JUnit configuration might be created with two "Before launch" steps: Make and Gradle-aware Make.
You should see the welcome screen. Some test run configurations don't work Not all run configurations that are available when right-clicking a test method are valid.
Adding Java breakpoints while debugging native code While your app is paused at a breakpoint in your native code, the Auto and Dual debuggers may not immediately recognize new Java breakpoints that you set.
Stepping out of the native debugger While using the Auto or Dual debugger to debug Java and native code, if you step into a native function from your Java code for example, the debugger pauses execution at a line in your Java code that calls a native function and you click Step Into and you want to return to your Java code, click Resume Program instead of Step Out or Step Over.
Native debugger hangs while loading libraries While using the native debugger for the first time after upgrading to Android Studio 4. Native debugger crashes with "Debugger process finished with exit code " This error occurs on Linux-based platforms when starting the native debugger. Profilers This section describes known issues with the Profilers. This issue is fixed in Android Studio 4. Native Memory Profiler: Profiling not available during app startup The Native Memory Profiler is currently unavailable during app startup.
0コメント