PassConstraints
ScreenshotEligibility
列舉 |
SCREENSHOT_ELIGIBILITY_UNSPECIFIED |
預設值,與 ELIGIBLE 相同。 |
ELIGIBLE |
如果未設定 ScreenshotEligibility,所有現有票證的預設行為。允許在 Android 裝置上擷取螢幕截圖。 |
INELIGIBLE |
禁止在 Android 裝置上擷取螢幕截圖。請注意,較舊版本的 Google 錢包仍可拍攝螢幕截圖。 |
NfcConstraint
列舉 |
NFC_CONSTRAINT_UNSPECIFIED |
預設值,未指定限制。 |
BLOCK_PAYMENT |
票證開啟時,系統不會顯示付款卡。 |
BLOCK_CLOSED_LOOP_TRANSIT |
系統不會在票證開啟時傳輸封閉式迴路的大眾運輸票證。 |
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2024-11-13 (世界標準時間)。
[null,null,["上次更新時間:2024-11-13 (世界標準時間)。"],[[["Pass constraints can be set to control screenshot eligibility and NFC behavior."],["`screenshotEligibility` determines if screenshots of the pass are allowed on Android devices, with options for eligible or ineligible."],["`nfcConstraint` allows restrictions on NFC interactions when the pass is open, such as blocking payments or closed-loop transit cards."],["The default behavior for screenshots is eligible, and there are no NFC constraints by default."]]],["Pass constraints are defined through `screenshotEligibility` and `nfcConstraint`. `screenshotEligibility` controls screenshot capture with `ELIGIBLE` (default) or `INELIGIBLE` options. `nfcConstraint` manages NFC interactions, allowing `BLOCK_PAYMENT` to prevent payment card conveyance and `BLOCK_CLOSED_LOOP_TRANSIT` to block closed-loop transit card conveyance. Unspecified settings use default behaviors: `SCREENSHOT_ELIGIBILITY_UNSPECIFIED` defaults to `ELIGIBLE` and `NFC_CONSTRAINT_UNSPECIFIED` implies no constraints.\n"]]