I am having a weird problem with Xcode where it keep indexing and takes long time to do that. Search functionality also does not work properly. It searches in all framework/library files instead of project files. I tried with my other project but that project has no problem. So I guess it is something wrong with my project...But I am not able to find out. Can anyone help?
Found out answer to my own question... I deleted workspace file in .xcodeproject package. Then When I opened the project in xcode, it still took time because it has whole "Application" folder under the project. I removed the reference to it and reopened it and now it works fine. It didn't affect the git repository for me.
Related
What to do I'm doing a project with a friend and I'm throwing him the project files, he opens the project and shows this error in Unity Hub, this did not happen before, and after one moment it began to appear, I don't have such an error, the Internet is almost empty about it. What to do?
nice error
I solved the problem, I just needed to create a new folder for projects
I solved the problem, I just needed to create a new folder for projects
There are some solutions online eg. here
It seems like one possible solution is related to the Crash Handler or related to git VC.
One simple common solution is
One interim test solution is to try copying the Assets/ and ProjectSettings/ and Packages/ file to a brand new directory somewhere, then try opening that.
Every time I look for a file using the files finder console the file does not show up as a result of the search despite its existence in the project.
At certain point this feature was working but I may have change some configuration in Rubymine involuntary. Any help it's welcome!
That's a known issue already fixed: https://youtrack.jetbrains.com/issue/IDEA-266391
Builds with the fix will be added to that issue so you can follow it.
As a workaround, please try invoking File - Invalidate Caches (still the issue might come back).
Just to get some context here is a screenshot, though you probably gathered this from the title:
Xcode is marking all symbols as undeclared, usually this would be because it doesn't exist or isn't imported, but in this case it was working fine 20 minutes ago and weirdly the project compiles and runs with no problems.
When I compile the errors go away but there is no syntax highlighting, as soon as I start to edit the file the errors all come back. I can work if I remember the exact signatures for anything that I need to use but with the lack of code completion and errors this is very hard.
Notably this is only a problem in a few source files, its not even the whole project. Nothing has changed that I am aware of that could cause this.
Before anyone suggests it, I have tried cleaning, deleting derived data/build folder, restarting Xcode etc...
My colleague is seeing the exact same issue on his machine.
So I managed to fix the offending source files, I just compared their attributes to those of a working source file and it turns out that the problem files included the tests project in their target membership and the working file did not. I'm not sure why this is causing the issue as other projects use automated testing without a problem. Nonetheless this solved it for me, at least until I start writing test cases...
kinda awkward asking this. But I cant seem to find the solution, because I dont know how/what to search in google. It goes something like this. In my project folder, whenever I click my Project.xcodeproj the latest code I have edited there was right or what I meant is when opened in XCODE it is updated.
Problem:
For example, when I try to unzip my latest project from the latest zipped project( for back-up purposes ) when I open the folder( back up ) then click for example View1Controller.m the codes in it arent updated the way they are in the XCODE though if I click the xcodeproj part. It is updated in the XCODE.
Hope someone could help me with this, and explain some good ways/solution for my prob. Thanks.
I assume that you are zipping old projects and saving them to avoid using git - I'm no git lover but for sure its a better solution.
The problem with trying to use Xcode to view old and new projects at the same time is (IMHO) is that Xcode seems to get confused about what file is in what project - if you have a new one and old one open.
open the old file in TextEdit, it should be exactly what you think it should be
in Xcode, have the current project open, look at some files. close the project, and open the older project. look at the files, they should be correct [if they are not, close and reopen Xcode between project openings, but I suspect this is not necessary]
if you really need to see the files from the old project while viewing the new ones, then in the Finder rename the file - put a "O" prefix on the file, then open that file (with the modified name) in Xcode
My experience is dated on this issue to older releases, but I do strongly recall having this kind of problem in the past.
If you press Shift+Ctrl+T or choose "Navigate > Open Type..." you get the "Open Type" dialog for quickly navigating to a known class. When you start typing a name only the classes for which the name matches stay visible. That way you can find a class of which you know the name very quick without having to browse through the package explorer tree.
This has been working great for me up until this morning. All of a sudden for a couple of my projects I am only seeing some of the types that exist. Of course I tried the obvious steps of refreshing the projects, cleaning the projects, re-building the projects, rebuilding the projects externally, but all to no avail. It is a bit odd since the types are known in other places. If I add an import statement Eclipse does not complain that it doesn't know the type and I can Ctrl-Click through the types to get to their file. However, the type navigation knows nothing about them.
In the past when InteliJ used to do this to me I would go find its cache files and delete them forcing it to rebuild. Does Eclipse have something similar I might do (I'm an Eclipse newbie)? I am using Eclipse 3.4.2 and I have it configured to not delete files on a clean (because our actual build process puts files into the output directories that I don't want Eclipse mucking with).
Have you tried closing and reopening the project? Only types from open projects are held in memory, and the refresh occurs when you Shift+Ctrl+T for the first time on a newly opened project.
Edit to add: Ctrl+Shift+R also displays the types (along with everything else) but it also supports the Camel-case thing to find the Java types quickly.
Close eclipse and delete any .index files and the savedIndexNames.txt file in workspace/.metadata/.plugins/org.eclipse.jdt.core once eclipse is restarted it will rebuildl the entire index for Ctrl+T
try starting eclipse with the -clean flag, you can add this to your eclipse.ini which can be found in the same directory as you eclispe.exe, or if you start eclipse using a bat or shell script, add it as a startup argument, e.g. eclipse -clean.
The clean will tidy your workspace, and should force eclipse JDT to recalulate types. Ive had issue with .snap files (with seem to be created on dirty shutdowns) that seem to corrupt my workspace until I clean them up, not long ago eclipse lost the Object class!! made for some interesting errors!
I get problems like this often. I tried your solution, noticed it seemed to rebuild its search index, but I still couldn't find any of my classes. Then I took a look at the little green arrow on top right corner of that dialog, and noticed I had a working set selected which belonged to another project. I find it a little dumb that Eclipse doesn't warn you about this or anything, since this can be a very annoying little detail that one tends to forget (me at least ;-)).
Anyways, clicked on "Deselect Working Set" and bam I can find my classes again. Thought I'd add this here since others may make the same mistake.
This worked for me -
Select your project in Package Explorer
Press F5 or Right click and select Refresh
I used the "-clean" as first line in the eclipse.ini (version Juno) and worked like a charm.
I'v tried all the answers and I still had the issue. I then tried this:
I deleted the project (it's a maven project) and re-imported it. This time I made sure i check the "Add Project(s) to working set" checkbox. After that Eclipse was able to find the classes in that project.
The problem must have started because I didn't check this checkbox when i first imported this project.
By the way, I'm using Neon
(Warning: Shameless marketing ahead)
If you like this feature, you would love nWire. nWire allows, among other things, to quickly search not only for types, but for any possible Java element like method or field. It also uses a navigator view which is non-modal. After searching you can see the class associations in a very quick and easy way. Check out the video on our site.