|
|
|
|
|
|
by veeti
4421 days ago
|
|
|
> This is about the easiest change for developers to accommodate. All they need to do is handle one exception. One exception, possibly in hundreds of different places in the code. What a ridiculous assumption to make: "just about the easiest change"? Seriously? Adding real permission revoking into Android at this point is a total no-go. The real solutions to this issue are App Ops (which transparently stubs out API's by returning blank data or simply ignoring calls) and optional permissions (for developers) in cases like temporary access to contacts. Both already exist in the AOSP codebase in one way or another. Only the settings UI for app ops is gone, and optional permissions are under work [1]. [1] https://android.googlesource.com/platform/frameworks/base/+/... |
|
|