Skip to content

install with cocoapods, but no such module Quick #731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ondev opened this issue Aug 4, 2017 · 14 comments
Closed

install with cocoapods, but no such module Quick #731

ondev opened this issue Aug 4, 2017 · 14 comments

Comments

@ondev
Copy link

ondev commented Aug 4, 2017

today, I try to use Quick in my project, after pod install, I try to import Quick,
but get the error: no such module Quick

xCode:8.3.3
cocoapods:1.3.0
Swift: 3.1

@ikesyo
Copy link
Member

ikesyo commented Aug 8, 2017

Are you sure that you are opening an xcworkspace file geneated by cocoapods instead of an xcodeproj file?

@ondev
Copy link
Author

ondev commented Aug 9, 2017

Pretty sure

@ikesyo
Copy link
Member

ikesyo commented Aug 9, 2017

What is the Quick version?

@Lopdo
Copy link

Lopdo commented Sep 3, 2017

I am facing same problem

xCode:8.3.3
cocoapods:1.3.1
Swift: 3.1
Quick 1.1.0

I am opening xcworkspace, we are using about 20 different pods and only this one throws this error.

our podfile looks like this:

platform :ios, '9.0'
use_frameworks!

target 'ourAppName' do

	pod 'Alamofire', '~> 4.4'
	pod 'AlamofireObjectMapper', '~> 4.1'
	
        ... snip.... 

	pod 'Firebase/Analytics', '~> 3.2'
	pod 'Firebase/Auth', '~> 3.2'
	pod 'Apptimize'
	pod 'OHHTTPStubs'
	pod 'OHHTTPStubs/Swift'


    target 'ourAppNameTests' do
        inherit! :search_paths

		pod 'Quick'
		pod 'Nimble'

		pod 'Firebase'
		pod 'Apptimize'

    end

    target 'ourAppNameUITests' do
        inherit! :search_paths

		pod 'Firebase'
		pod 'Apptimize'

		pod 'Quick'
		pod 'Nimble'
    end

end

@AlexKel
Copy link

AlexKel commented Sep 11, 2017

Try the following:

  1. Open xcode schemes list.
  2. Tick Nimble and Quick with "show" and close.
  3. Select Nimble as a scheme and build (cmd + b)
  4. Select Quick as a scheme and build (cmd + b)
  5. Change scheme back to your app scheme and see if the error is gone and autocompletion works.

This is what I have to do from time to time.

@ikesyo
Copy link
Member

ikesyo commented Sep 28, 2017

Closing this due to inactivity.

@ikesyo ikesyo closed this as completed Sep 28, 2017
@Shagee08
Copy link

I'm also having this issue. It seems that any pod I try to import now is nonexistent. I can't import FirebaseMessaging or Locksmith even though they're in the podfile that I'm importing from. I hope someone can help.

@edisonjoao
Copy link

right!!! this is getting frustrating

@greesh4
Copy link

greesh4 commented Jan 18, 2018

I too have the same issue . I removed the pod to which it was giving error and then it chose the next pod as not existing . Dont know what to do with this . I have opened the this stack overflow thread . But no luck till now .
https://stackoverflow.com/questions/48306879/no-such-module-fbsdkloginkit?noredirect=1#comment83640455_48306879

Some one please help to find the root cause so that this can be resolved forever rather than providing the workarounds without knowing the root cause . its been a while and i am really fed up with this .

@ratan93
Copy link

ratan93 commented Mar 8, 2018

Hello All,

Try using pod update after pod install command which will solve problem of No such module.
I just tried and it working fine.

Thanks,
Ratneshwar

@DullBottle
Copy link

Hello everyone,

I use command + U to compile Quick and Nimble, then the error will gone.

@revolter
Copy link
Contributor

Is it because (some of us maybe) are using them in an Objective-C project?

@davidseek
Copy link

davidseek commented May 26, 2020

Try the following:

  1. Open xcode schemes list.
  2. Tick Nimble and Quick with "show" and close.
  3. Select Nimble as a scheme and build (cmd + b)
  4. Select Quick as a scheme and build (cmd + b)
  5. Change scheme back to your app scheme and see if the error is gone and autocompletion works.

This is what I have to do from time to time.

This worked for me, but how am I supposed to do that in a CI environment?
Because my CI is not building because of the same problem.

@NousPradeepN
Copy link

Clean and Build fixed me the problem. In Xcode select Product -> Clean Build Folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests