[sdk33] fix test-suite not showing some tests on iOS
Add ExponentTest.log method that we can filter with os_log + bail out early- ExponentTest.log is a method that uses os_log, which we can see in the simulator's log stream.- We bail out of the test
Add ExponentTest.log method that we can filter with os_log + bail out early- ExponentTest.log is a method that uses os_log, which we can see in the simulator's log stream.- We bail out of the tests early in CI on iOS since they freeze. Need to look into this more later.fbshipit-source-id: bf8d6b0
show more ...
Log test-suite failures using Apple's unified logging API so we can stream them from a Release IPAThe native implementation for `console.log` messages gets compiled out of Release IPAs (where `RCT_
Log test-suite failures using Apple's unified logging API so we can stream them from a Release IPAThe native implementation for `console.log` messages gets compiled out of Release IPAs (where `RCT_DEBUG` is not set), which means we don't get test-suite's final `console.log` with the results when running a standalone IPA made with `cd test-suite && exp build:ios --type simulator`, for example.This commit uses os_log (Apple's new logging API as of iOS 10), which gives us more control over making sure the test-suite result is always logged. It also lets us create a logger with a "subsystem" and "category" that we can use to filter the logs programmatically.Since os_log (and also Android adb for that matter) truncate logs past a certain point, test-suite JS now passes only failures to the native side.Tested by building the client with DEBUG off (ran it for profiling, easy way to do this) and forcing EXTest to be loaded. Ran test-suite and ensured the results (namely the failures) were visible when running `xcrun simctl spawn booted log stream --predicate '(subsystem == "host.exp.Exponent") && (category == "test")'` and running test-suite in the Expo client on the simulator.fbshipit-source-id: 558ef05
Split Core and Optional ExpoKit sourcesfbshipit-source-id: 65abb7c