The Demo project does not work out of the box. about earlgrey HOT 11 CLOSED

It works just fine on Xcode 7.3.1 I recommend documenting this as a requirement. No directory renaming needed.

from earlgrey.

What version of OS X & Xcode are you using?

from earlgrey.

OSX 10.11.5
Xcode 7.3

from earlgrey.

Sorry that you're running into this Matt. @tirodkar: could you please help out Matt with this.

from earlgrey.

@mcmurrym I think you might be running into:
http://stackoverflow.com/questions/37212028/use-of-unresolved-identifier-grey-accessibilityid/37215155#37215155

from earlgrey.

I saw that, but just renaming the directory causes the BridgingHeader to fail on the import of EarlGrey/EarlGrey.h

from earlgrey.

This is the example project in the error state before changing the directory name
EarlGreyExample.zip

from earlgrey.

Try updating to the latest stable Xcode 7.3.1.

from earlgrey.

This seems to be related to a SourceKit issue with non allowing frameworks with hyphens or so in their names. An update might help in your case.

Try this -

Rename Pods/EarlGrey/EarlGrey-1.0.0 to Pods/EarlGrey/EarlGrey1 and re-add the EarlGrey.framework in your project in the Pods/Pods/EarlGrey/Frameworks directory which should now be red on changing the directory name. Remove the Framework Search Path to EarlGrey in the Swift Target's Build Settings.

from earlgrey.

On it. Thanks.

from earlgrey.

Closing as this fixed.

from earlgrey.