portapps / android-studio-portable Goto Github PK

Behaviour

Circumstances: Emulator is running OK on a PC and functions as a normal, fully interactive Android phone.

Actions: Using the GUI menu: Extended Controls (click the bottom "..." icon on the emulator's sidebar) -- Displays -- Add secondary display, does not work. Although the grey schematic simulation on the right side shows the preview of the newly defined additional display(s), clicking the APPLY CHANGES button gives no result in the emulator window (no actual second display is added), and no error message is displayed either.

Steps to reproduce this issue

1. Install the "Android Studio™ portable" normally, i.e. using the official portable installer linked from the Portapps page ([https://portapps.io/app/android-studio-portable]).
2. Start the program using the android-studio-portable.exe launcher in the main installation directory, and set up everything you need, including virtual devices.
3. On the "Welcome to Android Studio" screen, look down and click "Configure", select "AVD Manager".
4. This opens a new window "Android Virtual Device Manager", where you can start any existing device of your choice (which opens in a new "Android Emulator" window).
5. On the sidebar (right to the running virtual phone), click "..." to open the "Extended Controls" window, where you go to Displays -- Add secondary display. Click APPLY CHANGES.
6. You will see absolutely no response whatsoever.
7. There is a message "Emulator: emulator: ERROR: MultiDisplay.cpp:110: Adb interface unavailable" on the "Welcome to Android Studio" screen, bottom part, the "Events" drop-down menu. This message may or may not be related to the problem described above (there are no other messages in that list, and I have no idea whether there is a causative relationship between the message and software malfunction).

Expected behaviour

In regular local (i.e., non-portable) installations, the above procedure expands the emulator window and adds a new display, predefined or custom, just next to the phone's Home screen. This can be repeated up to 3 times, resulting in 4 displays neatly arranged next to each other in a single row (the Home screen, and the 3 secondary displays). Each additional display can be individually deleted or freely resized / reconfigured. All changes are remembered and when you stop or restart the Android Studio, the modified virtual device opens with the added displays and with the respective apps open on them running OK.

Actual behaviour

Nothing happens - no secondary displays are created - the button APPLY CHANGES is not reactive. This is a critical failure that prevents users from emulating dual-screen devices (e.g., Microsoft) and hampers testing apps in 2-, 3-, or 4-display settings.

Configuration

App release / arch (ex. 1.0.0-2 win64) :
Android Studio portable v.4.0.14
android-studio-portable-win64-4.0.1-14-setup.exe (installer)
android-studio-portable.exe v.2.4.4.0 (portable launcher)
studio64.exe v.4.0.0.0 (64-bit executable)
studio.exe v.4.0.0.0 (32-bit executable)

Operating system (ex. Windows 10 Pro 64 bits) / Winver screenshot :
Windows 10 Home, v.1909, 64-bit
OS Build: 18363.959

Logs

Join the log file log\[appname]-portable.log to this issue. File "android-studio-portable.log" is attached.
android-studio-portable.log

Behaviour

Error when try to update app.
Some conflicts were found in the installation area.
Some of the conflicts below do not have a solution, so the patch cannot be applied
File: uninstall.exe
Action: Update
Problem: Modified
Solution: NONE

Steps to reproduce this issue

1. Run the app.
2. Update the app.
3. After download I get an error.

Expected behaviour

The app should be updated to newer version using update package (without error).

Actual behaviour

The app is not updated (update will be cancelled by this error).

Configuration

App release / arch (ex. 1.0.0-2 win64)
Android Studio 4.0.1, Build #AI-193.6911.18.40.6626763
Runtime version: 1.8.0_242-release-1644-b01, amd64

Operating system (ex. Windows 10 Pro 64 bits) :
Windows 10 Pro x64

Winver screenshot :

Screenshots

Logs

Join the log file log\[appname]-portable.log to this issue.
android-studio-portable.log

How can I update it/why isn't it updated by you guys?

Behaviour

Steps to reproduce this issue

1. Installed portable version on an Windows without any restrictions (same path of the target device: C:\PortableApps\PortableApps
2. Start android the first time on the device without any restriction
3. Copy the folder to the target-device
4. Cannot start Android on the target device with the following error (translated from German with google translate): The specified device, path, or file cannot be accessed. You may not have sufficient permissions to access the item.

German: Auf das angegebene Gerät, den Pfad oder die angegebene Datei kann nicht zugreifen werden. Sie verfügen ggf. nicht über ausreichende Berechtigungen, um auf das Element zugreifen zu können.

Expected behaviour

It is possible to start IntelliJ IDEA Ultimate with the procedure as described above.

Actual behaviour

Get the error message above.

It is not possible to install Android Studio direct on the target device because of the restriction. It is not possible to start the setup. Same problem with IntelliJ but the workaround works with IntellJ

Configuration

App release / arch (ex. 1.0.0-2 win64) : Latest version.

Operating system (ex. Windows 10 Pro 64 bits) : Windows 10 Enterprise

Winver screenshot :

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

android-studio-portable.log

Behaviour

I can't install and uninstall plugins. Disable works fine.

Steps to reproduce this issue

1. Install a plugin from inbuild marketplace
2. Restart the IDE
3. The plugin isn't in the list of installed plugins
4. Search the plugin on the marketplace, you can press "install" again

Expected behaviour

The plugin should be installed

Actual behaviour

The plugin isn't installed

Configuration

App release / arch:

4.0.1-14 win64

Operating system:

Windows 10 Pro 64 bits

Winver screenshot :

Logs

android-studio-portable.log

Behaviour

This does not affect Desktop as badly as mobile. On cell/mobile, the first thing you can see is a linked exe file that actually takes you to the VirusTotal link. There at the top, it shows 3 issues found. I know the 'Assets' dropdown is where the actual downloads are. But it's not clear and the 3~4 virus alerts may not seem reassuring to first-time visitors. ( I assume these are false positives but let me know if I'm wrong)

Steps to reproduce this issue

1. go to Github link via cell phone and click on exe link
   

2. End result shows multiple Virus alerts
   

Expected behavior

VirusTotal should report an all-clear status and actual links to the portable app should be more prominent, especially on mobile devices.

Behaviour

In folder android-studio-portable\data.android there is subfolder also named .android
Is this right?

Steps to reproduce this issue

1. Upgrade android studio portable to 3.5.3
2. Create or open a project

Expected behaviour

Tell me what should happen
I suspect data.android.android folder is some miss.

Actual behaviour

Tell me what happens instead

Configuration

App release / arch (ex. 1.0.0-2 win64) :
3.5.3-win64

Operating system (ex. Windows 10 Pro 64 bits) :
Win 10 Pro 64 bits

Winver screenshot :
Win version is 1909 (OS inner version is 18363.592)

Open a command prompt and type winver then take / save the screenshot of the window and drag the image file in this issue. For example: http://bit.ly/2vA5sxR

Screenshots

If applicable, add screenshots to help explain your problem.

Logs

Join the log file log\[appname]-portable.log to this issue.

I always see blank screen in android emulator launched by AVD. Is there any one successfully launching it?

Hello Team,

First of al thank you for your great work in order to save our lives !

Android Studio 4.2 is working properly for my projects runnning under Gradle 4.
While using Gradle 7.4, I got this error:

Can't convert 'UNIFIED_TEST_PLATFORM' to enum type 'BooleanFlag'
Cannot convert string value 'UNIFIED_TEST_PLATFORM' to an enum value of type 'com.android.builder.model.AndroidGradlePluginProjectFlags$BooleanFlag' (valid case insensitive values: APPLICATION_R_CLASS_CONSTANT_IDS, TEST_R_CLASS_CONSTANT_IDS, TRANSITIVE_R_CLASS, JETPACK_COMPOSE, ML_MODEL_BINDING)
Cannot convert string value 'UNIFIED_TEST_PLATFORM' to an enum value of type 'com.android.builder.model.AndroidGradlePluginProjectFlags$BooleanFlag' (valid case insensitive values: APPLICATION_R_CLASS_CONSTANT_IDS, TEST_R_CLASS_CONSTANT_IDS, TRANSITIVE_R_CLASS, JETPACK_COMPOSE, ML_MODEL_BINDING)

Thanks in advance !

Behaviour

When launch emulator, has warning:

Emulator: I/O warning : failed to load external entity "file:/C:/Users/username/.AndroidStudio3.4/config/options/updates.xml"

Steps to reproduce this issue

1. Debug an android app using an Android 8.1 AVD

Expected behaviour

Not display this warning message.

It looks like the updates.xml is in android-studio-portable\data\config\options, but the emulator find it in C:/Users/username/.AndroidStudio3.4/config/options. and in fact there is no folder C:/Users/username/.AndroidStudio3.4/config/ in disk.

Actual behaviour

Tell me what happens instead

Configuration

App release / arch (ex. 1.0.0-2 win64) :

3.4.2-4

Operating system (ex. Windows 10 Pro 64 bits) :

Win 10 64 bit, 1903

Hi,

Thanks for your lovely work. I am looking forward to the build with Android Studio 2021.1.1.

Could I please request you to make a build for it? Is there anything I can do to help? I will be happy to contribute.

Cheers!