Adil Hussain

I just had a look into the implementation of the [UiDevice.getLauncherPackageName()](https://developer.android.com/reference/androidx/test/uiautomator/UiDevice#getlauncherpackagename) method and here's something which confuses me which I hope someone can clarify... The [UiDevice.getLauncherPackageName()](https://developer.android.com/reference/androidx/test/uiautomator/UiDevice#getlauncherpackagename) method queries for the...

Any update with this? I see version 2.0.0 is still not available on CocoaPods. I see some progress was made to update the Podspecs file for the 2.0.0 release a...

@jainhitesh3: I just tried upgrading from EarlGrey 1.15.1 to EarlGreyTest 2.0.0 but it looks like the [EarlGrey.swift](https://github.com/google/EarlGrey/blob/master/gem/lib/earlgrey/files/Swift-4.0/EarlGrey.swift) has a fair number of compilation errors which will need fixing. @tirodkar: Thanks...

This issue is fixed. See [this comment](https://github.com/google/EarlGrey/issues/971#issuecomment-722955348) in issue #971.

I followed the White-Boxing guides and created a helper bundle [here](https://github.com/adil-hussain-84/EarlGrey2-SwiftUI-Experiment/tree/master/HelperBundle). I am able to tunnel calls to `GREYHostApplicationDistantObject` and define my own custom matchers. However, I am unsure how...

Thank you @shaneong for sharing the extra steps that we need to follow to get white-boxing working with CocoaPods 👍 I had to alter the `post_install` script that you shared...

This is related to issue #1679. The existing matchers in EarlGrey work for UIKit views only and I can't figure out right now how to write custom actions and matchers...

I've created a pull request [here](https://github.com/vincent-pradeilles/locatable/pull/4) which fixes it. The fix is to rename the `value` property to `wrappedValue`.

Thanks for the response @renep. It looks like all I was missing was a `mavenCentral()` build script repository declaration. I had `jcenter()` and not `mavenCentral()`. Looks like the `org.pegdown:pegdown:1.6.+` artifact...

I created an issue in IssueTracker about this [here](https://issuetracker.google.com/issues/178965163) but sadly the Google engineer who picked it up marked it as "Won't fix (Intended behaviour)" 😔 In hindsight, now that...