mwfarb
commented
9 years ago We still need to handle SecurityException, the manifest still reports that the manifest holds the permission, even though a custom build of android may throw an exception based on user preferences.
Cyanogen users are getting warnings that SafeSlinger wants access to Contacts when not in use and they have not explicitly allowed this access. Need to investigate if there is a way to avoid tripping this warning, but I'm not sure if it's from real-time access in one of our background processes or from the actual manifest permission.
Does the Cyanogen build of Android warn users that the manifest allows access or that the app is using that access in real-time? If the latter, we can avoid a background warning by pushing and Contacts sync to when the app is in the foreground only.