mirror of
https://github.com/OAuthSwift/OAuthSwift.git
synced 2026-04-26 12:45:52 +03:00
[GH-ISSUE #135] watchOS 2.0 support? #83
Labels
No labels
bug
cocoapod
duplicate
enhancement
feature-request
help wanted
help wanted
invalid
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/OAuthSwift#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mohwaili on GitHub (Oct 31, 2015).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/135
Will the watchOS 2.0 get any support?
@sucharuhasija commented on GitHub (Oct 31, 2015):
Yes
On 31-Oct-2015 9:39 pm, "mohwaili" notifications@github.com wrote:
@phimage commented on GitHub (Oct 31, 2015):
must edit podspec and add
then add in code watchos ant tvos case (
#if os (watchOS)) when there isI can PR next week but don't know when PR will be merged
@phimage commented on GitHub (Nov 9, 2015):
@mohwaili or @sucharuhasija did you make development for watchos ?
Is it really necessary to make a framework compatible with watchos because when I create a project on xcode, all controller code seems to be executed on iOS, only UI is on the watch, but maybe I am wrong
I already add compatibility into podspec with one of my own project and see that watch os compile code with i386 , not x86_64 '(and have some bugs)
@mohwaili commented on GitHub (Nov 9, 2015):
@phimage The problem I had is: my project has a shared framework and I wanted to reuse it for the apple watch (since watch os2 it's only possible when duplicating the framework target). The user authentication is embedded in this shared framework, when installing the pod I received an error. So the quick fix was adding watch os2 support without changing anything in my shared framework.
The answer to your question: it's not necessary to add watch os2 support, I should have had considered this issue from the beginning. Now I've separated the login and authentication from the shared framework and everything is working.