Skip to content
This repository has been archived by the owner on Feb 2, 2021. It is now read-only.

RxExpect expects RxTest to have been compiled with bitcode enabled #2

Open
wlucjan opened this issue Jan 3, 2017 · 10 comments
Open

Comments

@wlucjan
Copy link

wlucjan commented Jan 3, 2017

I am getting following error from linker when I try to run my tests:

RxTest/RxTest.framework/RxTest' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE)

Here is my podfile:

target App
  ...
  target 'AppTests' do
    inherit! :search_paths
    # Pods for testing
    pod 'RxTest'
    pod 'RxExpect', '~> 0.2'
  end
end

Test target has disabled bitcode.

Any idea what's wrong?

@devxoul
Copy link
Owner

devxoul commented Jan 15, 2017

@wlucjan, sorry for delay. I didn't realize that I'm not receiving any notifications from this repo 😱 Anyway, could you try again with 0.3.0 release?

@wlucjan
Copy link
Author

wlucjan commented Jan 16, 2017

I get the same error.

Installing RxExpect 0.3.0 (was 0.2.0)
Using RxTest (3.1.0)

@devxoul
Copy link
Owner

devxoul commented Jan 17, 2017

Hmm. that's weird. Could you try with new project?

@DriesSchulten
Copy link
Contributor

DriesSchulten commented Jan 18, 2017

Same here, just added RxExpect, 0.3.0 with RxTest 3.1.0, on clean build it gives the bitcode error.
RxTest/RxTest.framework/RxTest does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target

@devxoul
Copy link
Owner

devxoul commented Jan 18, 2017

@wlucjan @DriesSchulten what is the ENABLE_BITCODE value of your project?

@wlucjan
Copy link
Author

wlucjan commented Jan 18, 2017

Like mentioned in my first post - Test target has disabled bitcode.
Yet both Release targets have enabled bitcode.

@devxoul
Copy link
Owner

devxoul commented Jan 18, 2017

@wlucjan could you please try with a new project? I cannot reproduce this issue.

@DriesSchulten
Copy link
Contributor

DriesSchulten commented Jan 18, 2017

I've tried to reproduce it with a new project; but I haven't been able to so far. I don't know what triggered it in the normal project; added it yesterday and it was working; after some clean/rebuild actions it was giving this error today.

I will try some more.

And indeed bitcode is disabled.

Update: when I build the test against the simulator it works, when I build it against an actual device it gives the error.

Maybe related to: Quick/Nimble#170, also error when deploying to actual device.

@ValeriyKliuk
Copy link

I have the same error using Carthage:
Cartfile
github "devxoul/RxExpect" ~> 0.5

$ carthage update --platform iOS

*** Fetching RxExpect
*** Fetching RxSwift
*** Downloading RxSwift.framework binary at "Naldi"
*** Checking out RxExpect at "0.5.0"
*** xcodebuild output can be found in /var/folders/16/07q__61d5tbddh51nly_g3vw0000gn/T/carthage-xcodebuild.FYNGty.log
*** Building scheme "RxExpect-iOS" in RxExpect.xcworkspace
** BUILD FAILED **

The following build commands failed:
CompileSwift normal arm64
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(2 failures)
/Users/valeriykliuk/Documents/Bitbucket/TestLab/RxApp3/Carthage/Checkouts/RxExpect/Sources/RxAssertion.swift:25:8: error: no such module 'RxCocoa'
A shell task (/usr/bin/xcrun xcodebuild -workspace /Users/valeriykliuk/Documents/Bitbucket/TestLab/RxApp3/Carthage/Checkouts/RxExpect/RxExpect.xcworkspace -scheme RxExpect-iOS -configuration Release -sdk iphoneos ONLY_ACTIVE_ARCH=NO BITCODE_GENERATION_MODE=bitcode CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** BUILD FAILED **

The following build commands failed:
CompileSwift normal arm64
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(2 failures)

carthage-xcodebuild.FYNGty.log

RxApp3/Carthage/Checkouts/RxExpect/Sources/RxAssertion.swift:25:8: error: no such module 'RxCocoa'
import RxCocoa
^

@giboJK
Copy link

giboJK commented Oct 26, 2020

I got the same error when only I tried to test with real device.

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

No branches or pull requests

5 participants