Home | History | Annotate | Download | only in safetynet

Lines Matching full:your

32   The service provides an API your app can use to analyze the device where it is installed. The API
33 uses software and hardware information on the device where your app is installed to create a
37 capabilities to run your app.
42 your app will function as expected on that device.
71 you use the APIs that it is your responsibility to provide any necessary notices or consents for the
81 instance of the Google Play services API client. For details about using the client in your app,
88 To connect to the API, in your activity's <a href=
106 <strong>Note:</strong> You can only call these methods after your app has established a connection to
118 A SafetyNet compatibility check allows your app to check if the device where it is running
125 Using the API to perform a check requires a few implementation steps in your app. Once you have
127 API client, your app can then perform the following steps to use the service:
155 executed outside of your app's main execution thread, to avoid pauses and unresponsiveness in
156 your app user interface. For more information about using separate execution threads, see
167 between your app and the service. When you request a compatibility check, you must provide a
168 single use token in the form of a number used once, or <em>nonce</em>, as part of your request. A
173 You can obtain a nonce by generating one within your app each time you make a compatibility check
174 request. As a more secure option, you can obtain a nonce from your own server, using a secure
180 check request, the response from the SafetyNet service includes your nonce, so you can verify it
193 ready to make a compatibility check request. Since the response to your request may not be
230 When your app communicates with SafetyNet, the service provides a response containing the result
270 You should take steps to make sure the response received by your app actually came from the
289 it matches your original request, including the nonce, timestamp, package name, and the SHA-256
290 hashes. You can perform these validation steps within your app, or as a more secure option, send
291 the entire JWS response to your own server for verification, via a secure connection.
326 <li>Obtain your API key by expanding <strong>APIs &amp; auth</strong> and
333 After enabling this API for your project, you can call the verification service from your app or
334 server. You need the contents of the JWS message from the SafetyNet API and your API key to call
353 https&#58;&#47;&#47;www.googleapis.com/androidcheck/v1/attestations/verify?key=&lt;your API key&gt;
369 payload data matches your original compatibility check request.