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.

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

Removing warning if NSAssert is undefined #53

Closed
wants to merge 3 commits into from
Closed

Removing warning if NSAssert is undefined #53

wants to merge 3 commits into from

Conversation

HiddenJester
Copy link
Contributor

The new checkAppGroupCapabilities function creates a NSURL and then uses it in a NSAssert macro. If NS_BLOCK_ASSERTIONS is defined (as it is in a release or beta build) then NSAssert is a no-op and you get a warning about the unused variable. This change only creates the NSURL if NSAssert is going to use it, and therefore removes the warning on builds without NSAssert.

Pulling the 1.2 release into the fork
- Providing a init method for MMWormholeFileTransiting because inheriting from NSObject requires it now.
@cnstoll
Copy link
Contributor

cnstoll commented Sep 14, 2015

Thank you for this! I ended up pulling it in as part of the watchOS branch, so I'm going to close the PR. It'll be merged in as part of the 1.3.0 milestone. Thanks again!

@cnstoll cnstoll closed this Sep 14, 2015
@cnstoll cnstoll added this to the 1.3.0 milestone Sep 14, 2015
@HiddenJester
Copy link
Contributor Author

Sure no problem. Glad it was helpful, and thank you for providing MMWormhole in the first place!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants