AppCheck support for watchOS

[Semty]

Feature proposal

• Firebase Component: AppCheck

We've implemented support for AppCheck in our app ecosystem (iOS, Android, Web) and thinking about enforcing App Check verification.

The main obstacle is that we have watchOS as well and it seems that AppCheck doesn't support it (well, of course, DeviceCheck and AppAttest just not available on watchOS).

What is the expected behaviour in this situation? Should we just abandon the idea of using AppCheck in a foreseeable future or there is some workaround we could do?

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[paulb777]

@Semty Thanks for the request. AppCheck should be community supported where possible for watchOS.

We just merged a PR fix today - #9187 that fixes a Firebase podspec issue for watchOS that will be available with the next release - 8.11.0. In the meantime - a CocoaPods workaround might be changing the Podfile from Firebase/AppCheck to FirebaseAppCheck

[paulb777]

I'll close since there is a staged fix and workaround, but please comment if you have another issue and we can reopen.

[Semty]

@paulb777 hey! it seems that the desired effect is seen only with using Cocoapods, but with SPM I get this after adding AppCheck for watchOS target:
DeviceCheck is not available when building for watchOS.

[paulb777]

Hi @Semty AppCheck should be available for watchOS for both CocoaPods and SPM. Device Check is not available for watchOS. See https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseAppCheck/Sources/Public/FirebaseAppCheck/FIRAppCheckAvailability.h and https://github.com/firebase/firebase-ios-sdk/blob/master/FirebaseAppCheck/Sources/Public/FirebaseAppCheck/FIRDeviceCheckProvider.h#L33

[Semty]

@paulb777 hello! Thank you for the quick response!

Of course, DeviceCheck is not available for watchOS, but the truth is that I don't use it in a watchOS target, I get this error just by adding FirebaseAppCheck package to the watchOS target

[paulb777]

@Semty Thanks for clarifying! I can reproduce and it looks like a problem in the Package.swift specification. I'll reopen and see if I can come up with a fix.