asmallteapot / cocoapods-playgrounds Goto Github PK

Most Pods will have a simple usage example in their README. We could take the first MD code block with Swift syntax from the Pod's README and add it to the Playground's Contents.swift for an even quicker start 🚀

I'm trying to 'pod playgrounds RxSwift,RxCocoa,ChameleonFramework/Swift' and getting an "unable to find specification for 'Swift'" error. It has no problem grabbing the objective-C cocoapod at 'ChameleonFramework', but trying to grab the subspec fails.

I see that the playground CLI tool supports specifying the --platform, but not when using pod playgrounds. Can you add this? :)

For Mapper I have defined module_name to be Mapper since I had to push it to CocoaPods as ModelMapper. It seems like when defining this key, importing either ModelMapper or Mapper in the generated playground ends up with a No such module error.

I run pod playgrounds RxSwift and immediately build on xcode 8.2 and get this error.

After upgrading to CP 1.0.0 the playground produced by the plugin can't find it's pods, like so:

pod playground RealmSwift ->

Please add this to home brew.

Running xCode 7.3

have tried to delete the derived data and rebuild as in another issue but still no luck

import XCPlaygroundPage
XCPlaygroundPage.currentPage.needsIndefiniteExecution = true

is replaced by

import PlaygroundSupport
PlaygroundPage.current.needsIndefiniteExecution = true

This change was mentioned in Session 213 at WWDC 2016.

Reference

This is rather a feature request.
Whenever I have big changes to the pod, such as new files or new dependency added, I need to update the playground.
However, at this time pod playgrounds runs in "generate" mode and wipes all my code in old playground.

It would be helpful to have an "update" option to preserve playground code and pages, or make "update" a default operation mode.

Just installed cocoapods-playgrounds-1.2.0.
Then ran:
pod playgrounds DateTools
After opening the workspace in Xcode 7.3.1, I built the DateToolsPlayground schema.
If I then open the playground, the line import DateTools has a compiler error "No such module 'DateTools'".

It was easily fixed by dragging the Frameworks/DateTools.framework to the DateToolsPlayground target's 'Linked frameworks and libraries'. It would be great if you could add this last step so no manual intervention was required.

(Aside, thanks for the handy tool!)

SWIFT_VERSION is hard-coded to 4.0 in #56, which works for many common cases. In the future, we should instead pick a version based on the requested spec(s) to be installed, a command-line option, and/or any other appropriate means.

When I try, for example, the README's suggestion of pod playgrounds Alamofire, I get the following in Terminal (with my own answers added where requested by the CocoaPods team). I haven't seen this with any other CocoaPods command, so I'm checking here first. Will bugger off if it's not your bug. ;)

――― MARKDOWN TEMPLATE ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

### Command

/usr/local/bin/pod playgrounds Alamofire

### Report

* What did you do?
  * Navigated in Terminal to an empty folder
  * `gem install cocoapods-playgrounds`
  * `pod playgrounds Alamofire`
* What did you expect to happen?
  * Expected a playground to be created with Alamofire embedded
* What happened instead?
  * Got a directory named `AlamofirePlayground` with a `Podfile` and an empty `Alamofire.xcodeproj`

### Stack

   CocoaPods : 0.38.2
        Ruby : ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin15]
    RubyGems : 2.4.5.1
        Host : Mac OS X 10.11.3 (15D21)
       Xcode : 7.2 (7C68)
         Git : git version 2.5.4 (Apple Git-61)
Ruby lib dir : /usr/local/Cellar/ruby/2.2.3/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ 611c523efb20ce5da94b0db9ef5d31f336a84d69

### Plugins

cocoapods-deintegrate : 0.2.1
cocoapods-playgrounds : 0.0.3
cocoapods-plugins     : 0.4.2
cocoapods-stats       : 0.5.3
cocoapods-trunk       : 0.6.4
cocoapods-try         : 0.4.5

### Error

ArgumentError - wrong number of arguments (2 for 3)
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-0.38.2/lib/cocoapods/executable.rb:50:in `execute_command'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-playgrounds-0.0.3/lib/cocoapods-playgrounds/workspace.rb:15:in `block in generate'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-playgrounds-0.0.3/lib/cocoapods-playgrounds/workspace.rb:13:in `chdir'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-playgrounds-0.0.3/lib/cocoapods-playgrounds/workspace.rb:13:in `generate'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-playgrounds-0.0.3/lib/cocoapods-playgrounds/command/playgrounds.rb:26:in `run'
/usr/local/lib/ruby/gems/2.2.0/gems/claide-0.9.1/lib/claide/command.rb:312:in `run'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-0.38.2/lib/cocoapods/command.rb:48:in `run'
/usr/local/lib/ruby/gems/2.2.0/gems/cocoapods-0.38.2/bin/pod:44:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

