James Ide 6fac6db4d4 Use xcodebuild and delete "Framework Search Paths" for Xcode 7.3 to un-stall the tests ... Summary:The Obj-C tests were stalling when we updated TravisCI to use the OS X image with Xcode 7.3 and iOS 9.3. On my own MBP with Xcode 7.3 the tests stall as well. Running `./scripts/objc-test.sh` prints out a warning near the end, which says `ld` couldn't find a Frameworks folder under the iPhoneSimulator9.3 SDK directory. Indeed, this directory doesn't exist on my computer. When creating a brand new project with unit tests and UI tests, both test targets don't specify "Framework Search Paths" so I don't think we need to specify it anymore. Closes https://github.com/facebook/react-native/pull/7168 Differential Revision: D3216524 fb-gh-sync-id: 3097bda98d78289ecdba86801bcd461f3311ac47 fbshipit-source-id: 3097bda98d78289ecdba86801bcd461f3311ac47		2016-04-22 23:04:19 -07:00
..
android-e2e-test.js	E2e android	2016-04-13 08:20:05 -07:00
bump-oss-version.js	Version release script	2016-03-24 08:41:24 -07:00
circle-ci-android-setup.sh	Fixed CI stability: running android tests via emulator not graddle:co…	2016-03-11 13:33:26 -08:00
objc-test.sh	Use xcodebuild and delete "Framework Search Paths" for Xcode 7.3 to un-stall the tests	2016-04-22 23:04:19 -07:00
publish-npm.js	Version release script	2016-03-24 08:41:24 -07:00
run-android-instrumentation-tests.sh	instrumentation tests are executed with BUCK	2016-03-02 06:55:35 -08:00
run-ci-e2e-tests.js	Use xcodebuild and delete "Framework Search Paths" for Xcode 7.3 to un-stall the tests	2016-04-22 23:04:19 -07:00
test-manual-e2e.sh	Simplify manual testing steps when doing the release	2016-04-18 11:32:28 -07:00