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

Minimum fixes for Xcode 9.3 build errors #1143

Closed
wants to merge 6 commits into from

Conversation

ikesyo
Copy link
Contributor

@ikesyo ikesyo commented Apr 4, 2018

Changes in this pull request

Issue fixed: #1141

This is a set of minimum fixes for Xcode 9.3 rather than #1142. Much smaller diffs 😃

The changes here were done by Xcode's FixIt. See also https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/Strings/Articles/formatSpecifiers.html#//apple_ref/doc/uid/TP40004265-SW5.

Platform Dependencies

OS X uses several data types—NSInteger, NSUInteger,CGFloat, and CFIndex—to provide a consistent means of representing values in 32- and 64-bit environments. In a 32-bit environment, NSInteger and NSUInteger are defined as int and unsigned int, respectively. In 64-bit environments, NSInteger and NSUInteger are defined as long and unsigned long, respectively. To avoid the need to use different printf-style type specifiers depending on the platform, you can use the specifiers shown in Table 3. Note that in some cases you may have to cast the value.

Checklist

  • All tests pass. Demo project builds and runs.
  • I added tests, an experiment, or detailed why my change isn't tested.
  • I added an entry to the CHANGELOG.md for any breaking changes, enhancements, or bug fixes.
  • I have reviewed the contributing guide

@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request. View: changes

@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request. View: changes

@iglistkit-bot
Copy link

iglistkit-bot commented Apr 4, 2018

1 Warning
⚠️ All pull requests should have a milestone attached, unless marked #trivial.

Generated by 🚫 Danger

@ikesyo
Copy link
Contributor Author

ikesyo commented Apr 4, 2018

@rnystrom @jessesquires Could you please review this?

@ikesyo ikesyo force-pushed the fix-xcode-9.3-build-errors branch from 8f66779 to 90e2edf Compare April 4, 2018 03:41
@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request.

@ikesyo
Copy link
Contributor Author

ikesyo commented Apr 4, 2018

I'm not sure why there are some SwiftLint violations from Examples in this PR: https://travis-ci.org/Instagram/IGListKit/jobs/361956020 but those are not seen in master: https://travis-ci.org/Instagram/IGListKit/jobs/361911790

@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request. View: changes

@ikesyo
Copy link
Contributor Author

ikesyo commented Apr 4, 2018

#1143 (comment)

Updated .swiftlint.yml to exclude the occurences:

  • url
  • to
  • obj
  • str
  • set

> Assertion Failure: MixedDataViewControllerUITests.swift:51: XCTAssertFalse failed: throwing "Invalid query - string identifier 'Maecenas faucibus mollis interdum. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit.' exceeds maximum length of 128 characters. You can work around this limitation by constructing a query with a custom NSPredicate that specifies the property (label, title, value, placeholderValue, or identifier) to match against." -
@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request. View: changes

@facebook-github-bot
Copy link
Contributor

@ikesyo has updated the pull request. View: changes

@ethanjdiamond
Copy link

Hi IG team!

Are you planning on merging this in and releasing soon? It's blocking my team's upgrade to Xcode 9.3.

@iostriz
Copy link

iostriz commented Apr 9, 2018

Hi IGlisters,
this is a real showstopper for our team also.
Please?

@rnystrom
Copy link
Contributor

rnystrom commented Apr 9, 2018

Our internal CI just moved to 9.3 over the weekend which means we can merge, that was the only thing holding us back. I’ll land this today!

Sent with GitHawk

Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rnystrom is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@ikesyo ikesyo deleted the fix-xcode-9.3-build-errors branch April 9, 2018 15:44
@ikesyo ikesyo restored the fix-xcode-9.3-build-errors branch April 9, 2018 15:44
@ethanjdiamond
Copy link

Thanks for the quick work @rnystrom! Is the team going to put out a release soon to grab this change from, or should we temporarily tie it to this commit hash?

@rnystrom
Copy link
Contributor

rnystrom commented Apr 9, 2018

@ethanjdiamond we’re stabilizing a couple recent merges and want to hold a fresh release til it’s totally stable. Feel free to just use the master branch for the time being (it’s what we use in Instagram).

Sent with GitHawk

@SebastianBoldt
Copy link

@rnystrom
Is there already a concrete date when the new version will be released? We would like to upgrade our build server to the new Xcode version, but the last IGListKit version does not work with Swift 4.1.

@rnystrom
Copy link
Contributor

@SebastianBoldt nothing concrete but its moving right now (see #1150 and #1151). Blocked on CI for #1152 that I'm trying to figure out. Once that's moving it's just a matter of genning docs and publishing. Shouldn't be more than a couple days!

@ikesyo ikesyo deleted the fix-xcode-9.3-build-errors branch April 24, 2018 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build error (carthage), xCode 9.3, swift 4.1
7 participants