From 5e353768577b6efd5eab9d08cecdf07ba7450f0f Mon Sep 17 00:00:00 2001 From: Michael Groover Date: Mon, 21 Sep 2020 15:27:52 -0700 Subject: Fix unique identifiers best practices links in device ID API docs Bug: 168447060 Test: m docs Change-Id: I483e0cf4915862254461200deb5d3dc7302bafb4 Merged-In: I483e0cf4915862254461200deb5d3dc7302bafb4 (cherry picked from commit 1aef206a3aadd0907204d3499882e1fd36790eeb) --- core/java/android/os/Build.java | 4 +- .../java/android/telephony/TelephonyManager.java | 44 +++++++++++----------- 2 files changed, 24 insertions(+), 24 deletions(-) diff --git a/core/java/android/os/Build.java b/core/java/android/os/Build.java index bde332792e18..018bb2c9f9b2 100755 --- a/core/java/android/os/Build.java +++ b/core/java/android/os/Build.java @@ -135,8 +135,8 @@ public class Build { * *

Starting with API level 29, persistent device identifiers are guarded behind additional * restrictions, and apps are recommended to use resettable identifiers (see Best practices for unique identifiers). This method can be invoked if one of - * the following requirements is met: + * href="/training/articles/user-data-ids">Best practices for unique identifiers). This + * method can be invoked if one of the following requirements is met: *