PlacesClient methods should only be called from the main thread. Calling these methods from
another thread will result in an exception or undefined behavior. Unless otherwise specified,
all callbacks will be invoked on the main thread.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-11-08 UTC."],[[["This documentation details globally available protocols within the Places SDK for iOS."],["These protocols provide functionality for tasks such as fetching App Check tokens, defining coordinate regions, and interacting with the Places SDK."],["Some protocols, like `CoordinateRegionBias` and `CoordinateRegionRestriction`, should not be conformed to by external types to avoid errors."],["The `PlacesClientProtocol` is the primary interface for using the Places SDK, offering methods for searching and retrieving place details."],["All interactions with the Places SDK, including calls to `PlacesClient` methods, should occur on the main thread for stability and predictable behavior."]]],["The core content details several Swift protocols available globally: `AppCheckTokenProvider` for fetching App Check tokens, `CoordinateRegion` for specifying coordinate region information, and `CoordinateRegionBias` and `CoordinateRegionRestriction` for defining search biases and restrictions. `PlaceProtocol` is available and the `PlacesClientProtocol` serves as the main interface for searching and retrieving place details, accessible via `PlacesClient.shared` and it must be used only from the main thread.\n"]]
