Develop Reference

Can't Launch Android Studio Arctic Fox 2020.3.1.26 on Windows

Recently, I tried to install the latest version of Android Studio (Arctic Fox 2020.3.1.26) on my computer. Initially, it went well. It asked me for my SDK version, and I installed android studio at my D: Drive, as my C: Drive was only left with 7 GB of space. So, I had to download an emulator. As the emulator takes up around 10 GB, I tried to install the emulator on my d drive by changing the path variable ANDROID_HOME to a folder in my D: drive. As I copied the contents from my .Android to my D Drive folder, that's when the problem began.
After I restarted my computer, I discovered that I could not open my android studio at all. I ran windows PowerShell on the folder and executed studio.bat, and it appears that the issue lies with the JDK version of 17.0. I changed my JAVA_HOME, JDK_HOME, STUDIO_JDK to JDK 11.0 and managed to launch android studio FRONT PAGE. Not the IDE, only the front image, and it jumped a lot of error of java.lang.NoClassDefFoundError.
Here is my Log FIle:
2022-01-20 20:35:06,137 [ 6331] ERROR - llij.ide.plugins.PluginManager - Android Studio Arctic Fox | 2020.3.1 Patch 4 Build #AI-203.7717.56.2031.7935034
2022-01-20 20:35:06,137 [ 6331] ERROR - llij.ide.plugins.PluginManager - JDK: 11.0.10; VM: OpenJDK 64-Bit Server VM; Vendor: Oracle Corporation
2022-01-20 20:35:06,137 [ 6331] ERROR - llij.ide.plugins.PluginManager - OS: Windows 10
2022-01-20 20:35:06,137 [ 6331] ERROR - llij.ide.plugins.PluginManager - Last Action:
2022-01-20 20:35:06,138 [ 6332] ERROR - llij.ide.plugins.PluginManager - Could not initialize class com.intellij.internal.statistic.eventLog.fus.FeatureUsageLogger
java.lang.NoClassDefFoundError: Could not initialize class com.intellij.internal.statistic.eventLog.fus.FeatureUsageLogger
at com.intellij.internal.statistic.eventLog.events.VarargEventId.log(EventId.kt:108)
at com.intellij.internal.statistic.eventLog.events.VarargEventId.log(EventId.kt:104)
at com.intellij.featureStatistics.fusCollectors.LifecycleUsageTriggerCollector.onError(LifecycleUsageTriggerCollector.java:154)
at com.intellij.diagnostic.DefaultIdeaErrorLogger.canHandle(DefaultIdeaErrorLogger.java:63)
at com.intellij.diagnostic.DialogAppender.appendToLoggers(DialogAppender.java:86)
at com.intellij.diagnostic.DialogAppender.lambda$queueAppend$0(DialogAppender.java:59)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:313)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:776)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:727)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:746)
at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:976)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:843)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$8(IdeEventQueue.java:454)
at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:773)
at com.intellij.ide.IdeEventQueue.lambda$dispatchEvent$9(IdeEventQueue.java:453)
at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:828)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:507)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:117)
at java.desktop/java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:190)
at java.desktop/java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:235)
at java.desktop/java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:233)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.desktop/java.awt.WaitDispatchSupport.enter(WaitDispatchSupport.java:233)
at java.desktop/java.awt.Dialog.show(Dialog.java:1063)
at java.desktop/javax.swing.JOptionPane.showOptionDialog(JOptionPane.java:874)
at java.desktop/javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:670)
at java.desktop/javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:641)
at com.intellij.idea.Main.showMessage(Main.java:335)
at com.intellij.idea.Main.showMessage(Main.java:270)
at com.intellij.ide.plugins.StartupAbortedException.logAndExit(StartupAbortedException.java:86)
at com.intellij.ide.plugins.StartupAbortedException.processException(StartupAbortedException.java:34)
at com.intellij.ide.IdeEventQueue.processException(IdeEventQueue.java:700)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:424)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
I even changed my JDK version to android studio own JDK Version, and I still get this log file.
The steps that I have taken are:
Delete my SDK Installation Directory
Went to `\AppData\Roaming\Google\AndroidStudio2020.3' and Deleted all the contents in my folder
Went to \AppData\Local\Google\AndroidStudio2020.3and Deleted all the contents in my folder
Added disable.android.first.run=true to my idea.properties
Open Android Studio Offline
Deleted .Android, .Gradle, .m2 from my Users Folder
Reinstall the Older version, Android Studio Arctic Fox 2020.3.1.22 but the problem persists
Did all the above steps in my C Drive, deleted everything first, did a fresh install, the problem persists
It is at this point, that I think that my only solution is to download android studio using a VM and run it on my computer. However, I would like to avoid using this solution, as you know, Android Studio requires a lot of processing power, and I think my computer is more likely to crash before I can even develop an application.
I need to use the android studio as it is compulsory for my school work in my university.
Note: I am unable to replicate the initial process of choosing where to download the SDK file for the android studio (After Deleting Everything stated in the above steps), if anyone could provide me advice on that, I would be extremely thankful.
TLDR: I was initially able to launch android studio, but after changing the directory for my emulator, I am now unable to open it. The log File is provided above. I have uninstalled and reinstalled multiple times, and I can't launch the IDE.

Nvm, I found the problem instead. Turns out I didn't properly check for my file URL in my system path environment. The issue lies with ANDROID_SDK_HOME. I deleted the file directory, and there was a unknown symbol at the front of the file URL. I manually set the file url in CMD instead using the command setx.

JavaFX-11/macOS: DirectoryChooser crashes 'NSObjectNotAvailableException'

I develop a java application using openjfx modules.
I now want to use DirectoryChooser to let the user select several files as an input (code below). Everytime I start the application from the IDE it crashes with the exception below. By crashing I mean totally terminates (not freezing).
I also tried some sample code like this to figure out if there is anything wrong with my implementation but each sample I found gave me the same issue.
I'm unsure if this is a general issue/bug because I saw old bugs, in the oracle bug tracker but they where all marked as fixed.
I would be happy if someone could provide some help on this. I would even be happy with a workaround that just avoids DirectoryChooser if there is any.
Steps to reproduce:
create a small Application with the demo code from here.
run the application
try to open directory chooser
Background information:
OS: macOS 10.15.2 Catalina
IDE: intelliJ IDEA Ultimate 2019.3
Exception
2020-01-30 17:18:31.288 java[49749:1319417] *** Terminating app due to uncaught exception 'NSObjectNotAvailableException', reason: 'GlassOpenPanel is not a supported subclass for sandboxing'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff364ea8ab __exceptionPreprocess + 250
1 libobjc.A.dylib 0x00007fff6c75b805 objc_exception_throw + 48
2 CoreFoundation 0x00007fff364ea701 +[NSException raise:format:] + 189
3 AppKit 0x00007fff33d43aa9 +[NSSavePanel(Instantiation) _crunchyRawUnbonedPanel] + 368
4 libglass.dylib 0x00000001370a2ba6 Java_com_sun_glass_ui_mac_MacCommonDialogs__1showFolderChooser + 358
5 ??? 0x0000000117695950 0x0 + 4687747408
6 ??? 0x000000011768fa00 0x0 + 4687723008
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Solution
As suggested by mipa increasing the OpenJFX version number solved the problem.
At the moment, it seems working for OpenJFX version 14-ea+7 and 15-ea+1 from MavenCentral

Why do you use an outdated Version of JavaFX? The current version is 13 and 14 is coming out shortly. EA releases are already available. You can also use them with Java 11.
I tried two of the examples you mentioned with JavaFX 13 and they worked without problem. This may be due to the fact that a bug has been fixed or due to the fact that I am still using MacOS 10.14.6 Mojave.
Give JavaFX 13 a try and then report back.

How to setup an emulator running API 25 using a build matrix on Travis CI?

I am attempting to setup Travis CI so that it runs instrumentation tests on an emulator running API 25. Travis runs the tests to completion on API 4/10/19, but fails to startup the emulator for API 25, with the following message:
$ echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI
Valid ABIs: no ABIs.
Error: Invalid --abi armeabi-v7a for the selected target.
The output of android list targets shows that the API 19 emulator has a Tag/ABI, whereas the API 25 emulator does not:
id: 7 or "android-19"
Name: Android 4.4.2
Type: Platform
API level: 19
Revision: 4
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a
id: 11 or "android-25"
Name: Android 7.1.1
Type: Platform
API level: 25
Revision: 3
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : no ABIs.
How can I fix this so that the API 25 emulator launches and runs the tests?
The full .travis.yml file is as follows:
language: android
android:
components:
- tools
- platform-tools
- tools # appears twice as per Travis docs
- build-tools-23.0.1
- build-tools-25.0.2
- android-4
- android-10
- android-19
- android-23
- android-25
- extra-android-m2repository
- sys-img-armeabi-v7a-android-25
env:
matrix:
- ANDROID_TARGET=android-4 ANDROID_ABI=armeabi
- ANDROID_TARGET=android-10 ANDROID_ABI=armeabi
- ANDROID_TARGET=android-19 ANDROID_ABI=armeabi-v7a
- ANDROID_TARGET=android-25 ANDROID_ABI=armeabi-v7a
before_script:
# Create and start emulator
- android list targets
- jdk_switcher use oraclejdk8
- echo no | android create avd --force -n test -t $ANDROID_TARGET --abi $ANDROID_ABI
- emulator -avd test -no-skin -no-audio -no-window &
- adb wait-for-device
- while [[ `adb shell pm path android` == 'Error'* ]]; do sleep 2; done
- adb shell input keyevent 82 &
script: ./gradlew --info connectedAndroidTest
sudo: false

Note: emulator version 26.1.4+ versions can introduce or fix bugs. If a reproducible ci build is required, the best option is to download the desired sdk-tools version no via android components.
Note: emulator version 26.1.3 is here including interesting fixes. I'm busy to revise my answer now:
Related issue using emulator 26.1.2 here. Relaunch last build like me to use 26.1.3 and pray, green
I am attempting to setup Travis CI so that it runs instrumentation
tests on an emulator running API 25. Travis runs the tests to
completion on API 4/10/19, but fails to startup the emulator for API
25...
How can I fix this so that the API 25 emulator launches and runs the
tests?
Update: I confirmed that ARM ABIs for APIs 23, 25 and 26 are also missing in Android Studio, so:
It's not a Travis-ci issue. I reproduced it locally as shown in the next image.
You can use ARM ABI for API-24. I forked your project and it worked in build #6 (next image).
You can use Google APIs image for API-25 as I explain below using the new sdkmanager: 1
You can use Google APIs image for API-25 using legacy tools if you know the img name: 1,2,3
We need to ask to Google or someone else why the ARM ABIs for these APIs are missing.
Update: A related bug was already reported to Google and discussed here, please, star it:
For some reason it's marked as being only available on windows. I'm
not sure if this is a problem with ADRT itself or the configuration
for this package, but from a quick look it seems like it's probably a
problem with adrt itself.
I'm not sure if the api-25 issue is related but I expect that it will work combining several solutions:
Use system images with google_apis to simplify the build matrix and avoid missing ABIs.
Use the new sdkmanager and avdmanager required by the recent Sdk Tools.
Use the new Trusty images including these tools to simplify the Travis-ci configuration or alternatively use dist: precise as explained here.
See the links below to working samples using a build matrix that includes Api-25 emulator.
I updated the api 23 system image one time on a macbook via Android Studio and appeared a message about the new version was not supported by my computer, so I use the google_apis one.
I offer a possible solution to the issue commented by Ashish Pathak (I'm also ardock) here.
I need to update my response to support the new Travis-ci images that comes with new SDK tools.
The new pre-installed Sdk Tools will simplify the solution and reduce the YAML file in size.
As announced in this blog post by Carmen Andoh and Dominic Jodoin on 19 Jun 2017:
Updates are coming to all Ubuntu Trusty 14.04 images
This new generation of Trusty images is already available in
production and can be used by adding group: edge in your .travis.yml
file:
sudo: required
dist: trusty
group: edge # Add this
And as explained here:
As a bit more information, this new Android image comes with:
Android SDK 25.2.3 build-tools-25.0.2
The new sdkmanager tool - a command line tool that allows you to view,
install, update, and uninstall packages for the Android SDK. Replaces
the previous android tool, see
https://developer.android.com/studio/tools/help/android.html
Also, the new Android image should be retro-compatible. See the full
list of Android SDK components that can be specified in the
.travis.yml file, including build-tools-26.0.0-preview.
But they are not using the new avdmanager, I'll try to fix it this weekend.
Alternatively, you can use the previous images by adding dist: precise.
The lines below are part of my answer on a related question: prior to the images update:
Full working sample using constraint-layout codelab repository for Android API level 22 to 25:
Two more samples using sdkmanager and avdmanager:
Android Maps Utils library - Google
Dexter library - Karumi
References
Official documentation related to Auto-download missing packages with Gradle
The new Emulator options are explained in Start the Emulator from the Command Line
avdmanager explained here replaces android avd since SDK tools version 25.3.0
sdkmanager explained here also enhanced to view and accept all licenses from the command line

virtualbox inaccessible and genymotion unable to load

Greetings to all I hope you have a good day , not like me.i have captive genymotion.My genymotion has been broken and disabled. I do not know what to do. I went a few places for solve this problem But I did not answer .my os win7.
Error
Unable to start the virtual device.
VirtualBox cannot start the virtual device.
To find out the cause of the problem, start the virtual device from VirtualBox.
For more information, check the log files.
ok when start the virtual device from VirtualBox this message show for my:
Failed to create the VirtualBoxClient COM object.
The application will now terminate.
Callee RC: REGDB_E_CLASSNOTREG (0x80040154)
and again message:
Failed to open a session for the virtual machine Samsung Galaxy Note 3 - 4.4.4 - API 19 - 1080x1920.
The virtual machine 'Samsung Galaxy Note 3 - 4.4.4 - API 19 - 1080x1920' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Rad\AppData\Local\Genymobile\Genymotion\deployed\Samsung Galaxy Note 3 - 4.4.4 - API 19 - 1080x1920\Logs\VBoxStartup.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {f30138d4-e5ea-4b3a-8858-a059de4c93fd}
and virtualbox error :
for virtualbox is Start tag expected, '<' not found.
Location: 'C:\Users\Rad\VirtualBox VMs\genymotion_vbox86p_4.4.2_140524_040850\genymotion_vbox86p_4.4.2_140524_040850.vbox', line 1 (0), column 1.
D:\tinderbox\win-4.2\src\VBox\Main\src-server\MachineImpl.cpp[725] (long __cdecl Machine::registeredInit(void)).
Result Code:
E_FAIL (0x80004005)
Component:
Machine
Interface:
IMachine {22781af3-1c96-4126-9edf-67a020e0e858}
how to copy file to file?!

All the problems were solved by changing the version of virtualbox .
version of VirtualBox-4.3.2-90405-Win
and
version of Genymotion.v2.5.3-vbox

Error on running a simple App Engine project

I'm new to Google App Engine, and I tried to create a test project on Ubuntu 11.04 following this quick tutorial http://www.youtube.com/watch?v=P3GT4-m_6RQ&feature=relmfu
and I have this error when i click on "debug > web application"
There is a new version of the SDK available.
Latest SDK:
Release: 1.6.2
Timestamp: Tue Jan 03 19:15:38 CET 2012
API versions: [1.0]
Your SDK:
Release: 1.6.1
Timestamp: Mon Dec 12 23:53:13 CET 2011
API versions: [1.0]
Please visit http://code.google.com/appengine for the latest SDK.
java.lang.RuntimeException: Unable to restore the previous TimeZone
at com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:228)
at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java:164)
at com.google.appengine.tools.development.DevAppServerMain$StartAction.apply(DevAppServerMain.java:164)
at com.google.appengine.tools.util.Parser$ParseResult.applyArgs(Parser.java:48)
at com.google.appengine.tools.development.DevAppServerMain.<init> (DevAppServerMain.java:113)
at com.google.appengine.tools.development.DevAppServerMain.main(DevAppServerMain.java:89)
Caused by: java.lang.NoSuchFieldException: defaultZoneTL
at java.lang.Class.getDeclaredField(Class.java:1899)
at com.google.appengine.tools.development.DevAppServerImpl.restoreLocalTimeZone(DevAppServerImpl.java:222)
... 5 more
Can anybody determine where the problem is? I also had problems trying to create a GWT app and a Python App Engine project.

Possible duplicate of: DevServer fails after updating to java 6u31
However, this problem seems to be documented (with solution) here:
http://code.google.com/p/googleappengine/issues/detail?id=6928
From the site:
Workaround - start the GAE with the following JVM parameter:
-Dappengine.user.timezone=UTC
(with eclipse, go to "run configuration", under the "Arguments" tab add "-Dappengine.user.timezone=UTC" to the VM arguments line. With maven-gae-plugin, add -Dappengine.user.timezone=UTC to the plugin configuration).
Good luck, and hopefully Google will support JDK u31 soon enough.

This article solved my problem with GWT: Fix The Unable To Restore The Previous TimeZone In GWT.