How would you go about creating a pod with dependencies? Currently there is no use of CocoaPods in either the module project or the example app project.

This template is great, it should be the default of pod lib create as soon as possible. The current template provided by CocoaPods is very confusing.

I've changed the project generated by the swift3-module-template a bit so that it is easier to create a pod that has dependencies on other pods (see issue https://github.com/fulldecent/swift3-module-template/issues/8). The podfile in the root of my project looks like this:

platform :ios, '9.0'
inhibit_all_warnings!
use_frameworks!

workspace 'Abc'

target 'iOS Example' do
  project 'iOS Example'

  pod 'Abc', path: '.'
end

target 'Abc' do
  project 'Abc'

  pod 'Dependency1'
  pod 'Dependency2'

  target 'AbcTests'
end

It will create one workspace that contains three projects:

• Pods
• iOS Example
• Abc

The pod spec looks like this:

Pod::Spec.new do |s|
  s.name = 'Abc'
  s.version = '0.1.0'
  s.license = { :type => 'MIT', :file => 'LICENSE' }
  s.summary = 'The greatest pod ever made'
  s.description = <<-DESC
      Let me tell you about the greatest pod ever made.
    DESC
  s.homepage = 'https://about.abc'
  s.authors = { 'Abc' => '[email protected]' }
  s.source = { :git => 'https://github.com/abc/abc.git', :tag => s.version }

  s.ios.deployment_target = '8.0'
  s.source_files = 'Abc/Source/**/*.swift'

  s.dependency 'Dependency1', '~> 1.2.0'
  s.dependency 'Dependency2', '~> 2.3.0'
end

When you add or remove files from your pod, just run pod update and the updated pod will be used.

My folder looks like this:

.git
.gitignore
.swift-version
.swiftlint.yml
.travis.yml
CHANGELOG.md
CONTRIBUTING.md
LICENSE
Package.swift
Podfile
Podfile.lock
Pods
README.md
Abc.podspec
Abc.xcodeproj
Abc.xcworkspace
Abc
  - Source
  - Resources
AbcTests
  - Resources
AbcTestsHost
iOS Example
  - Source
  - Resources
iOS Example.xcodeproj

What do you guys think?

Hey,

Thanks a lot for merging my pull request https://github.com/fulldecent/swift3-module-template/pull/35

I have a question after merging - should I add one ObjC class to the template, so it would be obvious for users how to add objc files and have interoperability with swift code? What do you think?

P.S. I think that this template can be universal for both languages. Ofc example and tests will still be in Swift, which is not a problem for me.

Upgrade Package.swift so it can take advantage of the latest features.

• Use swift-tools-version:5+ instead of swift-tools-version:4.2
• Add "platform" parameter to the package declaration
• Add "swiftLanguageVersions" parameter to the package declaration

Documentation references: https://developer.apple.com/documentation/swift_packages/package https://developer.apple.com/documentation/swift_packages/platform https://developer.apple.com/documentation/swift_packages/package/3197887-swiftlanguageversions https://developer.apple.com/documentation/swift_packages/swiftversion

When I created a project using "./configure", then opened Xcode and hit "Cmd+U" (to run the tests). Xcode can't find Info.plistor the tests, because in a base project it is located in Tests folder, but in project.pbxproj it was "__PROJECT_NAME__Tests/Info.plist". Removing "PROJECT_NAME" in plist path fixed the problem.

P.S. Thanks a lot for this template - very useful.

At Step: VI. Make your iOS Example application depend on your module

I am unable to drag and drop 'xxProjectxNamexx' into Opened 'iOS Example' as a separate package. When I do so it appears with int the iOS Example Project and not as a separate package

I am trying to create a UIKit Version of the template.

Rename this project to swift4-module template. The new Xcode just hit Gold Master so it is GO time.

Alternatives considered:

• Make a new project -- this is stupid because nobody wants to make new swift3 projects once Xcode 9 is out. AND because this project is only about making NEW projects.

Work plan:

• [x] Rename the project
• [x] Update the REMOTES on my computer
• [x] Ask people linking to the old project to now link to the new one
• [x] s/oldurl/newurl/g in the GitHub

Old links, care of AHREFS:

• Reach out to them to offer updated link to this project.

• [x] http://cocoadocs.org/docsets/FDWaveformView/2.2.1/
• [x] http://cocoadocs.org/docsets/FDWaveformView/2.2.1/index.html
• [x] http://cocoadocs.org/docsets/SwiftVer/1.0.1/
• [x] http://cocoadocs.org/docsets/ZHTableViewGroupSwift/0.2.0/
• [x] http://cocoadocs.org/docsets/ZHTableViewGroupSwift/0.2.0/index.html
• [x] http://cocoapods.org/pods/FDWaveformView
• [x] http://cocoapods.org/pods/ZHTableViewGroupSwift
• [x] http://getawesomeness.herokuapp.com/get/swift
• [x] http://hnpaper.forge.partlab.io/u/fulldecent
• [x] http://uiview.com/project/93/
• [x] http://www.alexruperez.com/entries/2014-matteocrippa-awesome-swift
• [x] http://www.alexruperez.com/repos/71-awesome-swift
• [x] https://cocoapods.org/pods/FDWaveformView
• [x] https://cocoapods.org/pods/ZHTableViewGroupSwift
• [x] https://devhub.io/repos/SwiftCarlos-awesome-swift
• [x] https://devhub.io/repos/candostdagdeviren-awesome-swift
• [x] https://devhub.io/repos/fulldecent-swift3-module-template
• [x] https://devhub.io/repos/jonkykong-awesome-swift
• [x] https://devhub.io/repos/malcommac-awesome-swift
• [x] https://devhub.io/repos/matteocrippa-awesome-swift
• [x] https://devhub.io/repos/omaralbeik-awesome-swift
• [x] https://devhub.io/repos/rchatham-awesome-swift
• [x] https://devhub.io/repos/ytakzk-awesome-swift
• [x] https://devhub.io/zh/repos/SwiftCarlos-awesome-swift
• [x] https://devhub.io/zh/repos/candostdagdeviren-awesome-swift
• [x] https://devhub.io/zh/repos/jonkykong-awesome-swift
• [x] https://devhub.io/zh/repos/malcommac-awesome-swift
• [x] https://devhub.io/zh/repos/matteocrippa-awesome-swift
• [x] https://devhub.io/zh/repos/omaralbeik-awesome-swift
• [x] https://devhub.io/zh/repos/rchatham-awesome-swift
• [x] https://devhub.io/zh/repos/ytakzk-awesome-swift
• [x] https://getawesomeness.herokuapp.com/get/swift
• [x] https://github.oldjpg.com/repository/47279041
• [x] https://libraries.io/github/fulldecent/swift3-module-template
• [x] https://libraries.io/github/pavangandhi/SwiftNew
• [x] https://news.ycombinator.com/item?id=12515713
• [x] https://porter.io/daily/2016-09-16/
• [x] https://porter.io/github.com/fulldecent/swift3-module-template
• [x] https://porter.io/github.com/matteocrippa/awesome-swift
• [x] https://project-awesome.org/matteocrippa/awesome-swift
• [x] https://recordnotfound.com/awesome-swift-marmelroy-89681
• [x] https://recordnotfound.com/awesome-swift-matteocrippa-1387
• [x] https://recordnotfound.com/swift3-module-template-fulldecent-137320
• [x] https://swift.zeef.com/robin.eggenkamp

I've found an interesting crash, and I'm not sure what would be an ideal solution to fix it.

So steps to reproduce:

1. Generate a project from template
2. Add function to YourProjectName.swift func crushFunc() { print("Let's crash!") }
3. Compile the project for target "iOS Example" or "YouProjectNameTests", you don't even need to call a function, it will crash on launch

