PlacesClient methods should only be called from the main thread. Calling these methods from
another thread will result in an exception or undefined behavior.
[[["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-05-06 UTC."],[[["The `PlacesClient` class is the primary interface for interacting with the Places SDK, enabling functionalities like searching for places and retrieving place details."],["Access the `PlacesClient` through the shared instance `PlacesClient.shared`."],["Ensure all `PlacesClient` methods are exclusively called from the main thread to avoid exceptions or unexpected behavior."]]],["The core content introduces the `PlacesClient` class, the main interface for the Places SDK, used for place searching and detail retrieval. It should be accessed via `PlacesClient.shared`. Key actions involve using its methods to interact with place data. Critically, all `PlacesClient` methods must be called exclusively from the main thread; using them from other threads will cause errors or unpredictable results. It's defined as a final class and conforms to `PlacesClientProtocol`.\n"]]