You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
relies on Intent::toString rather than Intent::toInsecureString.
This makes debugging difficult if the reason for the Intent matching failure is a discrepancy in Intentdata. Ideally, ResolvedIntentImpl::toString would use Intent::toInsecureString rather than Intent::toString, but I don't know how feasible that is.
The text was updated successfully, but these errors were encountered:
When Espresso
Intent
-matching fails to find a matching intent, it prints an error message:android-test/espresso/intents/java/androidx/test/espresso/intent/VerificationModes.java
Lines 56 to 57 in f7d881a
that includes string representations of all expected
Intent
s and all recordedIntent
s.Currently, this error message obfuscates the
data
associated with eachIntent
, becauseResolvedIntentImpl::toString
:android-test/espresso/intents/java/androidx/test/espresso/intent/ResolvedIntentImpl.java
Line 57 in f7d881a
relies on
Intent::toString
rather thanIntent::toInsecureString
.This makes debugging difficult if the reason for the
Intent
matching failure is a discrepancy inIntent
data
. Ideally,ResolvedIntentImpl::toString
would useIntent::toInsecureString
rather thanIntent::toString
, but I don't know how feasible that is.The text was updated successfully, but these errors were encountered: