Pod installed Alamofire 4.4, but class is not being autocomplete by Xcode 8.3

Question

I have noticed this problem as closed before but I am getting the same problem.

screen shot 2017-05-12 at 10 56 07 am

P.S - I have imported Alamofire in the class mentioned in the screenshot

Here is my pod details

platform :ios, '10.0'

use_frameworks!
target 'PhotoTagger' do
     pod 'Alamofire'
end

Also the only thing being auto completed is AlamofireVersionNumber and i cannot access anything when I am trying to use the auto complete feature. Now if i write Alamofire by hand then I can access some methods, but then again something is going wrong and code is not compiling, which i think boils down to the issue that the class isnt being fetched by auto complete.

I have tried -

In Project settings > Build settings

Always search user path To YES
Header search path to only include "$(inherited)" as non-recursive

All other pods are working fine, except Alamofire. Also after writing class name by hand or copy pasting, some of the methods that are being auto completed does not have the same signature of the actual method of the Alamofire class

Please please please !! help me sort this out, so that someone out there when facing this can help themselves too. There isnt any solution to this as of now.

P.S

I had opened an issue on Alamofire's Github page, but they responded with

Sorry, we're not responsible for Xcode's autocomplete issues.
In the future, you should open questions like this on Stack Overflow
and tag alamofire.

Cheers.

Please help, I am stuck with this for quite some time.

EDIT :

Here is my project settings details Also, I have build the project and still the problem persists.

P.S - Writing the class manually by hand , and the methods even, it compiles but everytime, I have to go to the github page, to copy paste the method signature, The problem is that with Autocomplete, i can navigate all method signatures and know about the public available methods. But I am only restricted to the example methods available in github, as everytime I have to copy paste the methods and the overwrite the implementation. Again, this compiles and runs, but the auto complete is not working, not for the class, or for the functions.

Please read the question, it already says I did import the framework — Saheb Roy, May 29 '17 at 05:58
First line after the image `P.S - I have imported Alamofire in the class mentioned in the screenshot` — Saheb Roy, May 29 '17 at 06:21
Please try to delete Derived Data for the project, restart your mac and restart Xcode, all the "magic" — Matz, May 29 '17 at 09:13
Tried all! Funny thing is, this is reproducible in other mac as well — Saheb Roy, May 29 '17 at 09:28
Yes, but its a overkill isnt it? I am trying to find the solution to this problem. — Saheb Roy, May 29 '17 at 12:00
I had the same problem once. Can you check what is displayed in: "build setting -> Search path -> Framework Search Path" for your target and post it in your question? Sometimes it helps to build the project for autocompletion to work. — JoakimE, Jun 02 '17 at 14:11

MGY · Answer 1 · 2017-05-31T09:38:47.297

1

Solution 1

Probably this is not about Alamofire or pod libraries but Swift and XCode. This answer could be your solution, shortly:

Go to Xcode > Preferences > Text Editing Under Code completion
Uncheck 'Suggest completions while typing' Quit out of Xcode and then
relaunch Xcode. Go to Xcode > Preferences > Text Editing again Again
go to Code completion and check 'Suggest completions while typing'.
Try typing library function or enum...

Solution 2

Or you can try this answer if your XCode have some cache file issue, shortly close XCode and remove file below:

~/Library/Caches/com.apple.dt.Xcode

and try again.

Solution 3

Or you can try this answer, shortly:

Find any commented out (/* abc */) code after @end in your files and delete.

Let me know if any solution it works.

edited May 31 '17 at 09:38

answered May 31 '17 at 07:10

MGY

7,245
5
41
74

Please be sure that all files in your code working correct, no errors in other classes, sometimes this can cause this problem, but X Code will not say this but just stop working correctly. – MGY May 31 '17 at 08:36
Yes build successfully but still problem persists – Saheb Roy May 31 '17 at 08:45
Tried solution 2 and 3 both, didnt work P.S - This is only for Alamofire, for all the other pod I have installed, everything is working properly ie autocomplete and class recognition is working – Saheb Roy May 31 '17 at 09:50
Strange but solution 1 was the one that fix the problem. Is there some explanation why? – m1sh0 May 16 '18 at 15:09

JoakimE · Answer 2 · 2017-06-02T14:37:54.657

1

I had the same problem once. I can’t remember exactly what worked, but we will figure that out now.

In «Build Settings -> Search path -> Framework Search Paths» check to see if you have the following:

Always Search user Paths : NO
Framework Search Paths: $(inherited), "$PODS_CONFIGURATION_BUILD_DIR/Alamofire", "${PODS_ROOT}/Alamofire/"

