Add back compat config for NSD
Add back compat config for RUN_NATIVE_NSD_ONLY_IF_LEGACY_APPS, which was lost when moving NsdManager to framework-connectivity-t. This causes NsdManager to start mdnsresponder again when used by apps with target SDK < 31. The change also changes the compat ID used, to make sure it does not conflict with the ID already in use in S and below, when the module is installed on such a platform. This is the only ChangeId used by framework-t. Also add a CtsNetTestCasesMaxTargetSdk30 test to verify that behavior. Bug: 235355681 Test: atest CtsNetTestCasesMaxTargetSdk30 Change-Id: I7ca6051d0a4ba5aff3e44bece2cbac22eb1be32d
Showing
- TEST_MAPPING 22 additions, 0 deletionsTEST_MAPPING
- Tethering/apex/Android.bp 4 additions, 1 deletionTethering/apex/Android.bp
- framework-t/Android.bp 5 additions, 0 deletionsframework-t/Android.bp
- framework-t/src/android/net/nsd/NsdManager.java 10 additions, 6 deletionsframework-t/src/android/net/nsd/NsdManager.java
- tests/cts/net/Android.bp 15 additions, 0 deletionstests/cts/net/Android.bp
- tests/cts/net/src/android/net/cts/NsdManagerTest.kt 36 additions, 0 deletionstests/cts/net/src/android/net/cts/NsdManagerTest.kt
- tests/unit/java/android/net/nsd/NsdManagerTest.java 10 additions, 10 deletionstests/unit/java/android/net/nsd/NsdManagerTest.java
- tests/unit/java/com/android/server/NsdServiceTest.java 4 additions, 4 deletionstests/unit/java/com/android/server/NsdServiceTest.java
Loading
Please register or sign in to comment