I've been trying for the last several days to build and run the GameMaker: Studio Android Google Mobile Ads app demo on my Samsung Galaxy S6. I finally have all the correct things installed I believe, and I've managed to solve a few other build errors before this, but I've hit a brick wall and despite all my searching I have not found an answer. My problem is very similar to this post's which poster said he solved by setting the build tools to the latest version. I don't know what he means by that.
The full compile form is too long to fit in a StackOverflow question, but I believe the only really relevant bit is the exception line:
com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command 'C:\Users\gunna_000\AppData\Local\Android\sdk\build-tools\23.0.1\aapt.exe'' finished with non-zero exit value 1
I've been pulling my hair out with this and any help would be immensely appreciated.
I followed the GameMaker: Studio Android instructions perfectly, with the only hiccup being the local IP address, which is supposed to be in the format xxx.xxx.xxx.0/24 such as 192.168.1.0/24. My IPv4 adress is 10.0.1.129. Not knowing what to do, I entered 10.0.1.0/24 into the Web Server IP allowed list, ignoring the last number. However I do not believe that really has anything to do with this problem, as I'm trying to run the GM:S app on my Android device over USB cable.
I believe I have all the right modules installed in the Android SDK Manager:
And my JDK, SDK, NDK, and Keystore are all accepted it seems:
I've been able to run and install Android apps made in Android Studio from this computer to this Android device (Android version 6.0.1), but GameMaker: Studio is just not having it. (And just to verify, I have bought GameMaker: Studio Professional and Android)
I don't have any weird extensions or plugins. I'm simply trying to run a GameMaker: Studio application on my Android device. Please help. Thank you.
If you still haven't solved this:
Make sure your PC doesn't have a pending Windows update (if you use Windows).
Make sure your phone is in the right mode to accept files and install from GameMaker.
Try to run a very simple project with only an empty room.
Make sure to have all packages up-to-date.
Potentially reinstall the hole Android SDK lib.
Make sure that your device is connected and is found by the ADB.
If GameMaker tries to start the network connection between your PC and the Android device, it means that it failed doing so over the cable.
Related
So I posted this question ( unity cannot find android SDK even when I have installed it already )
and I was hesitant to uninstall unity and reinstall so I installed Unity 2022.
Because I had android tools installed already the above issue was resolved for Unity 2022. ( not tested for 2018+
But I want to test the builds I was able to make now, so I created an AVD with the default resizable configuration, clicked next till the end and the AVD worked. But, when I installed the built .APK on the android device by dragging and dropping it said
INSTALL FAILED NO MATCHING ABI's
![AVD Error: INSTALL FAILED NO MATCHING ABI's ][2]
So I did some googling and found that I was trying to install it on intel x86/intel x64 architecture but the build was set to armv7 by Unity by default
So I made another AVD with ARMv8 and it did not even start
Threw a lot of errors :
![Android error log][3]
This was a photo but I don't have enough reputation on this platform to attach photos
I will attach the error log as a separate file here ( I cannot attach files here for some reason if anybody knows how please do tell me)
Anyway, I have no way of testing my unity android games and applications on my laptop and I need help with it
🥺 help please!
I tried formatting this better but I don't know why it does not take line breaks very responsively
I am trying to install apk from android studio. Initially I got below error:
So I disable instant run as suggested in many post on stackoverflow like this How To Stop Installation of Multiple Slice APK In Android Studio 2.3.
Now I am getting below error after disabling instant run:
java.io.IOException: An established connection was aborted by the
software in your host machine Error while Installing APK
I have only one instance of android studio running when I got this error.
Android studio version is 3.3.1. What can be cause of above error.
Also I am not able to install apk using adb install command. I am getting message failed to install apk with no detail message.
You can restart Android Studio : File -> Invalidate caches/restart
And i think you install ADB-Idea pluggin to uninstall or clear app data very easy with shortcut.
ADB-Idea pluggin :
Link
So I found out why I was not able to install apk from studio or from adb install command. Issue was due to my pc usb port was blocked by network administrator of our organization as my usb port usage period expired. So if anyone facing issue of not able to install apk and getting error as mentioned in question and no solution working for you than please check if your pc ports are not blocked by your organization network admin. I took approval to use usb port and it is working now.
You have got the first error because of :
You are testing your project_A on a emulator_E
As you had the app project_A, installed on the emulator_E, in previous run.
Now you started the execution of your project_A, again on the emulator_E.
The Android_Studio and emulator_E, both came to know that, the apk is already on the emulator_E, so just, whatever the new changes are, will be synchronised, within the, already available project_A apk, on the emulator_E.
But as the whole process takes some time, you uninstalled the apk of project_A on a emulator_E.
And now project_A on a emulator_E is not there, but Android_Studio tried to synchronised it, which leads you to the ERROR_1
Solution
You are following many approaches, for the same thing.
You are starting your project, project_A on the emulator_E by :-
via ADB INSTALL from the command line too
With Instant Run too
With Instant Run too
And you are not keeping the previous apk as it is there on the emulator_E, after starting the execution too.
Uninstall it from emulator_E, but before you start the execution for emulator_E. Which lead to your Android Studio to some dangerous STATE_A and, Android Studio is not tested by google for such types users
It may seem harsh, and obviously it is not the answer, but this is the exact problem, which is leading you to the such case.
I have recently been encountering this issue to the point where I cannot continue working. When starting Android Studio Gradle builds as normal but as soon as daemon starts it fails and I get the Error:
The first result from the daemon was empty. Most likely the process died immediately after connection.
I have done a number of different things and I have searched all over the internet trying to find a solution for this issue so I can work on some projects I have but so far I have not had any luck. A few of the links I tried using to find a solution are:
Android Studio gradle build error: 'The first result of the daemon was empty.Most likely the process died immediately after connection'
Gradle sync failed: The first result from the daemon was empty. Most likely the process died immediately after connection
https://teamtreehouse.com/community/first-result-from-daemon-was-empty-gradle-build-continues-to-fail
https://www.jianshu.com/p/5891e7d46f6c
I have tried everything in those links and no matter what I do it does not work. I was so desperate to the point where I uninstalled Android Studio Gradle and all the SDK hoping that would fix it and that didn't do it either. I figured hey maybe it's another issue so I thought doing a clean install would do the trick and guess what it worked for a day or two and right after that back to the same place I started at now... (Worst part is I had to download over 200gb for the clean install due to all of the things I had to reinstall).
I am attaching a picture below in case anyone wants to see the original Gradle:
Android Studio Gradle Screenshot
I found the solution after installing and reinstalling the operating system and everything on it about 4 different times. So the issue was the network driver and the software it seems like. Every time after the network driver is updated using driver website it crashes and renders the network useless.
After a while looking at the logs I finally noticed a pattern that Gradle was having issues with something involving the actual network adapters and so what I did was uninstall the network software and uninstall all of my network adapters driver and restarted the computer and had Windows 10 reinstall the drivers. I opened the Android Studio and it works flawlessly. So at the end of the day, the basics saved the day.
In case anyone is wondering which network devices I have they are the:
Killer E2500 Gigabit Ethernet & Killer Wireless-n AC 1535 Network Adapter
The software is the killer network manager.
I had the same problem with the Killer network interface. The motherboard I'm using has 2 gigabit NICs and a wireless adapter built into it. One of the two gigabit ports is Intel.
I believe the problem is with the Killer gigabit port/ Drivers. To get around it I just disabled the Killer E2500 Gigabit Ethernet port and restarted Windows. Gradle and Android Studio are now working without issues.
Also the mobo I'm using is a Gigabyte X299 Aorus Gaming 7.
Seems they fixed it with the latest Killer driver:
"KillerPerformanceSuite_1.5.1847_Win7_Win81_Win10_x64"
Just tested it and it seems to be working.
Had the same issue, and the culprit was also Killer-related software as mentioned in the other answers, after uninstall the software (from Store and through the Control Panel), then uninstalling the drivers, then restarting.
Then, it started to work again, but I just randomly decided to try installing the Killer Drivers+Software again through KillerPerformanceSuite_2.0.1175_UWD_x64, but it broke Gradle again, so I decide to do all those steps again, but after uninstalling the software (through Control Panel), I decided to check Android Studio if it would sync properly this time, and it did.
So the culprit might actually just be the software (Killer Network Manager).
I have created a blank activity project in Android Studio on Ubuntu 14.04. I can do a gradle build and install it to my device in one step using the installDebug target.
I wanted to work with the Nest API though, and I can't get the installDebug target to work. As a start, I downloaded their sample project and tried to build and install it in one go. I get this:
:testapp:installDebug FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':testapp:installDebug'.
> com.android.builder.testing.api.DeviceException:com.android.ddmlib.InstallException: Unable to upload some APKs
I created an app largely based off of this sample which also isn't working. Does anyone know how to fix this? What's weird is - it used to work at some point!!
I tried blowing away my Android SDK and re-installing everything, and also re-cloning the project from Nest's git repo and starting over. It's not working anymore.
I am extremely pleased I have figured out a solution to this problem.
I started to notice something was more seriously up with my adb connection because adb shell for example would just hang.
I neglected to mention it, but I was using Ubuntu 14.04 in Oracle Virtualbox as the guest to a Windows 10 host. I think that may have something to do with it.
In VirtualBox, I went to Devices > USB > USB Settings and under Enable USB Controller I enabled USB 2.0 (EHCI) Controller. Previously this was set to 1.1.
My guess is if the application is large enough, USB 1.1 is too slow to transfer all of the data in a timely manner.
I hope this helps someone in the future.
it could be because of three things:
If you are using a device, your device is not plugged in correctly. Make sure you can see it when you run adb devices on the commandline.
If you are using an emulator,the emulator is not running or it has not booted up yet.
Your app is configured to use a buggy version of gradle. Version 1.3.1 is well known to cause this problem.
The most likely cause of this problem will gradle version 1.3.1.
In my experience, upgrading gradle did not fix the problem. To fix it, I had to downgrade it to a rather memorable version of 1.2.3.
Look for com.android.tools.build:gradle:1.3.1 in the android/build.gradle, and update it to com.android.tools.build:gradle:1.2.3.
I had another program that was using the adb and was interfering with the build.
i'm currently reading through head first python and upon reaching chapter 8 I got stuck. The book wants me to download SL4A from the link http://code.google.com/p.android-scripting however that link no longer works. So I did some searching and found the file on github. My real problem is when I try to download it on the emulated device it just says waiting for data connection and it never downloads. I am wondering if there is a way to fix this. Any help is appreciated thanks!
EDIT: to get it to work I downloaded both files from here https://github.com/kuri65536/python-for-android/blob/master/README.md
then I copied the files to the folder
C:\Users\lucas\android-sdks\platform-tools
then I opened CMD and cd to the path above.
then use the command:
adb install (filepath)
for both files and they appeared on the emulated device.
Download to your pc and push through ADB.
Download files and adb install worked for me in my installation (Windows 10, android studio 2.1.1) with minor differences:
1) adb command is located in:
C:\Users\MyUser\AppData\Local\Android\Mysdk\platform-tools
Need to add to path
2) Needed release sl4a-r6.1.1-x86-debug.apk. Downloaded it from release pages
I'm also reading through HeadFirstPython and got stuck at this stage (with the error: app not installed). I tried the abs method above and ended up with yet another problem: install_failed_no_matching_abis. After a lot of research, I got to understand that the "native libraries" of the sl4a.apk were not matching the system architecture of my emulated android. In other words, if one wants a faster emulator in android studio, he ought to use an x86 architecture android; but the problem with that is scripting layer for android is programmed to work on ARM architectures hence the 'install_failed_no_matching_abis' error.
The solution that worked for me was to go back to AVD in Android Studio, delete the downloaded emulator (which was of x80 cpu/abi) and download one with armeabiv7 cpu, recommended level=24. It took a lot of trial and error to get to this choice as other android cpu/abi were either too slow or just wouldn't allow me to install the required apps.
Edited: In the end, I was directed to use GenyMotion as that performed better in terms of speed. I was reluctant at first but, to my surprise that really is the case (It is super faster than ARM android studio alternative). Not only is it a great emulator, it also has this ARM translation tools that allows one to easily install ARM sl4a.apk on the x86 devices.