My android gradle is kept on syncing even all the process under it are fully completed and got the green tick mark on their left side but the top header which is as in my case is MegaFlip:syncing this header shows that syncing is in the progress while all the sub tasks under it are entirely completed.I cannot even explore my project files.So any one have idea why this is happening?One thing to add is i created this project in the older window and now today i install fresh window and install android studio and try to open this project but it kept on syncing.Please suggest me a workable solution.
All the problems I had syncing gradle were solved once I disabled firewall.
Related
I've googled pretty much but i can't seem to find any information on this..
I've cloned a project from github, it opens and builds no problem. it's also added to my start menu.
I can run the program from my start menu as if it was a "normal" program.
Now I have made some changes to the sources and built it, and the changes seem to be present in the installed version (which I start from start menu) just by themselves.
my question is: is that really the case? do UWP apps get installed and updated automatically? is there a way to NOT update my installed version with my release-build every time? it seems wrong, did I miss something? (did I maybe "install" the changes somewhere along the way without noticing/by double-clicking the executable etc.) and: can I replace the executable that is started in the start menu? I tried to find where it is stored/linked, but I couldn't find anything, as there is zero information in the start menu.
Or can I rely on the start menu version always being my latest release build?
I'm confused, if someone has any information on this, I'd be really happy. :)
You are correct whenever you build and run the app on the local machine using Visual Studio it gets deployed to the system apps from where you can run it. So each time you build and run with any changes they will be updated in the system installed app as well(Basically they are same)
If you want that these changes do not get reflected in the system's app then I think you can use Device emulators available in the Visual Studio.
All my project (from the same solution) references are marked with a yellow triangle. The projects are all set to the same .NET version (4.5.1). The error log says:
The project 'CommonLibrary' cannot be referenced.
A way to temporarily fix the issue is to either:
Remove and re-add the references
Right click and choose Add Service Reference and immediatelly cancel.
However, the triangles come back every time I start the solution.
The solution is build successfully regardless or the issue. The real issue is that Resharper acts like the references don't exist.
Another thing that might be relevant is that I have 2 projects that are supposed to be unloaded but they become active every time I load the solution.
Any idea what to do with the issue?
I had similar issues and it usually comes down to the Target Framework (Project>Properties>Application). I was working on a solution using .NET 4.6 and for some reason the default framework for new projects have a different target (in my case it was 4.5.2). So make sure you check all your project at the very least have the same target framework.
Do the following:
In vs choose: tools->options->resharper->options-> general-> click the clear caches button.
then close all your opened tabs and shut down vs2013.
finally, start vs2013 again.
Let me know if that worked for you.
Try switching to managed compatibility mode in VS2013
you can do that by going to tools->options..->General tab and check the Use managed compatibility mode
I had the same thing happen but didn't suspect the 24 warnings I was getting was related to this error: Error 1 Unable to locate the .Net framework aspnet_merge.exe tool on path '~\Photo Archive\Main\etc\tools'. You need to set the msbuild property 'AspnetMergeToolPath' to the folder containing this tool. ODOT.PhotoArchive.Web
Trying to set the MS build property led to a lot of research just to find out WHICH property to set. So, Agent Ransack to the rescue -- searched my drive for the most recent version of the tool and copied it to the directory Visual Studio was complaining about.
Rebuilt the project with the idea of clearing the error but then the 24 warnings also disappeared.
FYI -- this is an MVC project which will replace a classic asp project. This might be peculiar to MVC projects.
At any rate, there was a lot of chasing snipes before this was finally tried. So, where this is happening, try handling any errors no matter how remote the possibility is they're related to the issue.
I had the same problem as you can see in this picture.
Its reason was the hidden folder. I had hidden the folder containing the project files. I got rid of this problem by unchecking the hidden attribute of the root folder containing the project files and restarting the visual studio.
Check it once, you might have checked the folder to be hidden.
This morning I have been experiencing an issue with Android Studio, whenever I open it I am getting the following error.
I have tried removing Android Studio and getting a clean install. Removing all the preference folders. Removing and re-downloading my project's repository. Creating a new project. All of these still end with this error showing up. No mater how high I increase the memory it is still getting this issue.
I have checked the Activity Monitor and it is actually only using 524mb of memory. Does anyone have any suggestions?
The next thing I'm going to try is using an older version of Android studios. Apart from that I'm not sure what else to do beside a clean install of the OS and hope for the best.
UPDATE:
Couldn't work out a way of fixing this, and had to perform a clean reinstall of OSX.
I was fighting with this problem today for a few hours and ended up trying File -> Invalidate Caches / Restart... and chose the Invalidate/Restart option. Seems to have fixed the Out of Memory error.
Don't know if that will work for you at a later time, but hopefully it helps.
Go to /Applications and do right click on Android Studio > show package contents
Then go to /Contents/bin/studio.vmoptions and change it like this:
-Xms128m
-Xmx800m
-XX:MaxPermSize=350m
-XX:ReservedCodeCacheSize=96m
-XX:+UseCompressedOops
There are couple of ways to handle out of memory in Android Studio:
Clean the Project And Rebuild
Invalidate Caches/Restart -> Sync Project with Gradle files
Restart the PC
Close Android Studio -> Delete .idea folder -> Start the Android
Studio and rebuild.
Still facing the issue, Need proper investigation.
This may be a simple error in your code that Android Studio does not know how to resolve.
Example problem: In my case, within my activity's onCreate function, I wrote binding.root.also{ } and deleted the opening curly bracket of the also scope function. This caused Android Studio to run out of memory and freeze.
Solution: I deleted the also function within Notepad and there were no problems afterwards.
This happened to me when I entered /* to begin commenting out a few lines. And it happened before I could add the */ to close the comment section. Therefore, the entire second half of the file (and beyond) was being commented out. I could not go back to add the needed */ to close the comment, because the "Out of Memory" window kept popping back up before I could do so.
So I closed Android Studio,
opened the same .java file in NotePad,
added the needed * / a few lines below the /*,
saved the file with NotePad,
then reopened it again in Android Studio.
The Out of Memory problem was gone for good.
I also got the same problem in my case, I tried to dump memory and it is reached to 200mb and while opening the studio it is showing the continuous process, because of '.hprof' the file is loading. Finally, I removed the '.hprof' and able to run my project. The .'hprof' file removed from the directory ''
I had the same error recently (Android studio 3) even though I had 16gb Ram + I7700K CPU.
I noticed that it started to appear after I disabled the Virtual Memory Ram because I needed some extra space in my SSD. so I just reactivated it and the problem was solved!
I'm posting this in hopes to help several folks who may be struggling the same way I am. I was just trying to fix my run configuration for a basic Android project in Android Studio when things went haywire. Ever since 2 updates ago my run config stopped working. It was somehow pointing to an apk path that had been changed. Something in the latest AS updates changes where the apk is built to without updating existing run configs. Long story lengthened…
I tried creating a new run config then tried running the old config. I got an error saying that I probably needed to sync my project with my Gradle build file. I clicked the "Refresh all GRadle Projects" sync-looking button in the Gradle tasks window when everything went awry. My module completely disappeared from the project! I tried re-importing from project settings then I started to get an error:
Could not install Gradle distribution from 'http://services.gradle.org/distributions/gradle-1.8-bin.zip
I couldn't figure this out because I didn't have this problem earlier and also I noticed my module file had been completely deleted! I tried a few more times before looking at the Android Studio logs which said something about it couldn't unzip the gradle 1.8 bundle or something. I realized it was trying to download something and that I was on paid wifi in an airport so the download couldn't complete. I then payed for wifi so that the download could complete and tried re-importing the project. I STILL got the error! After few more attempts I decided to check under ~/.gradle where I found and deleted "wrapper/dists/gradle-1.8-bin folder thinking the earlier download was corrupt and confusing AS. That seemed to get things going again as the next attempt triggered a download/install of something that allowed me to continue to the next step.
I'm currently still trying to re-import and set the module up again and it feels like a lot of re-work. I eventually got to a point where I was told my version of gradle was too old... (I have Gradle-1.7) I'm just throwing this out there now in case anyone else hits their head the way I just did. It can be an expensive mistake. (I'm still paying for Wifi so I can send this!)
I've finally figured out my issue. My build.gradle was set to use 'com.android.tools.build:gradle:0.5.+', which is incompatible with the latest version of Android Studio. After duplicating my project folder in Finder, updating to the latest Gradle, and tweaking the plugin version I am finally able to sync my project. I hope this post saves someone else a headache!
while doing the build of my dontnet 4.0 project setup i'm getting following errors
An error occurred generating a bootstrapper: Unable to finish updating resource for E:\project\Setup\Debug\setup.exe with error 8007006E E:project\Setup\Setup.vdproj Setup
General failure building bootstrapper E:\project\Setup\Setup.vdproj Setup
Unrecoverable build error E:\project\\Setup\Setup.vdproj Setup
I am using dotnet framework 4 and MSVS 2010.
This happens because The .NET framework version required by the setup project is different than the .NET framework version targeted by the application.
To change verify this:
In Solution Explorer, click the Setup project.
On the View menu, point to Editor, and then click Launch Conditions.
Click .NET Framework.
In the Properties window, change the Version property to the version of the .NET Framework that you want the Setup project to check for and install.
And also you need to Make sure that the Setup.exe program also checks for and installs the correct version of the .NET Framework.
Right click on the setup project -> Properties -> Prerequisites -> Select the correct ones.
When I turn McAfee real-time scan off, it works. I spent 2 hours on figuring this out :(
I googled a lot on this issue after trying all i just disabled my antivirus(NPAV) and this issue was solved.
turning off mcafee real time scanning worked for me as well on Windows 8.1
Here is yet another solution, this one is unlike the rest...
We recently added NTFS replication to our build tree root to provide some additional data redundancy and to begin to sync our old build machine with the new server. The NTFS replication caused some projects to fail with the exact same three error reported, and yet other projects work just fine. Set the replication on only run at night and the problem stopped occurring...
K
I got the same error when I changed targeted framework to 4.0 but neglected to change prerequisits for click once from 3.5 to 4.0 as well.
Fixing prerequisits resolved the problem.
Instead of disabling the Anti-Virus, I would suggest to just create an exclusion for your Solution Folder. See documentation if you are using Windows Defender. Microsoft Support
I've just had this same error and then realised Dropbox was running. I closed Dropbox and then the build completed successfully.
Thank you qwerty13579! How stupid of me, the solution is obvious. I have tried all sorts of things suggested over the internet, and even with the most recent version of VS Community 2017 (15.9.9), the bootstrapper failure pops up erratically, but with increasing frequency, to the point of frustration this past week. The principle: It doesn't succeed reliably, so it also doesn't FAIL reliably. The solution: Click the Publish Now button and watch the output panel. When it's that clear that it's failing, click the Publish Now button again immediately. Keep at it until it succeeds! Each round only takes a couple of seconds, much less time that it takes to re-build, take down anti-virus, and all that fancy stuff.
In my case, I traced the problem to an incorrectly dated setup.exe file in the bin\Release\app.publish folder of my application. When it fails, Publish Now creates an setup.exe that's two years earlier than the current day. When it succeeds, the setup.exe file is correctly dated.
Got the same problem. I disabled Windows Defender real-time protection and it worked. I also added the folder where the solution is saved in exclusions for Defender, and that allowed me to publish as well.