[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-05 (世界標準時間)。"],[],[],null,["\u003cbr /\u003e\n\nWe're merging our Swift extension SDKs into the main SDKs in order to make\nSwift-native APIs more broadly available and increase our ability to support\nnew Swift language features in the future. The changes we're making and their\nexpected impacts on your projects are documented below.\n\nWhat's changing?\n\nStarting with Firebase for Apple SDK 10.17.0, the Swift extension SDKs have\nbeen merged into their corresponding main SDKs. For example, all of the APIs\nfrom the `FirebaseFirestoreSwift` module have been added to `FirebaseFirestore`,\nso you no longer have to import the `FirebaseFirestoreSwift` module to access\nthose APIs.\n\nAs all Swift extensions now are part of the main modules, the extension SDKs\nare no longer required, and are deprecated. Including or using the Swift\nextension SDKs will raise a compiler warning and as early as February 2024,\nwe'll stop releasing the Swift extensions entirely.\n\n★ Note: Any currently or previously released versions of the Swift extensions\nwill still function. However, we recommend that you migrate your app to use\nSwift APIs from the main module to ensure you continue to receive fixes and can\ntake advantage of changes and new features.\n\nImportant dates for this change\n\nIn October 2023\n\nThe Swift extension SDKs have been merged into the main SDKs and then\ndeprecated in favor of the main SDKs. See the release notes for version 10.17.0\nannouncing this change.\n\nYou can now use the Swift extension SDK APIs directly from the main SDK modules.\nUsage of the extension SDKs will is still possible until the next major version\nrelease but will raise a deprecation warning when used.\n\nAs early as February 2024\n\nWe'll stop releasing new versions of the Swift extensions, and we'll remove the\nSwift extensions from Firebase's `Package.swift`. Older versions will continue\nto function but will not receive updates.\n\nHow to migrate to use Swift-native APIs from the main module\n\nIf you currently do not use the Swift extension SDKs, no action is necessary. If\nyou do use a Swift extension SDK, make the following changes in your project.\n\nWorkspace changes\n\nSwift Package Manager\n\nAfter updating Firebase to version 10.17.0+, navigate to the Frameworks,\nLibraries, and Embedded Content section in the General tab of your target's\nsettings and remove the Swift extension SDK (such as `FirebaseFirestoreSwift`).\n\nCocoaPods\n\nAfter updating Firebase to version 10.17.0+, navigate to your Podfile and remove\nthe line corresponding to your project's dependency on adding the frameworks\nsection for your target and remove the Swift extension SDK\n(such as pod `FirebaseFirestoreSwift`). Then, re-run the `pod install` command.\n\nZip distribution and Carthage\n\nAfter updating Firebase to version 10.17.0+, remove any Swift extension\n`xcframeworks` within your project (such as\n`FirebaseFirestoreSwift.xcframework`).\n\nSource code changes\n\nFor all of the Swift extension SDKs you previously used, take the following\nactions:\n\n1. Delete any import statements referencing the Swift extension SDK. If the main SDK was not imported separately, you will need to replace the Swift extension import with the main SDK import by deleting the `Swift` at the end of the line.\n2. If you used Swift's explicit-module namespacing to reference any Swift extension SDK types, you will need to replace those with the corresponding main SDK. For example, `FirebaseFirestoreSwift.QueryPredicate` would need to be renamed to `FirebaseFirestore.QueryPredicate`."]]
