Skip to content

Commit b29b266

Browse files
Add retrieve fingerprints page and consolidate
1 parent 562d96d commit b29b266

File tree

3 files changed

+22
-9
lines changed

3 files changed

+22
-9
lines changed

.prettierignore

-1
This file was deleted.

src/content/docs/en/sdk/android/v4/integrations/retrieve-certificate-fingerprints.mdx

+11-4
Original file line numberDiff line numberDiff line change
@@ -107,10 +107,10 @@ If you use Huawei App Signing, follow the below instructions. If you don't use H
107107
#### From a keystore {#from-a-keystore}
108108

109109
<Callout type="note">
110-
- The below steps require Java to be installed. - If you sign your app with
111-
the Android default debug keystore, you don’t need to configure the
112-
certificate fingerprint in the Adjust dashboard for SDK Signature. However,
113-
you do need to configure it for Android App Links.
110+
- The below steps require Java to be installed.
111+
- If your build has the Adjust SDK set to the sandbox environment, then SDK Signature
112+
will always pass, so it's not necessary to retrieve the certificate fingerprint for that
113+
build. However, setting up Android App Links requires certificate fingerprints for all builds.
114114
</Callout>
115115

116116
To retrieve certificate fingerprints from your keystore, follow these steps:
@@ -146,6 +146,13 @@ To retrieve certificate fingerprints from your keystore, follow these steps:
146146

147147
#### From an APK {#from-an-apk}
148148

149+
<Callout type="note">
150+
If your build has the Adjust SDK set to the sandbox environment, then SDK
151+
Signature will always pass, so it's not necessary to retrieve the certificate
152+
fingerprint for that build. However, setting up Android App Links requires
153+
certificate fingerprints for all builds.
154+
</Callout>
155+
149156
To retrieve certificate fingerprints used to sign your APK, follow these steps:
150157

151158
1. If needed, install [Android Studio](https://developer.android.com/studio) to get the [apksigner](https://developer.android.com/tools/apksigner) command.

src/content/docs/en/sdk/android/v5/integrations/retrieve-certificate-fingerprints.mdx

+11-4
Original file line numberDiff line numberDiff line change
@@ -107,10 +107,10 @@ If you use Huawei App Signing, follow the below instructions. If you don't use H
107107
#### From a keystore {#from-a-keystore}
108108

109109
<Callout type="note">
110-
- The below steps require Java to be installed. - If you sign your app with
111-
the Android default debug keystore, you don’t need to configure the
112-
certificate fingerprint in the Adjust dashboard for SDK Signature. However,
113-
you do need to configure it for Android App Links.
110+
- The below steps require Java to be installed.
111+
- If your build has the Adjust SDK set to the sandbox environment, then SDK Signature
112+
will always pass, so it's not necessary to retrieve the certificate fingerprint for that
113+
build. However, setting up Android App Links requires certificate fingerprints for all builds.
114114
</Callout>
115115

116116
To retrieve certificate fingerprints from your keystore, follow these steps:
@@ -146,6 +146,13 @@ To retrieve certificate fingerprints from your keystore, follow these steps:
146146

147147
#### From an APK {#from-an-apk}
148148

149+
<Callout type="note">
150+
If your build has the Adjust SDK set to the sandbox environment, then SDK
151+
Signature will always pass, so it's not necessary to retrieve the certificate
152+
fingerprint for that build. However, setting up Android App Links requires
153+
certificate fingerprints for all builds.
154+
</Callout>
155+
149156
To retrieve certificate fingerprints used to sign your APK, follow these steps:
150157

151158
1. If needed, install [Android Studio](https://developer.android.com/studio) to get the [apksigner](https://developer.android.com/tools/apksigner) command.

0 commit comments

Comments
 (0)