Skip to content

Conversation

yakovmanshin
Copy link
Contributor

  • Since Package.swift already limits Functions support to Catalyst 13, macOS 10.15, tvOS 13, and watchOS 7, explicit checks for these versions aren’t needed
  • @available attributes and #available checks for iOS 13 remain in place

* Since `Package.swift` already limits Functions support to Catalyst 13, macOS 10.15, tvOS 13, and watchOS 7, explicit checks for these versions aren’t needed
* `@available` attributes and `#available` checks for iOS 13 remain in place
@ncooke3 ncooke3 self-assigned this Oct 14, 2024
@ncooke3
Copy link
Member

ncooke3 commented Oct 14, 2024

I think these may still be relevant for other distributions like the Firebase zip distribution and maybe CocoaPods.

@paulb777
Copy link
Member

I believe we're ok without these for CocoaPods, as well, except for maybe the Catalyst ones. However, I'm leaning towards keeping the full list for clarity.

@yakovmanshin
Copy link
Contributor Author

Alright, sounds good.

Just one clarification. In v11, deployment target became iOS 13 for all components except Analytics and Crashlytics, but because SPM doesn’t support per-product versions, Functions (and other targets) continue using iOS 12 in Package.swift. Does that mean all features should fully support iOS 12, despite it’s been dropped?

@paulb777
Copy link
Member

No, we're setting the expectations that only Analytics and Crashlytics are fully supported for iOS 12. For example the new implementation of FirebaseAuth has almost zero support for iOS 12.

@yakovmanshin
Copy link
Contributor Author

Thanks!

Closing this PR.

@yakovmanshin yakovmanshin deleted the functions-unused-availability-checks branch November 7, 2024 15:25
@firebase firebase locked and limited conversation to collaborators Nov 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants