FR: watchOS Support #269

mknippen · 2017-09-14T05:30:42Z

With the release of watchOS 4 and an LTE Apple Watch, there’s no better time to plan support for Apple Watch. The Series 3 Watch has significantly more power, and applications will want to connect to Firebase.

salqadri · 2017-09-20T17:30:10Z

Hi Matthew! Yes WatchOS4 looks awesome and we are keeping a close watch (pun intended) on this platform. We will continue to evaluate officially supporting the platform as it grows in apps and users, but until we do, we welcome any community contributions in this area.

boblepepeur · 2017-10-28T17:25:27Z

I'm In !

coolioxlr · 2017-11-16T02:48:38Z

+1

robpeach · 2018-02-07T02:15:03Z

+1

dyah10 · 2018-03-21T13:11:22Z

+1

wipnick · 2018-03-23T14:56:03Z

+1

ugenlik · 2018-06-08T13:49:24Z

+1

Lawris · 2018-07-12T09:20:07Z

+1

polok · 2018-07-22T04:37:57Z

+1

thattyson · 2018-08-07T21:05:30Z

+1

AsteaDevelopment · 2018-09-07T13:54:10Z

+1

fabricio-stein · 2018-09-08T16:19:36Z

+1

GioPalusa · 2018-09-25T20:15:53Z

Watch OS 5 is here, and an addition with Firebase to WatchOS would be greatly appreciated! +1

zhgchgli0718 · 2019-01-14T02:35:06Z

+1

@available

