History log of /frameworks/base/core/tests/coretests/src/android/content/AbstractCrossUserContentResolverTest.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
1706bcddd5d5ad04db51ab03d16f9faafd8f5ef1 30-Nov-2017 Sudheer Shanka <sudheersai@google.com> Fix cross-user content resolver tests.

Wait for the user to get unlocked before trying to start an
encryption-unaware app in that user.

Fixes: 69927817
Test: adb shell am instrument -e class android.content.ManagedUserContentResolverTest -w
com.android.frameworks.coretests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I36f38d20c7f4584a68bc3b1b99941ce3e3b3815c
/frameworks/base/core/tests/coretests/src/android/content/AbstractCrossUserContentResolverTest.java
b4e2ddde4f08ba25f57c97a4fe7c339cbe805559 04-Feb-2017 Sudheer Shanka <sudheersai@google.com> Use context's userId in ContentResolver class.

- When registering and notifying observers, we should use the user in the
context as opposed to current user.
- Relax the permission check while registering and notifying content observers
to use INTERACT_ACROSS_USERS instead of INTERACT_ACROSS_USERS_FULL permission.

Change-Id: I973936903d4a2272c5722f3b98a057a40c0402be
Fixes: 32955100
Test: Created managed profile and verified that there are not failures.
runtest -x core/tests/coretests/src/android/content/SecondaryUserContentResolverTest.java
runtest -x core/tests/coretests/src/android/content/ManagedUserContentResolverTest.java
/frameworks/base/core/tests/coretests/src/android/content/AbstractCrossUserContentResolverTest.java