These search path might not be the same as yours, so just double check that the path above is correct, according to where the files are saved.

Before you do changes in the config files, take a backup in case something get's messed up.

When you do changes, build your project and restart Xcode.

I just did a test project with Alamofire:

Installing pod: pod 'Alamofire', '~> 4.4'

Opening xcworkspace first time: Autocompletion doesn't work. Xcode doesn't recognize import Alamofire.

Then:

Build project: Project -> Build

Xcode recognizes import Alamofire.

When typing Alamofire it doesn't work, only AlamofireVersionNumber is autocompleted.

But when typing Alamofire.(and typing a known command from alamofire it will autocomplete)

edited Jun 02 '17 at 14:37

answered Jun 02 '17 at 14:23

JoakimE

1,820
1
21
30

Yes I know, manually writing upto a part of Alamofire.Post then it gets auto completed, My Question is why isnt the class being recognised and being auto completed. This is a huge setback, as normally we use auto complete to get to know the public classes available, rather than going to the source file for documented methods and their signatures. Also , I am editing the question, Your suggestion didnt work – Saheb Roy Jun 05 '17 at 05:42
It's not working as expected. Really annoying thing. It seems to be that only some frameworks are affected. I haven't had any problems using e.g. Firebase before. It could be some CocoaPods settings for Alamofire issue. – JoakimE Jun 05 '17 at 13:42
I have literally tried everything, I have reset my pod setup in my local repo, reinstalled cocoapods, reset pod setup reinstalled xcode even. – Saheb Roy Jun 05 '17 at 13:47

score 1 · Answer 3 · answered May 07 '18 at 13:25

For me adding anything to the Build Settings didn't work, but deleting Derived Data and building the Pod scheme explicitely did the trick.

Go to "Manage Schemes" and check the Pods-MyProject scheme and the one of the pod which doesn't autocomplete. Close the window. First select the scheme of the broken pod (button next to the run and stop button) and Build for Running shift + cmd + R. Second select the Pods-MyProject scheme and Build this for Running too. Switch back to your normal scheme and you should be fine.

score 0 · Answer 4 · answered Jun 02 '17 at 13:59

0

Did you delete the derived data for your project or the whole of it? I've had this happen, wipe it all.

answered Jun 02 '17 at 13:59

Fernando Mazzon

3,562
1
19
21

score 0 · Answer 5 · answered Jun 07 '17 at 07:33

I had this exact problem a few days back. I think this is happening because Xcode is not able to find the Alamofire header libraries. What I did to resolve was :

1) Go to build settings and search for 'User Header Search Paths'

2) Enter its value as "${PODS_ROOT}/BuildHeaders" including the quotes

3) Click the thing again and in the right side , change the value of the selection to 'recursive'

Now Restart Xcode and build the project. Now the autocomplete works fine

score 0 · Answer 6 · answered Jun 07 '17 at 07:34

0

Sometimes when you install some pod from the terminal's window you need to restart xcode or also the mac, before see the import name correctly.

answered Jun 07 '17 at 07:34

Andrea Merli

85
1
7

Well this is the first step that I do, after pod installing, i restart the xcode. But again, this does not work – Saheb Roy Jun 07 '17 at 09:46

score 0 · Answer 7 · answered Jan 16 '18 at 21:14

0

Unfortunately this is Xcode being stupid. Same issue is happening with most advanced libraries even when using server side SPM. Until apple improves xcode some things will just stay hidden to us unfortunately.

I am currently using Xcode 9.2

answered Jan 16 '18 at 21:14

Ondrej Rafaj

4,342
8
42
65

score 0 · Answer 8 · answered Jun 18 '19 at 10:12

0

Just go for a build after removing any code with error (any incomplete alamofire call attempts or so).

answered Jun 18 '19 at 10:12

Rémi Belzanti

413
5
12

score 0 · Answer 9 · answered Oct 01 '19 at 01:29

0

SOLUTION

Start by writing "AF" and then the desired function.

AF.request(url...

AF is global namespace containing API

answered Oct 01 '19 at 01:29

Murphy

849
7
6

score -1 · Answer 10 · answered May 29 '17 at 06:14

-1

Your pod string may be wrong. Please try this

pod 'Alamofire', '~> 4.4'

Thanks.

answered May 29 '17 at 06:14

Bala AP

37
5

I have tried this but this does not work as well. Also, not giving a version in the podfile, will automatically fetch the latest version of the pod. here it is 4.4 – Saheb Roy May 29 '17 at 06:21

Pod installed Alamofire 4.4, but class is not being autocomplete by Xcode 8.3

P.S

EDIT :

10 Answers10

Solution 1

Solution 2

Solution 3