Skip to content

Commit 2da4134

Browse files
DebbieAtSeamgitbook-bot
authored andcommitted
GITBOOK-580: Fix agreement
1 parent 6f031ef commit 2da4134

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/capability-guides/mobile-access/mobile-device-sdks/using-unlock-with-tap.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ description: >-
66

77
# Using Unlock With Tap
88

9-
Unlock With Tap in mobile apps functions similarly to using a traditional proximity card. The app launches an unlock scanning process. When the user holds their phone close to the lock that they want to open, the phone communicates wirelessly with the lock and transmits an access credential. Once the lock verifies these credentials and confirms access is granted, it unlocks.
9+
Unlock With Tap in mobile apps functions similarly to using a traditional proximity card. The app launches an unlock scanning process. When the user holds their phone close to the lock that they want to open, the phone communicates wirelessly with the lock and transmits an access credential. Once the lock verifies this credential and confirms that access is granted, it unlocks.
1010

1111
In your app, you use `seam.phone.native.unlockWithTap.launch` to initiate this unlock scanning process. Note that `unlockWithTap` automatically starts scanning whenever it is possible to scan and stops scanning whenever it is not possible to scan. That is, when an issue obstructs the phone from scanning, the `can_scan` capability changes to `false`, and Seam adds the resulting error to the error list. Further, the error explains to the user how to fix the causing issue.
1212

0 commit comments

Comments
 (0)