No. The fake provider is a separate provider limited to the test authority (FakeASAA), and the values you inject are reflected only in that call's response. The real store's age signal decision (com.sec.android.app.samsungapps.provider.ASAA) is computed solely from the store's internal state and does not reflect caller-supplied values.

The fake provider builds each response based on the extras of that specific call(). For predictable tests, we recommend passing the desired values using extras on every call.

The provider's default status (VERIFIED) is applied. We recommend specifying the status explicitly.

The fake provider's response value is identical to the real provider's response value, so you cannot distinguish by value alone. Check the [FAKE] marker log under the FakeAccountabliltyActProvider TAG in logcat. In addition, your app already knows which authority (FakeASAA vs. ASAA) it called, so that alone distinguishes them. See Identifying Fake Responses (Logging) for details.