MultipleDevicesAndHoldersAllowedStatus
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
阐明了发卡机构的偏好设置,以确定 Google 钱包是否应允许在多名用户和多台设备之间共享和保存同一卡券对象。
枚举 |
STATUS_UNSPECIFIED |
未指定偏好设置。 |
MULTIPLE_HOLDERS |
卡券对象可由用户共享,并且可以由任意数量的不同用户和任意数量的设备保存。合作伙伴通常会将此设置用于不需要仅限单个用户或固定到单一设备的卡券。 |
ONE_USER_ALL_DEVICES |
一个对象只能由一位用户保存,但此用户可以在自己的多台设备上查看和使用该对象。第一个用户保存对象后,其他用户将无法再查看或保存该对象。 |
ONE_USER_ONE_DEVICE |
一个对象只能由一位用户在一台设备上保存。仅供特定合作伙伴在有限情况下使用。例如,公交车票应该“固定到设备”,这意味着它只能由用户在一台设备上保存、查看和使用。如需了解详情,请与支持团队联系。 |
multipleHolders |
MULTIPLE_HOLDERS 的旧别名,已弃用。
|
oneUserAllDevices |
ONE_USER_ALL_DEVICES 的旧别名,已弃用。
|
oneUserOneDevice |
ONE_USER_ONE_DEVICE 的旧别名,已弃用。
|
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis document outlines the issuer's preference for whether a Wallet pass object can be shared and saved across multiple users and devices.\u003c/p\u003e\n"],["\u003cp\u003eThree main sharing options are available: \u003ccode\u003eMULTIPLE_HOLDERS\u003c/code\u003e (shareable by any user on any device), \u003ccode\u003eONE_USER_ALL_DEVICES\u003c/code\u003e (one user, multiple devices), and \u003ccode\u003eONE_USER_ONE_DEVICE\u003c/code\u003e (one user, one device).\u003c/p\u003e\n"],["\u003cp\u003eLegacy aliases for these options (e.g., \u003ccode\u003emultipleHolders\u003c/code\u003e) are deprecated and should not be used.\u003c/p\u003e\n"]]],["The core content details issuer preferences for pass object sharing. `MULTIPLE_HOLDERS` allows any number of users to save the pass on multiple devices. `ONE_USER_ALL_DEVICES` restricts the pass to one user, usable across their devices. `ONE_USER_ONE_DEVICE` limits the pass to a single user and device. `STATUS_UNSPECIFIED` means the preference isn't defined. Legacy aliases for these options, multipleHolders, oneUserAllDevices, and oneUserOneDevice, are deprecated.\n"],null,["# MultipleDevicesAndHoldersAllowedStatus\n\nClarifies the issuer preference for whether Wallet should allow the same pass object to be shared and saved among more than one user and more than one device.\n\n| Enums ||\n|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `STATUS_UNSPECIFIED` | Unspecified preference. |\n| `MULTIPLE_HOLDERS` | The Pass object is shareable by a user and can be saved by any number of different users, and on any number of devices. Partners typically use this setup for passes that do not need to be restricted to a single user or pinned to a single device. |\n| `ONE_USER_ALL_DEVICES` | An object can only be saved by one user, but this user can view and use it on multiple of their devices. Once the first user saves the object, no other user will be allowed to view or save it. |\n| `ONE_USER_ONE_DEVICE` | An object can only be saved by one user on a single device. Intended for use by select partners in limited circumstances. An example use case is a transit ticket that should be \"device pinned\", meaning it can be saved, viewed and used only by a single user on a single device. Contact support for additional information. |\n| `multipleHolders` | Legacy alias for `MULTIPLE_HOLDERS`. Deprecated. | This item is deprecated! |\n| `oneUserAllDevices` | Legacy alias for `ONE_USER_ALL_DEVICES`. Deprecated. | This item is deprecated! |\n| `oneUserOneDevice` | Legacy alias for `ONE_USER_ONE_DEVICE`. Deprecated. | This item is deprecated! |"]]