-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fresh project, pod try 'RealmSwift'
fails; also pod install
fails.
#3985
Comments
If you're specifying a custom version of the # Uncomment this line to define a global platform for your project
# platform :ios, '9.0'
target 'SugarRecord_101_XCode7' do
# Comment this line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
# Pods for SugarRecord_101_XCode7
pod 'Realm', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', :submodules => true
pod 'RealmSwift', git: 'https://github.com/realm/realm-cocoa.git', branch: 'master', :submodules => true
target 'SugarRecord_101_XCode7Tests' do
inherit! :search_paths
# Pods for testing
end
target 'SugarRecord_101_XCode7UITests' do
inherit! :search_paths
# Pods for testing
end
end |
@ashokds did my suggestion work for you? |
@jpsim, Just tried the mirrored settings based on podfile edit you did, i.e. use both pods as per your comment. It's not working yet. Same error:
|
@ashokds, what's the error? |
I have just stumbled upon this issue today. Can't install Realm with CocoaPods anymore:
|
I have tried to install it both from the |
Narrowed it down to a Github instability. |
Fighting with the same issue. Is there somekind of workaround? |
We've maintained support for Realm Swift across Xcode 8 betas since WWDC, making adjustments to continue compiling and passing tests for Swift 2.2, 2.3 and 3.0 as new betas came out. However, due to the amount of churn Swift 3 has seen in the last 3 months, we held off on thoroughly reviewing all our Swift 3 API changes and accommodating both Xcode 7.3.1 and Xcode 8 into our continuous integration, testing, docs and release packaging processes. With Xcode 8 GM last week, we decided to make a push to finalize our Swift 3 APIs along with the other integration points mentioned above. That work is now mostly complete and we're preparing a 1.1.0 release for tomorrow, at which point our Swift 3 APIs will be final, binaries will be made available for Swift 2.3 and 3.0 in our release zips, and docs will be updated to reflect the new APIs. Thanks for your patience. |
Just started seeing this same issue happen on my build machine. Was working just a couple days ago. Not sure what's wrong. |
It's also failing when linting another pod, that depends on Realm. Here's how dependency looks in podspec: https://github.com/DenHeadless/DTModelStorage/blob/master/DTModelStorage.podspec#L20 And here is Travis CI job, that's failing the lint: Output from linter: -> Installing Realm (1.1.0)
> Git download
> Git download
$ /Applications/Xcode.app/Contents/Developer/usr/bin/git clone https://github.com/realm/realm-cocoa.git /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/d20160917-1857-c2sx0x --template= --single-branch --depth 1 --branch v1.1.0
Cloning into '/var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/d20160917-1857-c2sx0x'...
Note: checking out '5fbb4ce86b0679c2ced0babd2f1cfaf33f5dd68f'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
$ /Applications/Xcode.app/Contents/Developer/usr/bin/git submodule update --init --recursive
> Running prepare command
$ /bin/bash -c set -e sh build.sh cocoapods-setup
sh: build.sh: No such file or directory
-> DTModelStorage (3.0.0-beta.1)
- ERROR | [iOS] [DTModelStorage/Realm] unknown: Encountered an unknown error (/bin/bash -c
set -e
sh build.sh cocoapods-setup
sh: build.sh: No such file or directory |
Workaround can be found here: #4112 |
Goals
To get a project started with Realm (or SugarRecord).
Expected Results
'pod install' results in successful generation of xcworkspace file.
Actual Results
Getting following error
(output of
pod install --verbose
)Steps to Reproduce
Start an empty project using XCode 8 beta 6
Code Sample
Version of Realm and Tooling
In the CONTRIBUTING guidelines, you will find a script,
which will help determining these versions.
Realm version: 1.0.2
Xcode version: XCode 8 beta 6
iOS/OSX version: El Capitan
Dependency manager + version: Cocoapods 1.0.1
The text was updated successfully, but these errors were encountered: