Problem building dependencies of the example app.

[kzaher]

For some reason running Examples/dependencies.sh or git submodule update --init --recursive --force before building the Example target inside of theExamples/Examples.xcodeproj in a fresh cloned repo succeeds

... but trying to build Example target before running the Examples/dependencies.sh or git submodule update --init --recursive --force causes build failure.

I have no idea what's happening here.

[freak4pc]

It actually works fine for me. I just cloned a fresh one, built the project, get the osascript alert and the project worked.

[kzaher]

@freak4pc Did you clone it under the same name under which it was cloned before? If so, try cloning it to a new unique path.

[freak4pc]

It was unique, I didn’t have it cloned.

[kzaher]

I can repro it pretty consistently on my computer.

Xcode Version 10.1 (10B61)

• clone the repo under new path.
• Select Example target
• Build > Warning appears > Xcode closes
• Build again > Can't find Rx*

It happens to me on both of my computers, like 90% of times.

[marioradonic]

Hi @kzaher I stumbled upon same problem. If you delete derived data you can repro this always without having to change the name. Likewise, if you delete derived data after the dependencies script closes the Xcode it fixes the problem. Using the legacy build system also fixes the problem, so I guess it's a bug in a new build system probably caused by abruptly killing Xcode.

If you want I can help by deleting derived data in the script, but I think ultimately better solution would be to use another way to link Rx*

[kzaher]

@marioradonic I'm not sure is killing Xcode the real culprit here. I've tried removing the kill from ./dependencies but as far as I can tell it still failed on me.

On high level I think it would be nice to just be able to hit run in Xcode and for everything to magically work without any additional dependencies. Maintaining example apps for 3 package managers is too much for me.