Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Avoid using unavailable APIs when linking against app extension targets. #80

Closed
YuAo opened this issue Feb 15, 2015 · 5 comments
Closed

Avoid using unavailable APIs when linking against app extension targets. #80

YuAo opened this issue Feb 15, 2015 · 5 comments

Comments

@YuAo
Copy link

YuAo commented Feb 15, 2015

When using Bolts in an app extension development. Some Blots classes have references to [UIApplication sharedApplication] which is not available in an app extension target.

Need a way to avoid the unavailable API usage when linking against app extension targets. Maybe a macro for conditional compile?
@siuying
Copy link

siuying commented Mar 11, 2015

Or please separate two subspecs: Tasks and AppLinks. The AppLinks is not needed for extension anyway.

@smeador
Copy link

smeador commented Mar 25, 2015

+1 Two subspecs would be very nice. Tasks and AppLinks are independent from each other, and I would like to use Tasks in static libraries as well.

@Arthraim
Copy link

two subspecs +1 ;)

@josephearl
Copy link

See #60 for the specs issue

@ghost ghost mentioned this issue Apr 16, 2015
Merged
@nlutsenko
Copy link
Member

Fixed by #94

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@siuying @Arthraim @smeador @nlutsenko @YuAo @josephearl