-
Notifications
You must be signed in to change notification settings - Fork 511
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to add native Watch app #16417
Comments
Hello! Agreed, we need to document this better there are some good hints here #10070 (comment) we'll have a look at this in the future since watchOS is not currently supported in .NET 6/7 |
@dalexsoto you may want to refer to the document by @vouksh https://codebloq.io/2022/12/02/xamarin-ios-with-swiftui-watchos-app/ if you are not to write your own document for Xamarin.iOS, it may not be at the level of your documentation (and is not intended to be) but it is very usable. |
So using SwiftUi is the only way to build WatchOS apps today? can we not create using Xamarin WatchOS like Objective-C style with Storyboards? I have tried default template but I am unable to deploy on WatchOS simulator through Ios App. Is it now completely broken? I have created a SO issue |
@EmilAlipiev Unfortunately, Microsoft has dropped support for watchOS. There's not enough of us to warrant the amount of work they'd need to keep up with the latest changes. If you're starting a new project, your best bet is to go with MAUI + Native (SwiftUI/Kotlin) Watch apps if you still want to stay in .NET. Otherwise your best bet is to go with a full native app. I'm working on making a demo Maui (Phone) + SwiftUI (Watch) app so that I can write up instructions on pairing those up. |
@vouksh thanks for your comment. It is clear for me that Maui is not supporting. I have xamarin app and i want to add watchos extension. I could achieve to use watchos with c# today. project is running on my simulator and watch. From my understanding still until May 2024, Xamarin will get updates. Will that actually makes sense to use it still if i want to get a quick watchos version and in 2024 convert into SwiftUi. Or is there anyone obstacles deploying a Xamarin.Ios.WatchOs with the latest Xcode? |
Xamarin will no longer get any Xcode major updates. So the current Xcode in beta will never be supported by Xamarin. (Edit: just saw vouksh comments above, which is mostly the same as below, sorry for the double post) The team have said the number of people using watchOS was very low, so not adding support was acceptable to focus on other things. tvOS may also have a very small user base but it also is very similar to iOS SDKs so there was not much effort required to add it, which can not be said for watchOS. IMO I wouldn't hold my breath for watchOS support so I think the best way to build watchOS apps today is to build it natively and embed it into your MAUI iOS/net7-ios bundle. |
oh ok. "Xamarin will no longer get any Xcode major updates." i thought that they would still update us till next year May. thats of course game changer. too bad. |
See here for more info, but the main bit is
Xamarin will still be getting updates/bug fixes for its current things, but it won't ever target Android 14 or use Xcode 15 (iOS 17) SDKs. |
Can you publish working sample pls? |
I've thrown together a quick example from one of my test projects. MauiWithWatchApps |
Closing as a duplicate of #20317. |
It seems to be possible to add the native Watch app to the Xamarin app but with 0 documentation. According to #16142 this is done using
_ResolvedWatchAppReferences
Searching for this on the internet returned just that page, so it is not reasonable to think that anyone can do it.
On the other hand as noted here: #16120 , watchOS is not technically supported anymore since one month ago and I think it is reasonable not to ask for that fix from Microsoft as they don't have enough funds to support enough engineers to fix something like that (and you know that this is the fact).
Considering all of this it would be nice if you made some sample on how to do this. I have no expectations and I have Plan B, just it is really yours if you want developers to use Xamarin at all or not...
The text was updated successfully, but these errors were encountered: