Breaks autocompletion of imports from CocoaPods about fuzzyautocompleteplugin HOT 13 CLOSED

What does 'misbehaving' actually mean? It doesn't show the full paths, only entires for that level? A reproduction GIF would be tops too

from fuzzyautocompleteplugin.

What's the best way to capture the GIF?

from fuzzyautocompleteplugin.

http://www.cockos.com/licecap/

from fuzzyautocompleteplugin.

Thanks. Now that I try to reproduce the problem, it's working fine. What the what… I verified this 4 times over before reporting the issue. Xcooooode!

from fuzzyautocompleteplugin.

So I just found out that FuzzyAutocomplete stopped loading after 5.1 (totally forgot about that). I think I see the issue. If you autocomplete ReactiveCocoa/, then it doesn't autocomplete the files anymore. Is that right?

from fuzzyautocompleteplugin.

Partially: sometimes it will complete the first part (ReactiveCocoa/) other times it won't. Sometimes it completes the second half, other times it won't. I can't get a consistent reproduction of the issue — sorry mate — I'd be keen to see what you find now that you're using the plugin again 😉

from fuzzyautocompleteplugin.

I'm not sure when I'll have time for Obj-C. I'm having a look now though

from fuzzyautocompleteplugin.

Wtf. I can't reproduce it now either.

from fuzzyautocompleteplugin.

Maybe it's the indexer being screwy? It seems that once you have one good match it starts working again!

from fuzzyautocompleteplugin.

Possibly.. I don't do anything with the indexer though.

from fuzzyautocompleteplugin.

I wasn't suggesting that you are — Xcode is a fickle beast!

from fuzzyautocompleteplugin.

Yep, it has to be the indexer... at first it won't autocomplete, then while you are swearing like a sailor it starts working again.

from fuzzyautocompleteplugin.

I fixed this issue by going to "Build Settings" > "Build Options" and setting "Precompiled Header Uses Files From Build Directory" to "Yes".

from fuzzyautocompleteplugin.