Disable "next" targets in module release branch
The "next" targets are not necessary in the module release branch.
This should not be (auto)merged in development branches.
Ignore-AOSP-First: module release branch-only change
Merged-In: Iaa8b203660518e30c74d37a4322b45380df14835
Test: m
Change-Id: If6b3352f2c3cb73dd713a503b1d3b696eb3beeb4
diff --git a/tests/cts/hostside/Android.bp b/tests/cts/hostside/Android.bp
index e55ba63..2d07224 100644
--- a/tests/cts/hostside/Android.bp
+++ b/tests/cts/hostside/Android.bp
@@ -12,7 +12,7 @@
// See the License for the specific language governing permissions and
// limitations under the License.
-next_app_data = [ ":CtsHostsideNetworkTestsAppNext" ]
+next_app_data = []
// The above line is put in place to prevent any future automerger merge conflict between aosp,
// downstream branches. The CtsHostsideNetworkTestsAppNext target will not exist in