Fixes to remove warnings after updating project to recommended settings #290
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
|
Travis CI breaks. Are these changes still compatible with iOS 7? |
Author
|
Not sure. The lowest you can do in the latest XCode is 8. They compile clean for 8 and above (thats what I tested).
Take care,
Craig
… On Mar 26, 2018, at 03:43, Nicolas Seriot ***@***.***> wrote:
Travis CI breaks.
Are these changes still compatible with iOS 7?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After updating the to the latest iOS11 recommended XCode project settings there are a number of warnings. This PR just cleans up the warnings so that the STTwitter source compiles without any warnings.