This came up while attempting to install Siesta, which has no stable release, but does have a functional '1.0-beta.6' tag. Installable and functional via a Podfile entry like:

'Siesta', '>= 1.0-beta.6'

But the comma throws a wrench in the works. It attempts to pick up the version specification as another framework.

As a side note, when attempting things like:

pod playgrounds --verbose 'Siesta, ~> 1.0-beta.6'

Relatedly I appear to have managed to get passed through (perhaps by way of workspace.rb's @cwd = Pathname.getpwd) a rm -fr ~. I can't say if it was that precise version of the commands I tried, but there were many. Suddenly (and embarrassingly) I was missing a large number of files in my home directory. I hesitate to submit this precise thing as a bug in part because I've yet to replicate it...and that's because I've yet to attempt to replicate it. Hopefully you can understand why I might be hesitant to do so.

I like to separate my playground code into many files. In a regular playground, I place swift files in the Sources folder under the playground and I can use their public classes and functions in the playground code.

In a playground with pods, it seems only the main playground code is able to import modules coming from pods. I tried adding swift files to the Sources folder under the playground and adding swift files to the project main folder as a sibling to the playground, in both cases I cannot import the pod modules.

Please let me know if I'm missing something. If not, it would be great if you could fix this.

I'm thinking this should work fairly easy:

• Build using carthage
• Add binary frameworks to the generated project
• Make the generated target depend on them

When building the generated target, the dependent frameworks should end up in the Playground's framework search path.

after running command:

$pod playgrounds Gloss,Alamofire

only the first pod works.

thanks for the awesome, lifesaver pod! is there a way we can easily add new pods into an existing playground we have created with this tool?

Sometimes you need more than one pod when you want to try something in a playground. E.g. you very often need both RxSwift and RxCocoa (and sometimes the data sources pod).

I think it'd be great if you allow for a comma separated list when specifying the pods, eg something like this:

1. if pod name command line parameter contains ","
2. split name parameter by ","
3. add a "pod podname" line for each of the pods specified

Ta -daaa 🎉

Using Xcode 9 or 10 I get this error when adding import RxSwift to playground that is embedded in workspace and pod is either shared or unshared,

cf #56 (comment)

I run the command:

carthage-play ReactiveX/RxSwift

The project and playground files are created. But got the following error message:

The file /Users/myname/Projects/Swift/ReactiveXPlayground/ReactiveXPlayground/ReactiveX.xcodeproj does not exist.

And got error in playground file too:

No such module RxSwift

What's wrong with it? Thanks

carthage-play acquia/waterwheel-swift 
/Library/Ruby/Gems/2.0.0/gems/cocoapods-1.1.0.rc.2/lib/cocoapods/executable.rb:69:in `execute_command': [!] /usr/local/bin/carthage update --platform ios (Pod::Informative)

*** Fetching waterwheel-swift
*** Fetching SwiftyJSON
*** Fetching ObjectMapper
*** Fetching SwiftyUserDefaults
*** Fetching Alamofire
*** Checking out Alamofire at "4.0.1"
*** Checking out ObjectMapper at "2.0.0"
*** Downloading SwiftyJSON.framework binary at "3.1.0"
*** Checking out SwiftyUserDefaults at "3.0.0"
*** Checking out waterwheel-swift at "4.3.1"
A shell task (/usr/bin/env git checkout --quiet c0462747a546575665f57fceeb560b5d2830b36b) failed with exit code 128:
fatal: reference is not a tree: c0462747a546575665f57fceeb560b5d2830b36b


    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:40:in `setup_project'
    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:24:in `block in generate'
    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:23:in `chdir'
    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:23:in `generate'
    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/bin/carthage-play:42:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/claide-1.0.0/lib/claide/command.rb:334:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/cocoapods-playgrounds-1.2.2/bin/carthage-play:46:in `<top (required)>'
    from /usr/local/bin/carthage-play:23:in `load'
    from /usr/local/bin/carthage-play:23:in `<main>'

I think it may have to do with the fact that SwiftyJSON is downloading a binary and not checking out?

when i run 'pod playgrounds Alamofire'
A error said '[!] Unable to find host target for Pods-AlamofirePlayground. Please add the host targets for the embedded targets to the Podfile.'

And i add 'target 'Pods-AlamofirePlayground' do ... end ' or ' abstract_target 'Pods-AlamofirePlayground' do' to my profile.But none did work. i got the same error words what like above.
How can i fix it?

my Xcode is 7.3.1, pods is 1.1.0.beta.1

thank you.

Current version doesn't work with Xcode 9.

It fails with:

Errno::ENOENT - No such file or directory - /Applications/Xcode-beta.app/Contents/Developer/Library/Xcode/Templates/File Templates/Source/Playground with Platform Choice.xctemplate

Looks like Xcode 9 comes with a different Playground templates.

running carthage-play $SOME_LIBRARY invokes xcodebuild without any user-visible output, which is not great

Thought I'd post this here, even though it may be a CocoaPods issue at heart, because this exact error came up for me when first attempting the README's example command: pod playgrounds RxSwift,RxCocoa.

After building the project, a red exclamation (!) appears next to the TCBUBYP-generated playground's import RxCocoa with this error:

Cannot load underlying module for 'RxCocoa'

This works beautiful for referencing framework from Playground file! Following example just imports 'Realm' framework that I incorporated using this CocoPod plugin.

However, if I do the same from files under Sources, it cannot reference the same framework.

Is it a known issue? If it is, is there a workaround?

gem install cocoapods-playgrounds seems to install Cocoapods 1.0.1 (latest).

I need to stay on Cocoapods 0.39.0.

Is there quick fix for this, like specifying the version?

Title barely tells about how awesome the library is. Maybe something like PodPlaygrouds?

The prerequisite for this is getting swiftpm to build dynamic frameworks. With that, the approach from #3 should work for this as well, but keep in mind to generate OS X Playgrounds in this case.

I downloaded your project and followed the instructions. The playground gives the module not found err on any pod included.

What am I missing?

I ran pod playgrounds ReactiveCocoa and after it opens I went to the playground file.

I've touched nothing and it says No such module 'ReactiveCocoa'

$ pod playgrounds Alamofire,Fuzi

when opening and running i get the following warnings / errors:

ld: warning: directory not found for option '-F/Users/luis/Library/Developer/Xcode/DerivedData/Alamofire-gkuowffwjdhhqfcudpkzfivwlpwi/Build/Products/Debug-iphonesimulator/Alamofire'
ld: warning: directory not found for option '-F/Users/luis/Library/Developer/Xcode/DerivedData/Alamofire-gkuowffwjdhhqfcudpkzfivwlpwi/Build/Products/Debug-iphonesimulator/Fuzi'

On /Users/luis/Library/Developer/Xcode/DerivedData/Alamofire-gkuowffwjdhhqfcudpkzfivwlpwi/Build/Products/Debug-iphonesimulator/ there are the following after building:

Alamofire.framework
AlamofirePlayground.framework
Fuzi.framework
Pods_AlamofirePlayground.framework

The content of the playground is:

//: Please build the scheme 'AlamofirePlayground' first
import XCPlayground
XCPlaygroundPage.currentPage.needsIndefiniteExecution = true

import Alamofire
import Fuzi

print(AlamofireVersionNumber)

Where if it worked fine, we would see in the output: "1.1\n"

Of notice, if one just imports one framework, it works fine.

Hey!

This library is absolutely fantastic. I've been trying to use ReactiveCocoa on a playground since playgrounds came out, and today was the first time I finally managed to do it :)

Question: is there a syntax that will create this pointing to a Pod in the local system? Thanks!

pod playground 'RxSwift, RxCocoa' Does generate a Playground RxSwift but it says no module RxSwift and convert to Swift 3 and once we cover it to Swift 3 it is not working

Xcode 8.2, Sierra, Swift 3. Please Fix ASAP.

Is swift 3.0 and above supported? Thanks.

Trying to create a playground for TwitterKit and I get

pod playgrounds TwitterKit
Abort trap: 6

I've updated to the latest version of Cocoapods?

I am trying to create playground with Alamofire. I am doing everything according to the instructions (including building the scheme), but the framework can't seem to be imported in the playground:

My Xcode version is 7.2.1 (7C1002), CocoaPods version is 1.0.0.beta.3 (tried 0.39.0 as well).

Am I missing something?

I ran pod playgrounds Alamofire and I have the same problem as here: #52

It doesn't work with others pods eg: Moya, RxSwift.

I know it was fixed 2 days ago but maybe not for version 9.4?

Anyone else have this problem?

Error

Errno::ENOENT - No such file or directory @ dir_initialize - /Applications/Xcode.app/Contents/Developer/Library/Xcode/Templates/File Templates/Source/Playground with Platform Choice.xctemplate
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/generate.rb:43:in `open'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/generate.rb:43:in `foreach'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/generate.rb:43:in `dir_for_platform'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/generate.rb:10:in `initialize'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:26:in `new'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:26:in `block in generate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:23:in `chdir'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/workspace.rb:23:in `generate'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-playgrounds-1.2.2/lib/cocoapods-playgrounds/command/playgrounds.rb:46:in `run'
/Library/Ruby/Gems/2.3.0/gems/claide-1.0.2/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.3.0/gems/cocoapods-1.5.3/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:22:in `load'
/usr/local/bin/pod:22:in `<main>'

Stack

   CocoaPods : 1.5.3
        Ruby : ruby 2.3.7p456 (2018-03-28 revision 63024) [universal.x86_64-darwin17]
    RubyGems : 2.5.2.3
        Host : Mac OS X 10.13.6 (17G65)
       Xcode : 9.4 (9F1027a)
         Git : git version 2.16.2
Ruby lib dir : /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib
Repositories : master - https://github.com/CocoaPods/Specs.git @ b8a53d010801cce2087b0563d0e39c14058aeedb

Installation Source

Executable Path: /usr/local/bin/pod

Plugins

cocoapods-deintegrate : 1.0.2
cocoapods-playgrounds : 1.2.2
cocoapods-plugins     : 1.0.0
cocoapods-search      : 1.0.0
cocoapods-stats       : 1.0.0
cocoapods-trunk       : 1.3.0
cocoapods-try         : 1.1.0

Podfile

platform :ios, '9.0'
use_frameworks!

target 'transport-parents' do

  # Pods for XX
  pod 'Fabric'
  pod 'Crashlytics'
  pod 'Alamofire'
  pod 'Moya'
  pod 'SnapKit'
  pod 'PromisesSwift'
  pod 'PromiseKit'
  pod 'PromiseKit/Alamofire'
  pod 'RxSwift'
  pod 'RxCocoa'

  target 'XXTests' do
    inherit! :search_paths
  end

  target 'XXUITests' do
    inherit! :search_paths
  end

end

When running pod playgrounds all the files are created but they claim the .xcworkspace does not exist, even though it does. When opening the playground the error no such module is shown. I am using version 1.2.2 and Cocoapods-1.1.0.rc.2.

pod playgrounds AsyncDisplayKit --name ASLayout-AsyncDisplayKit == awesome. 🙇

I'm trying to use this gem with CocoaPods version 1.0.0.beta6 and it doesn't work.
The pod command just doesn't find playgrounds sub-command.

At the same time it works with 0.39.0.

Is it possible to use playgrounds with pre-release CocoaPods?

As the title says, if you try to import one of Podspecs that you want to Play With™, the import fails

Could this be because the Sources are compiled as a different Module and the xcconfig doesn't take this into account when linking the frameworks to the modules where they are required?

Any way I help you with this?

PS: Thanks for this plugin, loving it!

This playgrounds sub-command is lacking support for private pods. If my pod depends on another private pod, the pod install --no-repo-update will fail to fetch private pods.

I have to specify all of the privates pods directly then:

pod playgrounds MyPod.podspec,/path/to/dependency-a.podspec,/path/to/dependency-b.podspec

It would be great to have support for --sources option for playgrounds too.

• I keep having an error when I want to run the command gem install cocoapods-playgrounds. Here is the error that I get : ERROR: While executing gem ... (Gem::FilePermissionError)
  You don't have write permissions for the /Library/Ruby/Gems/2.0.0 directory.`
• I also tried to run sudo gem install cocoapods-playgrounds and here is the error that I get:
  ERROR: While executing gem ... (Errno::EPERM) Operation not permitted - /usr/bin/carthage-play

This is not a issue but an unsupported feature.

"pod playgrounds Alamofire" command created a workspace.
"import Alamofire" can be used in main playground file or playground pages. But if I add any swift file in source folder, I can't use any import statements for installed pods.

I am not sure if this is even supported by Apple.