* compile and run * unit tests pass and swift target compiles * dump build version in activity log * standardize cross sdk imports in firebase iam code (#211) standardize cross sdk imports & polish with style script * using new sample app for testing non-development fiam sdk (#213) * in-app messaging public interface cleanup (#216) * slim down public header files * move testing source files to their correct folders * compiles * style script fine-tune * adding root object creation methods to follow the firebse iOS convension * IAM url following refactor (#218) * @available not supported by blaze build yet (#220) * Clearcut integration for in-app messaging (#222) * Update iam-master to catch up with latest master (#223) * Support multiple triggers defined for the same iam message (#224) * FIAM Clearcut Client Implmentation Improvement (#226) * fixing action url bug and set auto dismiss to be 12 seconds (#227) * use official public api dns name (#233) * Logging firebase analytics events for fiam (#232) * Fine tuning of fiam's code for loading data from caches (#234) * fiam ui fine tuning before EAP (#235) * allow fiam SDK functions to be disabled/enabled dynamically (#247) * analytics event parameter name tuning (#253) * migrate off @import for fiam code (#261) * different modes for fiam sdk at runtime (#262) * realtime clearcut when in running in simulator (#265) * Update interface based on the Firebase API review feedback (#267) * check existence of fiam SDK resource bundle (#268) * handling api keys with application restrictions (#269) * fixing typo and refoctor for unit testing (#270) * fix color method name clash and layout adjust (#271) * Yongmao/layout issue and class rename (#273) * fix long text height calc error * rename class * fiam modal view layout tuning (#274) * test on device for ios client (#275) * dynamic testing mode handling (#277) * main header file comment update and run style.sh (#281) * honor global firebase auto data collection flag in fiam (#283) * honor global firebase auto data collection flag in fiam * address comments * tuning * address review comments * tuning for comments * Rename Core global data collection switch (#287) * Support displaying a messages defined as recurring (#286) * continue * Adjust some inapp messaging dependeces due to the firebase core changes from the upcoming release * bump up version for in-app messaging * Fix impression log clearing race condition bug. (#289) * fix impression handling race condition bug * podspec and interacting interfaces for new firebaseinappmessagingdisplay pod (#290) * create inapp messaging display podspec * Default fiam display UI implementation (#292) * Default fiam display UI implementation. Created the new pod for FirebaseInAppMessagingDisplay * Make FirebaseInAppMessaging headless (#293) * import path tuning * log test message events (#296) * respect fetch wait time from server (#297) * add changelog.md for fiam headless sdk (#300) * port the fetch wait time change back into github (#304) * remove resource bundle check for headless sdk * fix a bug in which the test-on-device message does not follow action url * Add category on NSString to interlace two strings, use it to obfuscate clearcut host name * Use FIR prefix to avoid collisions * Change method name for getting server hostname * Delete Swift example project, its coverage is already duplicated in the FIRInAppMessagingDisplay UITests * Miscellaneous open sourcing cleanup tasks * Convert FIAM to use the Analytics connector (#336) * Convert FIAM to use Analytics connector along with converting to the FIRLibrary component registration model. * Update interop headers for missing methods * Convert existing unit tests * Fix style for fiam sources (#342) * Clean up non-idiomatic ObjC method names * Clean up Swift test target from Podfile * Use dummy GoogleService-Info.plist and don't expose api keys (#343) * Update plist to include fake API keys * Remove changes in non fiam code from iam-master branch (#350) * Fix a few method and parameter naming nits * Fix comment typos in several files * Delete remaining Swift project files

mikemike396 · 2019-02-12T19:35:09Z

Any update on this?

mariohahn · 2019-03-07T13:50:57Z

+1

Supertecnoboff · 2019-04-01T10:21:27Z

2019 and still no watchOS support 😢

sotrosh · 2019-05-09T13:17:57Z

just watched firebase 2019. Added wearOS support. No watchOS support still.

pepejeria · 2019-06-06T09:09:34Z

I guess that this won't be an issue anymore with watchOS 6 since apps are independent?

mknippen · 2019-06-06T14:33:08Z

I think this will be a much bigger issue. Hopefully with all of the streaming data and network framework, we can make this available ASAP!

…

On Jun 6, 2019, at 4:09 AM, José Jeria ***@***.***> wrote: I guess that this won't be an issue anymore with watchOS 6 since apps are independent? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#269?email_source=notifications&email_token=AABTJ3GQ25BNHTXFWAKTKATPZDH5NA5CNFSM4D24IZL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXCHJBI#issuecomment-499414149>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABTJ3AD5RVKFDXAWYDRRK3PZDH5NANCNFSM4D24IZLQ>.

Supertecnoboff · 2019-06-06T14:36:30Z

I think this will be a much bigger issue. Hopefully with all of the streaming data and network framework, we can make this available ASAP!
…

Surely you can add watchOS support because presumably watchOS 6 has the CFNetwork framework?

robbiet480 · 2019-06-12T07:13:36Z

My assumption is that watchOS won't be supported until Google Analytics is supported which is gonna be a long time since we don't have UIKit for watchOS and at this point it's unlikely we ever will with the introduction of SwiftUI, so GA would have to get rewritten to support SwiftUI or at least remove the hard requirement on UIKit.

ryanwilson · 2019-06-14T20:07:14Z

Started some investigation into this and kicked off the attempt with GoogleUtilities since it has no dependencies and is a dependency of all other Firebase SDKs - a few hurdles to start:

OCMock isn't available for watchOS, meaning a majority of our tests won't work
A larger hurdle (after disabling the test_spec in the podspec) the SystemConfiguration framework isn't available in watchOS.
- This affects three subspecs: Reachability, Network, and AppDelegateSwizzler, which in turn affects Auth, Messaging, and Analytics.

It looks like it may be possible to add support for individual subspecs and maybe that's the way to pare it down further, but unfortunately this won't be as easy as just adding s.watchos.deployment_target = '5.0'

If anyone else wants to make an attempt in the meantime, you may be able to start adding support for each subspec and then creating a new watchOS target in the Example Xcode project.

morganchen12 · 2019-06-14T21:22:12Z

@ryanwilson watchOS tests running on simulator are compiled against the iOS simulator target. This might change with standalone watch apps, but afaik hasn't yet in watchOS 6. iOS simulator testing + build targeting watchOS should be sufficient for watchOS for the time being. I made a PR to OCMock to add watchOS support, but it shouldn't be a blocker for testing.

ryanwilson · 2019-06-17T17:05:41Z

@morganchen12 makes sense, the issue I ran into was using pod lib lint and pod gen - the watchOS bit choked when getting to the test spec that depended on the OCMock pod. I disabled the test spec to generate the project instead.

Re: SystemConfiguration not being available, it looks like WatchConnectivity has a reachability function we can use to replace the one in SystemConfiguration.

larryonoff · 2019-07-04T04:55:52Z

It would be really appreciated to do watchOS support at least from 6.0.

morganchen12 · 2019-07-29T18:00:11Z

Additional FR #3453

sotrosh · 2019-09-23T03:26:09Z

any updates on this issue? watchOS 6 has released.

morganchen12 · 2019-11-11T23:19:44Z

watchOS support was merged into OCMock today. In preparation for this feature, we can start running tests on watchOS simulator once OCMock makes a new release.

kajensen · 2019-12-10T15:29:53Z

Any movement on this issue?

paulb777 · 2019-12-20T02:57:18Z

Progressing at #4016

paulb777 · 2019-12-24T00:55:12Z

Now that #4016 has merged with support for FirebaseMessaging and watchOS and will be part of the first release of 2020, I'm going to close this is umbrella issue.

Please open additional issues for any additional specific requested functionality for watchOS.

mknippen · 2019-12-24T15:53:14Z

@paulb777 Is this supporting the Firebase Database on independent watch apps, or just Firebase Messaging? The original ticket here was so that we can make read/writes to the Realtime Database in watchOS

paulb777 · 2019-12-24T16:10:21Z

@mknippen It's just Firebase Messaging so far.

Going back and looking at the OP, I don't see the Firebase Database mention.

How about creating another issue specifically for Database and watchOS? A similar issue could be created for any other requested Firebase libraries for watchOS. That will help us prioritize.

BTW, if anyone wants to work on this, the approach would be to update the relevant podspec's like #4016, working though any build issues, validating, and sending a PR.

n3at18 · 2019-12-27T14:36:19Z

@paulb777 @mknippen I've created a separate feature request for Realtime Database support: #4556

jroets · 2019-12-27T15:31:58Z

I've created feature requests for Firebase Analytics and Firebase Crashlytics on watchOS: #4557 and #4558, respectively.

morganchen12 added the type: feature request label Sep 14, 2017

paulb777 added the help wanted label Sep 20, 2017

mknippen changed the title ~~FR: WatchOS Support~~ FR: watchOS Support Jan 3, 2019

morganchen12 added the watchOS label Jun 5, 2019

morganchen12 mentioned this issue Jul 29, 2019

watchOS 6 support #3453

Closed

maksymmalyhin mentioned this issue Oct 9, 2019

FirebaseInstallations: CreateInstallation API request error handling #4024

Merged

charlotteliang mentioned this issue Nov 7, 2019

Enables Firebase Messaging push notification function on watch only and independent watch app #4016

Merged

paulb777 closed this as completed Dec 24, 2019

mknippen mentioned this issue Dec 27, 2019

FR: RealtimeDatabase support for WatchOS #4556

Closed

hohteri mentioned this issue Jan 8, 2020

FR: Firebase Auth support for watchOS #4621

Closed

firebase locked and limited conversation to collaborators Jan 23, 2020

FR: watchOS Support #269

FR: watchOS Support #269

Comments

mknippen commented Sep 14, 2017 • edited Loading

salqadri commented Sep 20, 2017

boblepepeur commented Oct 28, 2017

coolioxlr commented Nov 16, 2017

robpeach commented Feb 7, 2018

dyah10 commented Mar 21, 2018

wipnick commented Mar 23, 2018

ugenlik commented Jun 8, 2018

Lawris commented Jul 12, 2018

polok commented Jul 22, 2018

thattyson commented Aug 7, 2018

AsteaDevelopment commented Sep 7, 2018

fabricio-stein commented Sep 8, 2018

GioPalusa commented Sep 25, 2018

zhgchgli0718 commented Jan 14, 2019

mikemike396 commented Feb 12, 2019

mariohahn commented Mar 7, 2019

Supertecnoboff commented Apr 1, 2019

sotrosh commented May 9, 2019

pepejeria commented Jun 6, 2019

mknippen commented Jun 6, 2019 via email

Supertecnoboff commented Jun 6, 2019

robbiet480 commented Jun 12, 2019 • edited Loading

ryanwilson commented Jun 14, 2019

morganchen12 commented Jun 14, 2019

ryanwilson commented Jun 17, 2019 • edited Loading

larryonoff commented Jul 4, 2019

morganchen12 commented Jul 29, 2019

sotrosh commented Sep 23, 2019

morganchen12 commented Nov 11, 2019

kajensen commented Dec 10, 2019

paulb777 commented Dec 20, 2019

paulb777 commented Dec 24, 2019

mknippen commented Dec 24, 2019

paulb777 commented Dec 24, 2019

n3at18 commented Dec 27, 2019

jroets commented Dec 27, 2019

mknippen commented Sep 14, 2017 •

edited

Loading

robbiet480 commented Jun 12, 2019 •

edited

Loading

ryanwilson commented Jun 17, 2019 •

edited

Loading