To fix this, I had to turn on build setting "Always Embed Swift Standard Libraries" -> YES for both targets (Example and Tests), otherwise it will crash on launch. But this fix will generate warnings if user wants to add Pod Dependencies to the project (Debug + Release for Example and Test targets - 4 combined warning when installing cocoapods):

[!] The iOS Example [Debug] target overrides the ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES build setting defined in ../Pods/Target Support Files/Pods-iOS Example/Pods-iOS Example.debug.xcconfig'. This can lead to problems with the CocoaPods installation - Use the$(inherited)` flag, or - Remove the build settings from the target.

Just like in PR #30, this PR tries to leverage the (macOS flavor of) find and sed to automate the execution of steps 5.1.1 and 5.1.2. in the recipe, ultimately merging both into a single step of 5.1.

Hopefully, this saves template maintainers a bit of time when executing those recipe steps, and seems less tedious to me than the manual process. It also loses the dependency on the text editor.

This PR removes all occurrences of the development team ID from project.pbxproj files, which would lead to unsightly warnings if Xcode does not know that particular team ID.

The PR also updates the recipe to reflect this change. Since the recipe already assumes we’re on macOS, we can use (the macOS flavors of) find and sed to find and replace such IDs via Terminal.app. I feel this is more convenient than manual search-and-replace; besides, no text editor is needed while executing that step.

1. The WORKSPACE variable currently is set to WORKSPACE="__PROJECT_NAME__.xcworkspace"

2. Similarly, IOS_FRAMEWORK_SCHEME="__PROJECT_NAME__"

3. I had to set my DESTINATION="platform=iOS Simulator,OS=10.2,id=E40727B3-41FB-4D6E-B4CB-BFA87109EB12" for the destination to not be invalid and cause failure.

4. The last line being CheckCocoaPodsQualityIndexes.rb ProjectName fails to find the file. I currently am trying ruby Tests/CheckCocoaPodsQualityIndexes.rb. But travis is running slow for some reason at the moment.

5. The test target is looking for the info.plist file at ProjectNameTests/info.plist while it's actually at Tests/info.plist. This has to be changed in the test target's build settings.

The ./configure script works great, but I had to change the author name from the usual "Nicolás Miari" to "Nicolas Miari" (no diactritics) to get it to work, otherwise it would fail with:

Traceback (most recent call last):
	8: from ./configure:107:in `<main>'
	7: from ./configure:13:in `replace_variables_in_files'
	6: from ./configure:13:in `glob'
	5: from ./configure:17:in `block in replace_variables_in_files'
	4: from ./configure:17:in `open'
	3: from ./configure:19:in `block (2 levels) in replace_variables_in_files'
	2: from ./configure:19:in `each'
	1: from ./configure:20:in `block (3 levels) in replace_variables_in_files'
./configure:20:in `gsub!': incompatible character encodings: ASCII-8BIT and UTF-8 (Encoding::CompatibilityError)

I guess I can go back to the generate files and fix it, but it would be nice to have.

The images in the recipe folder show an example of using Xcode.

The pictures illustrate an old version of Xcode.

Update the pictures to show the same thing but using the current version of Xcode (with default themes, font sizes, etc.)

I would like to promote GitHub Actions as the new, better-maintained alternative to Travis CI.

GitHub Actions appears to be the new best practice.

Work plan:

• [ ] Remove .travis.yml in the project folder
• [ ] Add corresponding GitHub Actions CI to the project folder
  • [ ] Please study https://github.com/Alamofire/Alamofire/blob/master/.github/workflows/ci.yml
  • [ ] Please also include our extra feature (quality checks)
• [ ] Update the recipe so that the correct GitHub Actions CI is now included (see the curl commands)
• [ ] Test that it works:
  • [ ] Complete the recipe, ensure that the generated product folder matches the files already in your pull request
    • [ ] Attach screenshot of empty diff -r
  • [ ] Deploy the generated product folder as a new repository on GitHub and ensure that the GitHub Action was successfully triggered
    • [ ] Attach link to the GitHub Action CI task that was triggered