Install pods on a second machine.
On the first machine bundle exec pod update succeeded and updated the Podfile.lock accordingly. Doing a bundle exec pod install on a second machine with having the following in Podfile.lock
- Realm (3.19.0):
- Realm/Headers (= 3.19.0)
- Realm/Headers (3.19.0)
- RealmSwift (3.19.0):
- Realm (= 3.19.0)
is expected to just succeed without any errors.
bundle exec pod install --verbose
[...]
-> Installing Realm (3.19.0)
> Git download
> Git download
$ /usr/bin/git clone https://github.com/realm/realm-cocoa.git /var/folders/r7/0xvdqbpn5991qb0sz4dz7ssh0000gp/T/d20191004-29275-1ewmwr8 --template= --single-branch --depth 1 --branch v3.19.0
Cloning into '/var/folders/r7/0xvdqbpn5991qb0sz4dz7ssh0000gp/T/d20191004-29275-1ewmwr8'...
Note: checking out '69a4f4c73c877bf6df4cc416d1590a5e42426cc0'.
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>
$ /usr/bin/git -C /var/folders/r7/0xvdqbpn5991qb0sz4dz7ssh0000gp/T/d20191004-29275-1ewmwr8 submodule update --init --recursive
Submodule 'Realm/ObjectStore' (https://github.com/realm/realm-object-store.git) registered for path 'Realm/ObjectStore'
Cloning into '/private/var/folders/r7/0xvdqbpn5991qb0sz4dz7ssh0000gp/T/d20191004-29275-1ewmwr8/Realm/ObjectStore'...
Submodule path 'Realm/ObjectStore': checked out '25018d4e5428989adcaa5e78cf9beba8bb51b9a7'
Submodule 'external/catch' (https://github.com/catchorg/Catch2) registered for path 'Realm/ObjectStore/external/catch'
Cloning into '/private/var/folders/r7/0xvdqbpn5991qb0sz4dz7ssh0000gp/T/d20191004-29275-1ewmwr8/Realm/ObjectStore/external/catch'...
Submodule path 'Realm/ObjectStore/external/catch': checked out '6860c8def0ba7559bf077515b7a7ff63ad3444f8'
> Running prepare command
$ /bin/bash -c set -e sh build.sh cocoapods-setup
core is not a symlink. Deleting...
Downloading dependency: sync 4.7.8 from https://static.realm.io/downloads/sync/realm-sync-cocoa-4.7.8.tar.xz
mv: rename core to sync-4.7.8/core: Directory not empty
[!] /bin/bash -c
set -e
sh build.sh cocoapods-setup
core is not a symlink. Deleting...
Downloading dependency: sync 4.7.8 from https://static.realm.io/downloads/sync/realm-sync-cocoa-4.7.8.tar.xz
mv: rename core to sync-4.7.8/core: Directory not empty
The permissions inside of $TMPDIR for directories like the above are the following:
drwx------ 2 <the-user> staff 64 Oct 3 04:11 d20191003-96746-42crc8
These are the same permissions on both, the first machine and the second.
Realm framework version: 3.19.0
Realm Object Server version: 3.19.0
Xcode version: 11.0 (11A420a)
macOS version: Mojave Latest
Dependency manager + version: CocoaPods v1.8.1
Deleting $TMPDIR/sync_bin and Pods/Realm/core should fix this.
rm -rf $TMPDIR/sync_bin did the trick. Thanks
Hey - looks like you forgot to add a T-* label - could you please add one (if you have access to add labels)?
Most helpful comment
Deleting
$TMPDIR/sync_binandPods/Realm/coreshould fix this.