Playground does not execute on first chapter

None of the solutions works for me. I have Xcode 9.3 with Swift 4.1, newest release of Cocoapods. Here are my error in the playground. This is totally frustrating…
Playground execution failed:

error: Couldn’t lookup symbols:
__T07RxSwift14ObservableTypePAAE2ofAA0C0Cy1EQzGAHd_AA018ImmediateSchedulerD0_p9schedulertFZ
__T07RxSwift10ObservableCyxGAA0C4TypeAAWa
__T07RxSwift10ObservableCMa
_T07RxSwift14ObservableTypePAAE2ofAA0C0Cy1EQzGAHd_AA018ImmediateSchedulerD0_p9schedulertFZfA0
__T07RxSwift14ObservableTypePAAE4justAA0C0Cy1EQzGAHFZ

I get the same thing - have you found a solution?

Using pods version 1.3.1 worked great for Xcode 9.3 with Swift 4.1
You guys are good.

Yup.

Works with cocoapods v 1.3.1

sudo gem uninstall cocoapods
sudo gem install cocoapods -v 1.3.1

1 Like

This worked for me. Here are my steps:

  1. Uninstalled all version of cocoapods
  2. Installed cocoapod version 1.3.1
  3. Create the project as instructed in the video
  4. Performed nuke and repave

On Xcode 9.2, Swift 4.1 toolchain running, I cleared the error by adding this inside Podfile, then pod install again

# Workaround for Cocoapods issue #7606
post_install do |installer|
    installer.pods_project.build_configurations.each do |config|
        config.build_settings.delete('CODE_SIGNING_ALLOWED')
        config.build_settings.delete('CODE_SIGNING_REQUIRED')
    end
end

From https://github.com/CocoaPods/CocoaPods/issues/7689

4 Likes

@vinamelody Thanks! Finally working! (nuke did not work, did not try the submodule workaround)
Being on xcode 9.3, pod 1.5.0 (sooo glad I don’t need to downgrade cocoa pods, breaking other projects), seeing swift 4.1.2 being used with the source bundled in v2.0 of the book did the trick.

As there’s already a post_install hook and pod install complained on this. I added these lines just below the existing line post_install do |installer|:

installer.pods_project.build_configurations.each do |config|
    config.build_settings.delete('CODE_SIGNING_ALLOWED')
    config.build_settings.delete('CODE_SIGNING_REQUIRED')
end
2 Likes

I downgraded to 1.3.1, didn’t work. After that …

  1. I deleted the line ‘import RxSwift’
  2. Clean
  3. Build (with error)
  4. put back ‘import RxSwift’

Works!

1 Like

Thanks for that! (also works for Realm BTW) - too bad v1.5 causes that much trouble …

The script looks like this then (just to make sure - this one works):

platform :ios, ‘11.0’

target ‘RxSwiftPlayground’ do
use_frameworks!

Pods for RxSwiftPlayground

pod ‘RxSwift’, ‘~> 4.0’
end

post_install do |installer|

installer.pods_project.build_configurations.each do |config|
config.build_settings.delete(‘CODE_SIGNING_ALLOWED’)
config.build_settings.delete(‘CODE_SIGNING_REQUIRED’)
end

installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings[‘CONFIGURATION_BUILD_DIR’] = ‘$PODS_CONFIGURATION_BUILD_DIR’
end
end
end

4 Likes

This solution works for me. Thanks

it works like a charm, thanks so much

I can confirm that this works with Xcode version Version 9.3 (9E145) and Pod version 1.5.2. Thank you so much!

Couldn’t get this to work with any of the solutions, then noticed my active scheme was an actual device. Set it to a simulator and everything worked!

1 Like

Thanks! This worked for me!

Works like a charm. Thanks.

Yeah, run pod install with 1.3.1 version works for me. And the trick mentioned by scotteg is not working.

Thanks! It worked for me.

Worked for me, thanks

Even though CocoaPods 1.3.1 and nuking and repaving worked for me on the first playground for Chapter 2, it was a real hassle to do that for all the following playgrounds from the book.

I decided to use Carthage instead, and followed this tutorial to create a workspace with a playground that has RxSwift integrated via Carthage. Worked flawlessly.

@scotteg It might be a good idea to switch to Carthage on the next edition considering Cocoapods isn’t supporting playgrounds :slight_smile:

nuke project
Recopy over
uninstall
install
install RxSwift
Clean
Build

Worked for me the 5th time trying. Could be a lot better and much easier.
Would be wonderful to have an update for this so we don’t have to do this

Thanks,~! This worked for me~!!
And, raywender unkind!!!