I am creating signed apk for my app and it taking like 1 hour and the process of "Gradle building"is still going on. Is it normal or something wrong is hepping and no error is shown here ?
As it is my first app so i don't know.
Give me some suggestion about it.
First, check the specification of your computer, as the official site said:
you need >=3GB RAM, In my personal experince, I recommend that you use >= 8GB RAM; also, if you has SSD, the android studio will be faster.
So, check your computer, if you don't have enough memory, update your computer
Second, maybe there is a bug in your program, sometimes, android studio will execute very long time due to a bug. => maybe you should check if there is anything wrong in your program before you click build.
Hope this post help you!!
reference:
1. https://developer.android.com/studio/index.html
Related
enter image description here
Please help me resolve this issue.
Android studio is heavy IDE and takes lot of of time for initial setup.
a couple of things:
Make sure you got good strong wifi
If you're on VPN, disconnect it.
stop other stuff if you're downloading
last resort is to shutdown and restart.
Here is the error I'm getting when trying to archive my app for deployment.
This error doesn't show up at any other time. The project builds and runs on emulators and devices without issue. This error has zero context or direction as to where to look to fix it. It also just randomly showed up out of nowhere, last time I built/archived (with zero functional changes) this error did not happen.
Main difference between this archival and the previous one is a newer version of VS 2017. Don't remember exactly the version from before, but am currently on 15.9.4 (stable).
Looking around on the interwebs, I've found that this error seems to have something to do with ObservableCollection's, which there are probably 10-ish in my app. Not really sure what to do here, because this has never been an issue previously, and I'm coming up on a deadline and with the structure of the app, am not in a good position to start making functional changes.
EDIT
I have also cleaned and rebuilt my solution, as well as deleting all bin/obj folders in my xamarin projects. Even tried deleting the .vs folder which can sometimes help. But still no go.
Going to try updating VS to 15.9.5 and see if maybe it was fixed in a release.
EDIT 2
Updating VS 2017 to 15.9.5 made no difference.
EDIT 3
I had my coworker try archiving the exact same project on his machine (running VS 2017: 5.9.3, and it archived fine for him. So far that's the only difference we've been able to find between our environments.
I saw the same problem using VS2017 15.9.9. Even the same code that could be archived a week ago threw the above mentioned error. It seems related to local data in the solution. A "clear" build was not sufficient. However manual deletion of the local obj and bin folders followed by archiving (build is done implicitly) solved the problem for me.
For my part closing Visual studio and deleting the .vs hidden folder did it.
It's actually a fix for many issues using Xamarin.
I had this other issue where I couldn't archive because the build process would just hang and never end. Deleting the .vs folder did it too.
https://github.com/xamarin/xamarin-android/issues/1760
Just go to project property then go to Android options-> Select Advanced then increase the Java Max heap size to 2G/3G -> it's working for me.
Leon Lu's suggestion worked. I don't particularly like it, as it took forever and repairing basically restores you to a base install (no extensions or personalizations). Took about 1.2 hours to complete, but once done I was able to again archive my android application. I guess something went wrong in vs at some point, perhaps during an update. There's no way to tell.
I tried ALL of the ideas above, but had no consistent reliable luck with any of them.
I found that Microsoft has had the problem reported to them (see link below). After a ton of time burn on this, I posted at the link below one way that I've been able to get around this archive-build issue.
Like the other fixes, it's not exactly logical, and nothing that you would think would work, but I've found the process to be repeatable, which is golden for me with tight timelines and having no time for this.
MS Visual Studio Developer Community Problem 507708
Posted on a Saturday morning, a sign of really needing to get around this urgently. I hope it helps you too.
Hey guys and girls for a the past week I've grown a lot of interest in android studio (even without knowing quite much about it) I decided to create an app that I deemed quite useful. However the app required maps to be integrated in it and I really did not know what I was doing and at one point I started messing with the settings and then all hell broke loose and I kept getting AAPT2 errors and I even tried to fix this issue with the gradle properties line that you add (I forgot the line of code to add). Anyways it still didnt work. However I rembered that I always kept the good version (before I broke everything) of the app on my phone. So when I go in my phone the app is there and it works just fine. Ive tried so many things to get the source code from the app on my phone without any succes. My question is, how can I get the source code back from the working app onto my laptop to continue coding in android studio? If it helps I am using Linux 18.04 LTS and running the newest version of android studio. Thank you for any help from you guys. This means a lot to me.
You can’t get back the ‘source code’ from an already compiled app.
You should consider using some version control platforms like git from the next time
I'm having this problem when I debug my app. It blocks at this line and I don't know what is causing it. I could not find any answer or anyone that had the same problem. I have no clue what part of the code could cause this to happen. Do you have any ideas or have experience with this?
I'm using
Android Studio 3.1,
JRE 1.8.0,
JVM: OpenJDK 64-bit
Waiting for a blocking GC ProfileSaver message appears for me when I have set too many break points.
This link will help if you are looking to manage your break points.How to effectively remove all breakpoints in Android Studio
I solved this by wiping out all user data from the emulator and reloaded the app. You may use this step if you are absolutely sure about loosing user data.
Go to Android Studio, then in Tools menu click on AVD Manager and select your virtual device and click on wipe data
As may be seen in the attached picture
It happens to me too. But not only in debug, but also in real. As you say, one of 10-15 times when I sign in. I think the problem is derived from http connection problems. This has happened whenever I load the initial data.
I faced the same problem just now, I tried another device and the application worked usually, then I knew that the problem is in the device I used not in the code itself. To fix that, I wiped the device data and it works again.
I searched around a lot before asking, on this website and others, I've found a lot of advice but I either can't fully understand it, or I'm implementing it wrong.
I build my .apk from Unity3D, and then I put that on Google Drive and using ASTRO File Manager on my Galaxy Tab 2 10.1 (GT-P5110) I launch it and install it, it says 'installing' for a short amount of time and then it just tells me 'App not installed'.
Most of what I've read is telling me that it wont work if it's an unsigned build, but to start with I was using the debug option in Unity's Publishing Settings, and now I've generated a new keystore, rebuilt it, got it back over on the device and the same thing is still happening.
Am I missing some critical concept or step here? I'm brand new to Android development and it's taken me a while to get to this stage, so if there's something I'm missing that is glaringly obvious then please help me out!
Thanks in anticipation!
SOLVED: Followed the instructions here, and it fixed my problem! Hope this helps someone else!
http://forum.unity3d.com/threads/210920-Failure-INSTALL_FAILED_CONTAINER_ERROR
The Solution in this is following:
Go to "Player Settings", click Android Tab
Under Other Settings/Configuation/Install Location, set to "Automatic".