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

πŸ§˜β€β™€οΈ[Xcode] Zen out build warnings #720

Merged
merged 5 commits into from
Jun 25, 2019

Conversation

dusi
Copy link
Contributor

@dusi dusi commented Jun 23, 2019

πŸ“² What

Cleans up all outstanding Xcode warnings

πŸ€” Why

Warnings should be an indication that something is wrong. We haven't really pay much attention to this because our project has been producing at least couple warnings in the past and therefore it's easy to introduce new ones (because we simply don't take them seriously).

πŸ›  How

Updated Xcode project with Xcode's update tool

πŸ‘€ See

Before After
Screen Shot 2019-06-23 at 8 47 22 PM Screen Shot 2019-06-23 at 8 46 48 PM

πŸ› Architectures - Before

Screen Shot 2019-06-22 at 8 23 30 PM

πŸ¦‹ Architectures - After

Screen Shot 2019-06-22 at 8 23 56 PM

πŸ› Code signing - Before

Screen Shot 2019-06-22 at 8 20 47 PM

πŸ¦‹ - Code signing - After

Screen Shot 2019-06-22 at 8 20 49 PM

βœ… Acceptance criteria

  • 32-bit devices are still not allowed
  • Project builds and produces no warnings (other than type-check limit in some expensive functions)

@dusi dusi requested a review from justinswart June 23, 2019 03:56
@dusi dusi changed the title πŸ§˜β€β™€οΈ [Xcode] Zen out build warnings πŸ§˜β€β™€οΈ[Xcode] Zen out build warnings Jun 23, 2019
@@ -5544,7 +5548,6 @@
buildSettings = {
ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES = NO;
ALWAYS_SEARCH_USER_PATHS = NO;
ARCHS = "$(ARCHS_STANDARD)";
Copy link
Contributor Author

Choose a reason for hiding this comment

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

It looks like that after removing this it still resolves into Standard Architecture anyways Β―_(ツ)_/Β―

@@ -177,7 +177,7 @@ internal final class ActivitiesViewController: UITableViewController {
}

self.viewModel.outputs.updateUserInEnvironment
.observeValues { [weak self] user in
.observeValues { user in
Copy link
Contributor Author

Choose a reason for hiding this comment

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

And it all started because of this πŸ˜„

@dusi dusi marked this pull request as ready for review June 24, 2019 16:45
Copy link
Contributor

@justinswart justinswart left a comment

Choose a reason for hiding this comment

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

Nice, thanks for catching this πŸ‘

Can I just suggest that we delete the values in the test targets rather than set them to empty? Visually it looks like this:

Values as empty Values removed
Screen Shot 2019-06-24 at 10 19 47 AM Screen Shot 2019-06-24 at 10 20 16 AM

Then, can we also delete the 'Any iOS SDK' rows here, I think it's left over from when we once had a tvOS target:

Screen Shot 2019-06-24 at 10 17 23 AM

@dusi dusi requested a review from justinswart June 24, 2019 18:20
Copy link
Contributor

@justinswart justinswart left a comment

Choose a reason for hiding this comment

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

Looks like just this one sneaky code-signing setting is at app target level and not project level.

Screen Shot 2019-06-24 at 11 40 04 AM

There are a couple more in the whole project config that are at the app target level but some of them make sense to be there. I think let's change this one seeing as it's part of a group that we've changed to all be at project level and then let's do a separate audit sometime of all the settings to ensure they're configured and inherited at the right level, what do you think?

@dusi dusi requested a review from justinswart June 24, 2019 21:47
Copy link
Contributor

@justinswart justinswart left a comment

Choose a reason for hiding this comment

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

Thanks for caring!

@dusi dusi merged commit ffa3520 into master Jun 25, 2019
@dusi dusi deleted the zen-out-warnings branch June 25, 2019 04:53
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.

None yet

2 participants