GNSPublicationParams Class
Stay organized with collections
Save and categorize content based on your preferences.
Optional parameters for a publication.
See the property declarations below for explanations of each parameter.
Inherits NSObject.
The strategy to use for publishing the message. See GNSStrategy for the default.
| - (GNSOperationStatusHandler) statusHandler |
|
readwritenonatomiccopy |
A handler for publication status.
It can be used for tracking the status of a newly created publication.
| - (GNSPermissionRequestHandler) permissionRequestHandler |
|
readwritenonatomiccopy |
A handler for requesting user permission to use Nearby.
This handler overrides the default dialog used by Nearby; if you supply this handler, Nearby will not show its permission dialog.
In your request handler, you should request the user's permission to perform the task that requires the use of Nearby, explaining why it's being used. When the user has given or denied consent, you must call the block that's passed into your request handler. If you pass YES into the block, it means the user has consented to allow Nearby to function. If you pass NO, it means the user has not consented; your publications and subscriptions will not work until consent has been given.
The handler can also be used as a method of "preflighting" for the iOS permission dialogs. You can use it to explain why the user is expected to consent to the iOS permissions before your app can perform its Nearby related functions.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-12 UTC.
[null,null,["Last updated 2025-08-12 UTC."],[[["\u003cp\u003eGNSPublicationParams provides optional parameters for configuring message publications in Nearby Messages.\u003c/p\u003e\n"],["\u003cp\u003eIt allows customization of the publication strategy, status handling, and user permission requests.\u003c/p\u003e\n"],["\u003cp\u003eA \u003ccode\u003estrategy\u003c/code\u003e property defines how the message is published, with a default strategy available.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003estatusHandler\u003c/code\u003e and \u003ccode\u003epermissionRequestHandler\u003c/code\u003e properties enable monitoring publication status and managing user permissions, respectively.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers can override the default permission dialog by providing a custom \u003ccode\u003epermissionRequestHandler\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# GNSPublicationParams Class\n\n[Properties](#properties) \nGNSPublicationParams Class Reference \n\nOverview\n--------\n\nOptional parameters for a publication.\n\nSee the property declarations below for explanations of each parameter.\n\nInherits NSObject.\n\n|---------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Property Summary ---------------- ||\n| [GNSStrategy](/nearby/messages/ios/reference/interface_g_n_s_strategy) \\* | [strategy](/nearby/messages/ios/reference/interface_g_n_s_publication_params#aa5b307ccee2b3c5214cde08cd2bfb7e4) |\n| | The strategy to use for publishing the message. See [GNSStrategy](/nearby/messages/ios/reference/interface_g_n_s_strategy \"The strategy to use to detect nearby devices. \") for the default. [More...](#aa5b307ccee2b3c5214cde08cd2bfb7e4) |\n| ||\n| GNSOperationStatusHandler | [statusHandler](/nearby/messages/ios/reference/interface_g_n_s_publication_params#a59b5094d5f639371724e7475defb6b63) |\n| | A handler for publication status. [More...](#a59b5094d5f639371724e7475defb6b63) |\n| ||\n| GNSPermissionRequestHandler | [permissionRequestHandler](/nearby/messages/ios/reference/interface_g_n_s_publication_params#a09124c8fa69e5b3dc46c4d102eddb0b1) |\n| | A handler for requesting user permission to use Nearby. [More...](#a09124c8fa69e5b3dc46c4d102eddb0b1) |\n| ||\n\nProperty Detail\n---------------\n\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|\n| |---------------------------------------------------------------------------------------| | - ([GNSStrategy](/nearby/messages/ios/reference/interface_g_n_s_strategy)\\*) strategy | | readwritenonatomicassign |\n\nThe strategy to use for publishing the message. See [GNSStrategy](/nearby/messages/ios/reference/interface_g_n_s_strategy \"The strategy to use to detect nearby devices. \") for the default. \n\n|-------------------------------------------------------------------------------------------------|------------------------|\n| |---------------------------------------------| | - (GNSOperationStatusHandler) statusHandler | | readwritenonatomiccopy |\n\nA handler for publication status.\n\nIt can be used for tracking the status of a newly created publication. \n\n|---------------------------------------------------------------------------------------------------------------------------|------------------------|\n| |----------------------------------------------------------| | - (GNSPermissionRequestHandler) permissionRequestHandler | | readwritenonatomiccopy |\n\nA handler for requesting user permission to use Nearby.\n\nThis handler overrides the default dialog used by Nearby; if you supply this handler, Nearby will not show its permission dialog.\n\nIn your request handler, you should request the user's permission to perform the task that requires the use of Nearby, explaining why it's being used. When the user has given or denied consent, you must call the block that's passed into your request handler. If you pass `YES` into the block, it means the user has consented to allow Nearby to function. If you pass `NO`, it means the user has not consented; your publications and subscriptions will not work until consent has been given.\n\nThe handler can also be used as a method of \"preflighting\" for the iOS permission dialogs. You can use it to explain why the user is expected to consent to the iOS permissions before your app can perform its Nearby related functions."]]
