joy/android_packages_modules_Connectivity
Watch
1
Fork
You've already forked android_packages_modules_Connectivity
 0
Code Issues Pull requests Projects Releases Wiki Activity
android_packages_modules_Co.../framework/api/lint-baseline.txt

19 lines
1.3 KiB
Text
Raw Normal View History

Split out the connectivity API surface Split out connectivity APIs to connectivity module directories. This prepares future move of the connectivity code into a mainline module, but still keeps it implemented by framework-minus-apex for now: the API stubs are moved to framework-connectivity.stubs, but the implementation on device remains in the same place. This allows moving the connectivity code in/out of APEX with minimal changes. BYPASS_INCLUSIVE_LANGUAGE_REASON=Moving files, can't modify released API Bug: 171540887 Test: device boots, connectivity working Merged-In: I21c42f032efa6c10e36c749df3183ce9679303a7 (cherry-pick from internal branch with API files conflicts) Change-Id: I21c42f032efa6c10e36c749df3183ce9679303a7
2021-01-28 13:37:03 +09:00
// Baseline format: 1.0
Baseline issues that were previously suppressed java_sdk_library has previously internally disabled a few legitimate issues. As this is being un-done for modules, add baselines for the pre-existing issues. Bug: 306806877 Test: m checkapi Merged-In: Ie764d33196675e1482f30ecfd3d6d22b7fa25c27 Change-Id: Ie764d33196675e1482f30ecfd3d6d22b7fa25c27
2023-10-25 15:39:26 +00:00
BroadcastBehavior: android.net.ConnectivityManager#ACTION_BACKGROUND_DATA_SETTING_CHANGED:
Field 'ACTION_BACKGROUND_DATA_SETTING_CHANGED' is missing @BroadcastBehavior
RequiresPermission: android.net.ConnectivityManager#requestNetwork(android.net.NetworkRequest, android.app.PendingIntent):
Method 'requestNetwork' documentation mentions permissions without declaring @RequiresPermission
RequiresPermission: android.net.ConnectivityManager#requestNetwork(android.net.NetworkRequest, android.net.ConnectivityManager.NetworkCallback):
Method 'requestNetwork' documentation mentions permissions without declaring @RequiresPermission
RequiresPermission: android.net.NetworkCapabilities#getOwnerUid():
Method 'getOwnerUid' documentation mentions permissions without declaring @RequiresPermission
RequiresPermission: android.net.http.BidirectionalStream.Builder#setTrafficStatsUid(int):
Method 'setTrafficStatsUid' documentation mentions permissions without declaring @RequiresPermission
RequiresPermission: android.net.http.UrlRequest.Builder#setTrafficStatsUid(int):
Method 'setTrafficStatsUid' documentation mentions permissions without declaring @RequiresPermission
Split out the connectivity API surface Split out connectivity APIs to connectivity module directories. This prepares future move of the connectivity code into a mainline module, but still keeps it implemented by framework-minus-apex for now: the API stubs are moved to framework-connectivity.stubs, but the implementation on device remains in the same place. This allows moving the connectivity code in/out of APEX with minimal changes. BYPASS_INCLUSIVE_LANGUAGE_REASON=Moving files, can't modify released API Bug: 171540887 Test: device boots, connectivity working Merged-In: I21c42f032efa6c10e36c749df3183ce9679303a7 (cherry-pick from internal branch with API files conflicts) Change-Id: I21c42f032efa6c10e36c749df3183ce9679303a7
2021-01-28 13:37:03 +09:00
VisiblySynchronized: android.net.NetworkInfo#toString():
Internal locks must not be exposed (synchronizing on this or class is still
Reference in a new issue Copy permalink