Aditya Atul Tirodkar

To be clear, this feature would require us to have an abstraction layer on top of EarlGrey that supports the JSON protocol? So you would write tests that could be...

Can you provide any repro steps? On Sun, Feb 21, 2021 at 18:58 GreatSungKook wrote: > i got DYLD_FALLBACK_FRAMEWORK_PATH error > > — > You are receiving this because you...

It is available. Take a look at https://github.com/google/EarlGrey/blob/earlgrey2/docs/cocoapods-setup.md. We need to look more into white-box support using category bundles, but the rest works.

EarlGrey 2.0 is based on XCUITest which is a UI test - the app and test are two different processes. That's why we need an `App` and `Test` config.

Can you print the error please?

We don't have any specific tests for `UITabBar`. I can add one and check with EarlGrey 2.0.

``` "GREYAppStateTracker": "Waiting for viewDidAppear: call on the view controller. Please ensure that this view controller and its subclasses call through to their super's implementation. Full state transition call stack...

EG 1 isn't supported anymore for bugs in iOS 13. We're just working on a fix for build issues. Is the issue present in EG 2?

https://github.com/google/EarlGrey/blob/earlgrey2/docs/cocoapods-setup.md Tell me if something is missing. It uses XCUITest instead of XCTest.

Does this crash repro with the EarlGrey Functional Tests as well? As in - can you try opening `FunctionalTests.xcodeproj` and running some of the tests?