My projects on Visual Studio 2019 were working fine. There was an auto-update and since then, I keep getting this annoying message:
Please wait for an editor command to finish.
Is there a solution to this?
I have fixed that problem by deleting .vs folder from project.
update
Some times .vs may be hidden in solution folder make it visible from folder option
Like as Akbar Asghari said, just delete .vs folder from project (located in the root solution, this folder is system hidden).
Close the VS or kill the task.
Delete the folder .vs
Reopen solution and be happy.
Version: Visual Studio Community 2022 (17.3.6)
I tried the provided solution of deleting the .vs folder from the project without success. However, my problem seemed to go away when "Automatic brace-completion" was disabled.
Note: My problem was specific to editing a small JSON file. Maybe this will help others have an idea what to look for.
When I updated and added some more Rapid XAML extension in VS 2019 I started to get this message. So I deleted these extensions and it solved the problem but I also deleted the .vs folder in the solution I was working in. However this was happening in all the solutions so I think it was the extensions that was causing the issue.
I had a simmilar issue but the other methods did not work.
I have activated GitHub Copilot lately. A while it worked flawlessly (I guess Copilot was watching during the first period of time). Then, the already included AI of VS2022 - namely ItelliCode - and Github were active at the same time and caused crashes.
When I disabled either IntelliCode or Copilot, I had no more crashes.
To disable IntelliCode you can go to Tools->Options->IntelliCode and disable "C# suggestions".
Or disable Copilot: Tools->Options->GitHub->Copilot and set "Enable Globally" to false.
Had the same problem and even after doing what Akbar Asghari said, it didn't work. Then I reset the Keyboard Shortcuts of VS22 Mac to default i.e. Visual Studio for Mac and it resolved the issue. I had set it to VSC Keybindings earlier.
Link to Screenshot
After unchecking the box Auto cancel long running auxiliary operations on typing in Tools>Options>Text Editor>Advanced the message box does not appear anymore.
I was able to resume working normally after doing so and VS behaved normally for all the session after that.
I had installed the UiPath and accept the free license. But, once if we close the tool and again try to open it then every time it opens the installation screen and asks for a license.
Please give the solution of this issue.
Thanks.
Expected Result: Once the UiPath is installed then able to easily open it.
Actual Result: Every time needs to install the UiPath tool.
Generally, no matter what version you have, you have to activate it. Studio activated once will not ask for it anymore, for community edition you can do it here:
https://www.uipath.com/renew-community-license
I have created a Cordova 2.1.0 app, It ran fine for the first 2-3 times. But now when I am trying to run it through terminal it is giving me the following error.I didn't change anything.
Ankurs-Mac-mini:~ ankur$ /Users/ankur/Desktop/CordovaSMS/cordova/emulate
Ankurs-Mac-mini:~ ankur$ 2012-10-17 16:11:08.695 ios-sim[7032:507] stderrPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
2012-10-17 16:11:08.698 ios-sim[7032:507] stdoutPath:
/Users/ankur/Desktop/CordovaSMS/cordova/console.log
[DEBUG] Session could not be started: Error Domain=DTiPhoneSimulatorErrorDomain
Code=1 "iOS Simulator failed to install the application." UserInfo=0x7fc643902320
{NSLocalizedDescription=iOS Simulator failed to install the application.,
DTiPhoneSimulatorUnderlyingErrorCodeKey=-1}
any help would be appreciated.
Thanks
Solved the problem
Deleting contents of ~/Library/Application Support/iPhone Simulator and re-run the project solved this problem.
or you can simply reset content and setting of the simulator.
Try manually launch the iOS Simulator and from the "iOS Simulator" menu, click "Reset content and settings", then close and rebuild your app.
My solution is:
From menu, iOS Simulator, Reset Content and Settings.
Close XCode 5.0: close project and close it from Dock and re-open the project and launch again, like in Windows :)
I tried everything mentioned above and nothing worked. My problem was iOS 7 specific. I was finally able to resolve the issue by assigning a non-empty value to Bundle versions string, short (CFBundleShortVersionString) in the -Info.plist file. Looks like iOS 7 doesn't like an empty value for the build number. I had a script that auto increments the bundle number by 1 every time I build the project so this field was empty. I just assigned a dummy value there to get it working.
You can also remove the app from the simulator.
This worked for me in iOS6.1
Solved here: https://stackoverflow.com/a/16279286/1927253
I copied a folder into XCode 4.6.2 with the name "Resources". When XCode asked, I created the folder references for any added folders.
Every time I did this, I would have to goto the Derived applications directory, and delete the build directory for my project to get it working again.
Solution: Do not copy a folder by reference into XCode with the name "Resources". Rename it to something else other than Resources.
Very annoying error.
just reset your simulator and re-run your project
Unfortunately none of these solutions solved my problem. I did everything, even restarting my mac but it was still failing. What actually did solve my problem was to go to the Organizer and delete the Derived Data and Snapshots.
Had the same problem after installing XCode 5. Had no iOS 6.1 Sim or SDK. Obtained these. Tried to run the App up under the iOS6.1 Sim and go the failed to install message. Having read through all of the above posts, I decided to simply remove the App from the Simulator and re-istall, re-run from the project window and that solved it for me.
I tried ALL these things and more including reinstalling Xcode 5 and nuking every xcode and simulator preference/application support file with no luck.
Then for the hell of it, I CHANGED my short bundle version string (it already had a value, it was not empty), and it fired right up.
3 hours gone but yeah
All the answers I looked for do not work for me!.
Finally
The only way to make it work is as follows
1.Check the version of titanium being used for the project in tiapp.xml
2.right click the prject in the project explorer window.
3.Select Properties
4.Choose project build path. Select Titanium Mobile SDk all versions of 3.* Tick all of them.
5.Now click apply and re run the project.
None of the above worked for me, I finally compared my info.plist to another project and found that I had somehow deleted the "Executable File = ${EXECUTABLE_NAME}" key/value pair, replacing it fixed the problem for me.
This error occurs on iOS 7.0 if you leave the "Build" empty.
Enter a build number!
What worked for me was to simply delete an old version of the app, which was made in a prior version of Xcode (likely 4, now running 5) from the simulator (tap-hold, jiggle, x).
I encountered this problem while trying to create a build for Facebook application approval. I found that for some reason, when I used the following command line:
xcodebuild -arch i386 -sdk iphonesimulator7.1 -scheme Mana -configuration Release
the files didn't end up in [project root]/build/... (as the instructions on Facebook suggest), but in ~/Library/Developer/Xcode/DerivedData/[app name + unique identifier]/Build/Products.
I'm not sure exactly what's going on here (anyone who knows more please enlighten me!) but I was able to run the files in the DerivedData directory on the simulator. Hopefully they'll also work for Facebook!
I tried everything mentioned above and nothing worked.
Finally the only way to make it work was unsetting DYLD_INSERT_LIBRARIES=/usr/lib/libimckit.dylib
How I did this:
Open terminal and typing "sudo vi /etc/launchd.conf"
Changing
"setenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
to
"unsetenv DYLD_INSERT_LIBRARIES /usr/lib/libimckit.dylib"
Save changes
Reboot your system
In this post [1] explain what DYLD_INSERT_LIBRARIES is for
[1] https://stackoverflow.com/a/26053165/2091181
On Mavericks 10.9.5 using Xcode Version 6.0.1 (6A317) with an iOS SDK supporting 8.0 originally had Simulators all version 8 all getting this error. All the advice above was not working for me. So went to Xcode->Preferences->Downloads and saw as installable (but not yot installed) in the Components section were iOS Simulators 7.1 and/or 7.0. Went ahead and installed the 7.1 Simulators and got extra designations on the Product->Destination list Simulators of version 8.0 and 7.1, and using the 8.0 still had the same error, but the 7.1 Simulators all worked.
I'm trying to install subclipse 1.6.x onto Aptana Studio 3 (build 3.0.7.201112151935). It isn't working cause once I've clicked that I accept the licence agreements the finish button doesn't light up.
I've tried rolling back the configuration history, closing and reopening and installing 1.8.x. 1.8.x worked once, but isn't compatible with my SVN repo so that's no use.
Any guesses/solutions?
Thanks in advance
Rob
There is a bug in Eclipse where the Finish button does not show up. It was fixed, but maybe Aptana is not using the latest version. I seem to recall you could click Back and then Next and the button would enable.
Here are some Eclipse bugs on this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=136907
https://bugs.eclipse.org/bugs/show_bug.cgi?id=149300
For me I found that there were sub-packages which couldn't be installed.
Bad Components:
Mylyn
Revision graph
These were identified as bad on the sub-components selection screen, however, when this is done, and the licenses are accepted, the "Finish" button does not get highlighted.
I Found that if you remove this bad components on the initial "Available Software" screen (and not on the sub-componets selection screen) and continue, that you the "Finish" button gets highlighted and you can proceed with installation.
More precisely, I am facing this issue while trying to install https://github.com/barraponto/thacker-profile (commit 75c693581796eddae5fc39870dfcc2647e00c81b shows the bug, I will update if i can fix it).
It happens that if the sitename variable is already defined, drupal halts its installation.