Historical errata for iOS 8 SDK Development

Last paragraph.
“The eye icon only appears when the Playground knows that the object its evaluated has a graphic representation.”
“its evaluated” to be replaced by “it has evaluated” or “it’s evaluated”

Missing verb in last sentence of page.
“Here’s what that looks like if we the buttons for ….”

How about ?
“if we click on the buttons…”

“…and a variety
of tools for making apps look and work well on both iPhone and iPad.” s/b “…and a variety
of tools for making apps look good and work well on both iPhone and iPad.”

Middle of page: “Swift lets us build strings from smaller parts, and uses the sequence \\() to say “evaluate what’s inside the parentheses, and insert that into the string“.”

Should probably have something inside the parens, like [expr] or the like, then “evaluate [expr] inside the parentheses…”

3rd graf of “My First Computer”: “Inevitably, computers got
away writing programs as being the primary user experience…”

word missing? “got away from”?

redundancy: “The ability for apps to send tweets from apps….”

End of first paragraph.
“The initial storyboard is shown looks like the following figure.”

Insert “that” in between “storyboard” and “is shown…”

Paragraph on Align popover.
“constraints that align a views edges… ”

Put the possessive ’s on view as in
"that align a view’s edges

Align popover paragraph.
Coordinate the plural used in the first verb, “align” with the last one “centers”.
I am assuming the subject of both verbs is the plural constraints.

Me bad! The last two issues that I had attributed to page 23 are actually page 34 on PDF. (got mixed up on where to look, top of page page number or PDF page number on top of window).
Sorry about the error, … twice….

The description of filling out the popover for the connection is missing the step to actually click the “Connect” button.

“In PRPViewController.m…” looks like an Objective C reference. Should presumably refer to ViewController.swift.

Add a line to say to click on Connect button inside the popover before returning to standard editor, and dismissing the assistant editor?

Near top of page: “Try clicking the button; it likely shows an error alert saying that no Twitter accounts have been configured, with buttons offering to take you
to Settings or to cancel.” It does not do that. But it does give the “Can’t send tweet.” message in the console.

“Edit the text if desired and then click Send.” s/b “…click Post.”

“The idea is that the UIAppDelegate protocol describes methods that…” I think it s/b UIApplicationDelegate.

“Then click the “Pin” button and add a constraint pinning the distance to the “Top Layout Guide” as 0, which should be…."

I’m not seeing “Top Layout Guide” as an option. The default is “View”.

Setting the constraints for the UIWebView does not seem to work as described and shown. When I make the UIWebView full width, the Pin button shows me to be –16 from the left and –16 from the right, not 0, 0 as printed. If I make the values 0,0, then the UIWebView does not touch the left and right sides of the container.

“The Swift language, along with the Foundation and UIKit frameworks, do
their part to support internationalization….” s/b “does” instead of “do”

When looking at Localizations, the text says that just one file (Main.storyboard) will have localizations, but in fact the project also shows LaunchScreen.xib as having localizations.

“Select Storyboard.main and switch to the Assistant Editor.” s/b Main.storyboard.

“In ViewController.swift, replace the line that assigns tweetVC.message with the following:” should refer instead to the setInitialText method on tweetVC.

“Click on the PragmaticTweetsTests file in either the Project or the Test Navigator.” s/b “the PragmaticTweetsTests.swift file….”

Actual: “Here’s what that looks like if we the buttons for each myLabel, from top to bottom:”

Expected: “Here’s what that looks like if we select the buttons for each myLabel, from top to bottom:”

Actual: ‘In this case, there’s one connection shown in the “Sent Actions” section’

Expected: ‘In this case, there’s one connection shown in the “Sent Events” section’

Actual; “Armed with this class, we’re ready to lay down some code. In
PRPViewController.m, rewrite the handleTweetButtonTapped()”

Expected: “Armed with this class, we’re ready to lay down some code. In
ViewController.swift, rewrite the handleTweetButtonTapped()”

Actual: “The line ends an open curly-brace; any functions and properties between this and the
matching closing curly-brace are part of the class.”

Expected: "The line ends with an open curly-brace; any functions and properties between this and the matching closing curly-brace are part of the class.

Actual: " The idea is that the UIAppDelegate protocol"

Expected: " The idea is that the UIApplicationDelegate protocol"

Inaccuracies for creating the new test file. It’s not File -> New File, it’s File -> New -> File. There is no XCTest to subclass, it’s XCTestCase.

“Swift considers all the classes in the PragmaticTweets to be one module….” There is a missing word after PragmaticTweets. Perhaps “folder” or “target”?

“Start in WebViewTests.swift by adding an import statement….” refers to a non-existent file. I think maybe it s/b PragmaticTweetsTest.swift…?

Disregard erratum #77399. I made a mistake in where I saved WebViewTests.swift.

When we create the new reloadTweets method, the “sender” parameter suddenly disappers. It should remain.

Actual: “Make sure this class is a subclass of XCTest”

Expected: “Make sure this class is a subclass of XCTestCase”

Actual: “So put a public modifier right or after”

Expected: “So put a public modifier right before or after”

In the code to establish cellForRowAtIndexPath `cell.textLabel.text = “Row \\(index.Path.row)”` it seems that cell.textLabel should be unwrapped with the ! modifier.

Missing “t” in extensions in last sentence for the chapter 13 reference.

“Chapter 13, Launching, Backgrounding, and Exensions, …”

very bottom of the page, a semicolon snuck in: self.loadedWebViewExpectation!.fulfill();

“Now, add the line self.reloadTweets() to the viewDidLoad() method.” Since this piece of code is inline in the text, it doesn’t stand out as a line to actually add to the program. Consequently, I missed it, and didn’t find it until my test failed. Might be good to make it consistent with other code snippets.

“Well, there’s a big round Run button,”
The Run button in Xcode 6 is not round anymore.

Same as Issue #77425, about the “t” in Exensions in the title of the chapter reference

The PDF says “in Chapter 13, Launching, Backgrounding, and Exensions, on page 219”, should be Extensions?

Second full paragraph on the page references a PRPViewController class, instead of just ViewController

Bug with app: Modal UserDetail does not dismiss when selecting “Done” after code has been reworked to work as a split view.

“Select the View Controller from the previously existing scene and press J to
delete the old scene. Notice that the table view automatically gets the incoming
arrow from its left side, which indicates it is the app’s initial view controller
(this can also be inspected in the table view controller’s attribute inspector).”

When I deleted the View Controller, XCode did not make the new Table View Controller the default, giving it the arrow into its left side. (And, it should be the incoming arrow to its left side.)

I’m on Xcode 6.0 (6A313)

On line 3 of the example code at the top of the page, I believe there is an ! missing after “(URL: url”. So it should read “(URL: url!)”
[The downloadable code has the !, and won’t compile without it.]

Add // before the " I just finished…." and after to write it in the file Localizable.strings (French) as shown in the downloaded code.

Repetition of the word “method” in first paragraph.

"Every test class that we create will have a setUp() and a tearDown() method method.

Two sentences merged together in the Side note on OCUnit and XCTest

“XCTest is built on top of OCUnit, so anyone already familiar with OCUnit should fine translating from OCUnit to XCTest is simple and straightforward.”

How about?

“XCTest is built on top of OCUnit, so for anyone already familiar with OCUnit, the translation from OCUnit to XCTest should be simple and straightforward.”

or “XCTest being built on top of OCUnit should make it easy for anyone familiar with OCUnit to translate to XCTest.”

Top of this page: “In the “Custom Class” field, enter ViewController. This should auto-complete…."

s/b “In the ”Class" field in the “Custom Class” section…."

Also, the field does not auto-complete.

It looks like all the functions that are overridden on this page also need to be declared as “public”.

It says: Once it does, tap the “Show My Tweets” button.
There’s no button on the screen anymore. Should be “use the Pull to Refresh”, or something like this.

End of paragraph just before “Wrap-Up” .
“(…) please check out the excellent book.”

Missing reference to the book itself.
Jonathan Penn’s book I suppose ? ;-)

There seem to be many errors on this page. At the top: “In the “Custom Class” field, enter ViewController." It looks like you enter ViewController in the Class field of the Custom Class section, and also must enter PragmaticTweets in the Module field.

Numerous compiler errors in the UITableViewController functions added on this page. I fixed them one by one, and lost track of the error messages. Here is the code I wound up with, that does run:

override public func numberOfSectionsInTableView(tableView: UITableView) -> Int {
return 5
}

override public func tableView(_tableView: UITableView, titleForHeaderInSection section: Int) -> String? {
return “Section \\(section)”
}

override public func tableView(_tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
return section + 1;
}

override public func tableView (_tableView: UITableView, cellForRowAtIndexPath indexPath: NSIndexPath) -> UITableViewCell {
let cell = UITableViewCell(style: UITableViewCellStyle.Default, reuseIdentifier: nil)
cell.textLabel?.text = “Row \\(indexPath.row)”
return cell
}

“To create a new class in our project, we use File→New File… (DN)….” s/b File -> New -> File…

There are some stray semicolons in the code at the bottom of the page.

Superfluous figure at the top of the page? Shows an old view of the app; no caption….

“Select the cell, and visit its Attributes Inspector (ED4), and set its style to
“Subtitle”." There are a lot of “cells” being bandied about here, so would help to clarify it as Table View Cell.

“So, in the File Navigator, select the “Pragmatic Tweets” group, go to File→New File…" s/b File -> New -> File…

“Then, in the Identity Inspector (ED3), change its class to the ParsedTweetCell class that we just created.” I think this needs to mention the Module too (PragmaticTweets).

“Within the cell, we can labels, image views, whatever we like…” missing word?

Word “is” in final sentence of first paragraph of Storyboard section should be removed.

In the last paragraph I had to click on the View to see the proxy objects;

The Warning box should be moved to just after the discussion of the sizing bar.

Keyword weak is missing in inserted code shown in book.

Drop the “we” in the 2nd paragraph in the “Swift Structures” comment box.

In the first paragraph of the section “Internationalization” in line 3 the second use of the word “a” should be “of”

On the last paragraph the book tell us to create a group for Root VC, but the image on the next page (#141) show 2 groups (Root VC and Twitter Classes), and a file we didn’t create yet (TwitterAPIRequest). This don’t affect the meaning, but could show just what has been to done to this point.

LaunchScreen.xib also showed up on the slide out sheet described in top paragraph.

In paragraph 2 Storyboard.main should be Main.Storyboard

In the bottom paragraph click Localized instead of OK. Button label has been changed.

Path is now “GeneralLanguage & Region>iPhone Language” instead of “General→International→Language”

“J’ai fini le projet” is not there but “Envoyer Tweet” is there.

overriding viewDidLoad() must be marked as public.

In the box “My First Computer”, paragraph 3, text reads “Inevitably, computers got away writing programs…”. In context, it seems likely that it was meant to read “Inevitably, computers got away from writing programs…”

Paragraph 3 states “Click the ‘eye’ icon next to this”, in reference to the “Math is easy” string. I wish I could upload a screenshot, but with my version of Xcode (Version 6.0.1 (6A317)), the eye does not appear next to the final statement with the math string like it does in Figure 4. However, if I click the eye for the statement above that, myLabel.textColor = UIColor.whiteColor(), then the text in that popup is set to the math string with a white color and a red background.

The whole scenario in Adding a Table View to the Storyboard fails miserably most;y because the starting point is unclear. Do we start with the code from the preceding chapter or start over with a new clean project?

“The JSONObjectWithData()’s third parameter is listed as an NSErrorPointer” Should this be “NSError”?

It would help to be clearer about where this code goes:

if parseError != nil {
return
}

Superfluous semicolon at bottom of page.

“What’s happened? A race condition, actually. When a cell goes offscreen and is queued for reuse, it will eventually get dequeued and filled with new data. But the closure doesn’t know that.”

We’ve got lots of closures in the code now…which closure are we referring to here?

It would help to be explicit as to where the code snippet at the bottom of this page goes.

“For consistency, we want the file name to match its contents, so in the file navigator on the left (D1), select ViewController.swift, click again to edit the line, and change its name to RootViewController.swift”

When attempting to rename the file, I got ‘The document RootViewController.swift’ could not be saved. The file has been changed by another application."

“The first field here is “Custom Class”, which we used before when we were telling the storyboard to use our custom table cell class." Same issue here again with the Custom Class section and the Class and Module fields, as opposed to a Custom Class field.

The navigator diagram at the top of the page does not reflect the state of the project files at this point in time. There has been no Twitter Classes folder created, nor do all the files shown in that group exist yet.

“Move the files for the existing ParsedTweet in here….” s/b “file,” singular

“Choose the iOS →Cocoa Touch → Class template….” s/b iOS -> Source -> Cocoa Touch Class

“Select the “Twitter Classes” croup…." s/b “group”

Superfluous semicolon on line 5 of the code snippet.

“This class has to do with how our app interacts with the rest of the application….” Huh? Don’t app and application mean the same thing? What does this mean?

“Switch to the storyboard and then locate the Navigation Controller in the
Object Library; it looks like a yellow circle with a blue “back” arrow in it, like this:"

Fig 59 does not match this description.

“Under “Triggered Segues”, there’s a connection called “Root View Controller”. s/b “root view controller”

“anyone already familiar with OCUnit should fine translating from OCUnit to XCTest” Should be: find.

I found while following along and writing the tweet button handler, not having SLComposeViewController available and getting build errors (as designed!), my first instinct is to fix that problem… reading on I see that we need to “import Social”, but (perhaps it’s just me) I don’t imagine many people would keep typing while a build error exists.

I’ve seen this pattern in other programming books/tutorials too, and every time I wish the author had just started off by explaining that they following code will require these imports, or - alternatively - just included the import in the first code snippet. I realise the intention is to show what happens when trying to use a class that isn’t imported, but I think we’ll run into that problem enough on our own :)

The text says:

“We saw this in the last chapter when we inspected the project’s build phases and added Social.framework to the frameworks that were already part of the project”

Actually, all I remember doing was “import Social”. I think in Objective C/older versions of XCode you did have to do this. But, you don’t any longer it seems :)

In the Custom Table Cells, first paragraph.

I get ParsedTweetCellTableViewCell as a choice (or UITableViewCell) in the Identity inspector.
The text says “Subclass of:” to UITableViewCell

Please disregard erratum #77511. Me bad ;-)

Beginning of third paragraph.
“The UITableViewController that our PRPViewController subclasses… ”

Should not it be “that our ViewController” simply?

Last paragraph.
“we’re promising to write a method called handleRequest()…”

Do you mean “handleRefresh:” ?

Aside from the compiler warnings already mentioned, it seems that:

• The text doesn’t mention needing to delete the call to reloadTweets from the constructor (although it’s easy enough to figure out)
• The WebViewTests now fail, and since they tested the now deleted web view that whole file could be deleted… not sure if this is done later though!
• A compiler warning is generated because there is no reuse identifier on the table view. I guess it’s OK to ignore for now, but good to be aware of.

“override func viewDidLoad()” needs to be made public - “override public func viewDidLoad()” (XCode provided this correction).

Note: I noticed that I have been referencing the absolute page number instead of the number printed on the page in the PDF. I will use the printed number on the page from now on.

Errant “;” at the end of second to last line of code

“cell.avatarImageView.image = nil;”

Second sentence: putting functionality into a plural? “functionalities”
in
" We’ve swapped different functionality into and out of this view, …"

Second line: replace “croup” by “group”
in
“Select the ”Twitter Classes" croup and do …"

Missing word “Here’s what that looks like if we HIT the buttons for…”

last paragraph: “which is meant to clean up some of the cruft hat has accumulated around C” should be presumably Cruft THAT has…

Missing “i” for the word “with” in method name “performRequestWthHandler()” in the last paragraph.

I would generally recommend putting the figures before the text that explains them. Currently you have to read and remember a lot before the actual screenshot appears oftentimes on the next page.

If you get the screenshot upfront, you tend to understand the written content better, because you can relate it to the things you have seen.

Looks like an ObjectiveC leftover: “In PRPViewController.m, rewrite the handleTweetButtonTapped method. . .”

Just a little “;” at the end of the last line of code of the page
“delegate : self);”
I know it does not hurt and the compiler is happy though. Just fun to see them cropping back up sometimes. They are missed! ;-)

Same as issue # 77430 about then “t” in “Exensions”

Another case where the text says to ‘Run this, tap “Show My Tweets”’ after the button has been removed and replaced with a tableview and pull-to-refresh control. Actually, with the current implementation it fetches the tweets on viewDidLoad, so there’s no need to refresh either.

The semicolon at the end of the println statement isn’t necessary

In the second paragraph you are talkin about adding the Social.framework to the build phases. That didn’t happen in the last chapters. The only thing one can find is the “import Social”.

The text says “In the handleTwitterData() call, change the target from self to delegate,…”. Actually, delegate needs to be unnwrapped, so it should say “change the target from self to delegate!” I think.

function prepareForSegue needs to be declared public.

“…we’re reading to start navigating. “Reading” should be “ready”.

The text says to select the “Parsed Tweet Cell”. It’s still called “CustomTweetCell” (unless I missed changing it earlier?)

Test text says “Drag a Navigation Item icon (shown below) from the Object Library to the new scene.”

Shouldn’t we drag it to the navigation title bar area, specifically? Does it make a difference?

One of the labels and its constraint is “A label called “Real Name” top-aligned to the button,…". We haven’t used an alignment constraint like that before, however I did figure out that you need to select both the label and button and can then add the constraint via the Align popup menu. I might be worthwhile mentioning that.

Page says:

Visit the log navigator using
the rightmost button in the Navigator area toolbar, or just type D8.

It appears to be called the “Report Navigator” in Xcode 6.

Chapter 1 has a section that has you search for “social framework” and clicking on the “Social Framework Reference” result. It then says to scroll down to the class listing and discover that there are just four classes (one of which is supposedly SLComposeViewController).

When I do the search and click on the result, I only see one class in the Class Reference section(the only class I see is SLRequest).

Am I missing something?

When the text asks to “verify everything’s OK”, I ran the app but found it crashed in viewWillAppear(animated:), which was defined on page 166, at the line it calls the super method.

I looked at the linked file in the PDF and the implementation there used viewWillAppear() (although was just a stubbed method). So, I tried using this method instead and it worked.

override func viewDidLoad() {
super.viewDidLoad()
reloadTweetDetails()
}

Hmm, I have no idea why.

Middle of the page. First paragraph of “Using the Storyboard Segue”, second sentence.
“But hold up, how do we know which tweet was selected?”

Did you mean “hold on” as in wait a minute?
I might just not be familiar with that use of “hold up” though ;-)

Second paragraph:
“An unwind method needs to have @IBAction annotation (…), take a UIStoryboardSegue as a parameter, and return nothing.”
First verb is 3rd person singular for the unwind method but “take” and “return” should be too, not plural.

“Top Layout Guide”, meaning we want to lock the distance between the top of our button and the area… should read….“Top Layout Guide”, meaning we want to lock the distance between the top of our label

End of first sentence, continuing from p 193
“However, if we tap one of the tweets, it doesn’t populate the detail view and take it to us.”
Did you mean " and take us to it" ?

Last paragraph, last sentence.
“On a sufficiently large device, the spilt view… ”

split view instead of “spilt view”

At the top of the page, “According to creator, Chris Lattner”. This should probably either read “According to creator Chris Lattner”, dropping the comma, or “According to its creator, Christ Lattner, …”.

Unsure about what “well” means here in the second paragraph, second sentence.
“A well to accept the drop will appear, …”

“Within the cell, we can labels, image views, whatever we like” — you need to add “add”

Second to last paragraph, last sentence: repetition of “to”

“… but we can override to to take some interesting action, ..”
Maybe “override it to take …”

Not an error: just a pleasant surprise. You had guessed what mistake I would make…. I did misspell the segue identifier in the RootViewController.swift, and it did not work, as you just said… ;-) Made my day!

Last paragraph in last sentence before code snippet.

“where we to the rest of our JSON unpacking:”

Replace “to” with “do”

Middle of the page: “when” to be replaced by “then” ?
in
“If this works, when we can assign the …”

Xcode 6.1 shows multiple errors for the tableView(cellForRowAtIndexPath:) function. In the function definition, the ! after the parameter types UITableView and NSIndexPath causes complaints about implicitly unwrapped optional types. Removing the ! from each clears these complaints.

Also, the line:

cell.textLabel.text = “Row \\(indexPath.row)”

shows:
‘UITableViewCell?’ does not have a member named ‘textLabel’

I also tried the downloadable sample code, and it has the same problem, even with .textLabel! instead of .textLabel. If I double-click UITableViewCell and Jump to Definition, it shows that textLabel is defined.

This can be corrected by changing that line to:

cell.text = “Row \\(indexPath.row)”

and changing the return line to:

return cell!

The code then works as shown in the book.

In the TDD section of Chapter 4 (its on page 151 of the .epub version in iBooks):

“Make sure this class is a subclass of XCTest” should be “Make sure this class is a subclass of XCTestCase”

In the Arrays section of Collections, the paragraph after the musicGenres code block, there’s old Array type declaration syntax — “String[]” should be “[String]” in the line:

“..We could make that explicit by making the declaration var musicGenres: String[].”

In the section “Calling Up the SLComposeViewController”, the last line of the first paragraph references “PRPViewController.m” — which should be updated to “ViewController.swift”

One more reference to “PRPViewController” which should just read “ViewController”

Based on later statements, first line of the page should be appending, not assigning:
“musicGenres = 2.99” should be “musicGenres += 2.99”

Xcode 6.1 shows multiple errors for the tableView(cellForRowAtIndexPath:) function. In the function definition, the ! after the parameter types UITableView and NSIndexPath causes complaints about implicitly unwrapped optional types. Removing the ! from each clears these complaints.

Also, the line:

cell.textLabel.text = “Row \\(indexPath.row)”

shows:
‘UITableViewCell?’ does not have a member named ‘textLabel’

I also tried the downloadable sample code, and it has the same problem, even with .textLabel! instead of .textLabel. If I double-click UITableViewCell and Jump to Definition, it shows that textLabel is defined.

This can be corrected by changing that line to:

cell.text = “Row \\(indexPath.row)”

and changing the return line to:

return cell!

The code then works as shown in the book.

[Sorry, I had originally submitted this with the page number from iBooks, then realized that it wasn’t appearing with the other submissions on table views.]

In 1st paragraph of Internationalization “a lot a” should be “a lot of”

In 1st paragraph LaunchScreen.xib showed in addition to Main.storyboard

In paragraph 2 “Storyboard.main” should be “Main.storyboard”

In paragraph 2 navigation through Settings has changed a lot in iOS 8.2. Also French labels have changed

In paragraph 2 of OCUnit and XCTest “should fine translating” should be “should feel fine since translating”

Third full paragraph “XCTest” should be “XCTestCase”

The paragraph about wiring up the “+” button that spans (ebook) pp 162-163 has a number of issues.

1. “there is just a “Triggered Segues action” and a “Sent Actions selector”…actually, there are those two, and “Referencing Outlets” and “Referencing Outlets Collection”

2. “drag from “selector” over to the Root View Controller icon (the yellow ball that now says “Tweets”)“…i don’t see a yellow ball that says ”Tweets"

I must be doing something wrong here. I can’t get the drag of the selector to “activate” anything. Help, anyone?

“When we tap a cell in the list of tweets, we navigate to the new view controller, which we’ll customize to show the details fo the selected tweet.” “fo” -> “for”

In the explanation of the NSBundle method localizedStringForKey:value:table:, the second parameter is referred to as “variable” rather than “value”, and it says we passed it nil, when the figure above shows we pass it an empty string literal. I assume this is all stale text referring to an old objective-C behavior of the API?

“The only attributes we can edit are the Identifier and the Style (which can be “Show”, “Show Detail”, “Present Modally”, etc.)." s/b “…are the Identifier and the Segue….”

“The only attributes we can edit are the Identifier and the Style (which can be “Show”, “Show Detail”, “Present Modally”, etc.). For the identifier, enter showTweetDetailsSegue."

Might be nice to say what the Segue field should be set to, even if it’s the default.

“Then select this group and do File→New →File… to create a new “Cocoa class” file." s/b “…to create a new ”Cocoa Touch Class" file."

“Fix that by selecting the second view controller in the storyboard….”

Naming that controller explicitly might be more robust than calling it the “second” controller.

Bottom of 169, top of 170: “Under “Custom Class”, change the class from UIViewController to TweetDetailViewController (it should auto-complete
as you type)."

It doesn’t auto-complete for me.

Middle of page in code snippet: superfluous semicolon.

In “Designing the Second View Controller,” references to “superview” should possibly be just to “view”? I’m not seeing any way to set for “superview.”

“A label called “User Name” just below it…." might be more clear as, “A label called ”User Name" just below the “Real Name” label…."

MKMapView is called MapKit View in the object library. Probably better to call it that on this page?

MapKit View is not shown in Figure 70, but it should be there.

four overridden functions in ViewController must be declared public otherwise error is thrown.

I’m getting a runtime error after writing the handleTwitterData method:

2014-10-13 12:41:15.632 PragmaticTweets[33640:8169342] Unknown class TweetDetailViewController in Interface Builder file.
2014-10-13 12:41:15.998 PragmaticTweets[33640:8169342] * Terminating app due to uncaught exception ‘NSUnknownKeyException’, reason: ‘[<UIViewController 0x7fdf495bf1b0> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key tweetLocationMapView.’

I think I’ve eliminated a typo as the problem. Will go back and reread the section for anything I missed. In the meantime, if anyone knows that cause of this, I’d love the help! The message seems pretty obscure to me, though there is lots of info in Googleville.

Somewhere around this page, need to note that Custom Class Module for this new controller needs to be set to PragmaticTweets.

Xcode seems to be create the @IBOutlet connections with the “weak” modifier, so might want to change the code snippet to:

IBOutlet weak var userImageButton: UIButton! IBOutlet weak var userRealNameLabel: UILabel!
IBOutlet weak var userScreenNameLabel: UILabel! IBOutlet weak var tweetTextLabel: UILabel!
@IBOutlet weak var tweetLocationMapView: MKMapView!

reloadTweetDetails() is called twice in TweetDetailViewController. Once in the tweetIDString setter (p163). Again in viewWillAppear (p166), This causes the Twitter API to be called twice. I verified this by putting a println in handleTwitterData for TweetDetailViewController. You don’t need them both.

The Cell-reuse section is a little confusing with reuseIdentifiers. When I read it, I thought that the reuseIdentifier represented a single cell. However, the reuseIdentifier is used to represent a type of UITableViewCell and is manage a pool of specific UITableViewCells when reusing it. I thought it would be more correct to explain how that works

cell.textLabel!.text = parsedTweet.tweetText should be cell.textLabel?.text = parsedTweet.text

The map does not work for me. Examining the JSON object returned by Twitter, the “geo” entry is always .

I almost never get a non-blank “geo” response from Twitter. So the map only very rarely shows. I think this is because “geo” is deprecated in the Twitter API (disallowed linked to the dev twitter overview api tweets page goes here) I modified your routine to use the “place”/“bounding_box”/“coordinates” instead and it gets a lot more map responses.

“that group, create a new file, using the iOS “Cocoa Class” template…" s/b “Cocoa Touch Class”

Superfluous comma just past middle of page, on “return” statement.

“That’s something the second view controller will do as it begins the segue.”

It might be better to more specifically identify “the second view controller,” as there is really no order to the view controllers.

“These methods, commonly called unwind methods have to follow a certain signature — they take a UIStoryboardSegue parameter and have return type IBAction….”

But the code for this function (on the top of the next page) doesn’t have a return type at all.

in line 8 of the code example for the new reloadTweets: implementation to use ACAccountStore, the type declaration of the completion closure is still using the old obj-c syntax.

‘(Bool granted, NSError error) -> Void in’ should be
‘(granted: Bool, error: NSError) -> Void in’

Another place where the obj-c type declaration syntax is hanging around.

Line 12 in the code example, in performRequestWithHandler:
‘(NSData data, NSHTTPURLResponse urlResponse, NSError error) -> Void in’ should be
‘(data: NSData, urlResponse: NSHTTPURLResponse, NSError: error) -> Void in’

dispatch_async(dispatch_get_main_queue(), { cell.avatarImageView.image = avatarImage } should be dispatch_async(dispatch_get_main_queue(), { () -> Void in cell.avatarImageView.image = avatarImage }

“Finally, select the split view controller, bring up its attribute inspector ( ED3), and select the “Is Initial View Controller” checkbox."

— option-command-3 should be option-command-4 for the attribute inspector.

“The UIViewController class has an optional property, splitViewController, defined ad “the nearest ancestor …”
— should be “as”

Line 11 of code:

UIImage (data: NSData (contentsOfURL: parsedTweet.userAvatarURL!))

throws error in Xcode 6.1:
Value of optional type ‘NSData?’ not unwrapped; did you mean to use ‘!’ or ‘?’?

and will not build. Xcode suggests following correction:

UIImage (data: NSData (contentsOfURL: parsedTweet.userAvatarURL)

Which compiles but images are not scaled properly.

Unnecessary comma after return statement.

(already reported in B1.0 by another reader).

Both userImageURL and NSData need to be unwrapped (probably an Xcode 6.1 change). So, the last line in the handleTwitterData function should be:

self.userImageView.image = UIImage(data: NSData(contentsOfURL: userImageURL)

Xcode offered an autocomplete for prepareWithSegue with a non-optional UIStoryboardSegue parameter.

I found that either the signature in the book or using the suggested signature (with unwraps for segue removed) both worked.

I’m not sure which is the preferred way to implement it, but I’m guessing Xcode suggested the new preferred way of doing it.

Had to do a Project=>Clean to get this to work on Xcode 6.1.

Got an error in Xcode 6.1 for not having a ! in front of url accepted fixit suggestion.

Name to enter should be “handleShowMyTweetsButtonTapped” instead of “handleShowMyTweetsTapped” paragraph 3 of Calling in to the UIWebView property.

No “Button - ” in Xcode 6.1 simply “Show My Tweets”

first page of chapter 14. 3rd paragraph:
“One of the single biggest favors we can do for ourselves is to become a fast
and efficinet debugger.”
Should read efficient debugger.

Chapter 14. Debugging Apps • 244
The following text appears on a line by itself half way down the page just before Figure 106: Sure. -JCH

Chapter 14. Debugging Apps • 246
Mispelling in 2nd paragraph just before figure 107. “Craete a breakpoint” should read “Create a breakpoint”

In the Simulator it seems to be necessary to set also ‘Application Language’ in the Scheme Settings[1]. Otherwise it won’t work for me.

Simulator Version 8.1 (550.3)

[1] rshankar.com/wp-content/uploads/2014/08/201408071852.jpg

Source:
rshankar.com/internationalization-and-localization-of-apps-in-xcode-6-and-swift/

I think this text is wrong: “Control-click on the user view controller to see its connections. Under “Triggered Segues”, drag from the “Manual” connection ball down to the new user detail scene, as seen in the following figure"

It’s not clear what you mean by “user view controller”. I believe the one you want to control-click is the “Size Class Overriding View Controller”. And that’s what Figure 97 seems to show.

“Drag the “Tweets” up to the right of the surviving navigation controller…." Probably s/b “Drag the ‘Tweets’ Scene….”

“Drag the “Tweets” up to the right of the surviving navigation controller…." Since you don’t say specifically where to drag the Split View Controller into the storyboard, assuming that the reader will drag the Tweets scene “up to the right” is not valid.

“Delete the empty default detail scene.” It might be useful to say, again, “the one attached to the new Split View Controller.”

“So there should be two: the navigation controller that’s in front of our RootViewController, and the TweetDetailViewController.”

Maybe you’re using RootViewController generically speaking, but we just deleted the RootViewController a page or two ago.

“The first step to dealing with starting on the wrong scene is knowing that we’re even in this scenario and that we need to do something. Actually, we can get that by becoming the split view controller’s delegate.”

I found this hard to understand at first reading. I read it as though the “speaker” was the developer, trying to figure out how to debug the problem, but you’re actually speaking “as the code,” saying that “we” (the code) needs to detect that it’s in a particular condition. (At least I think that’s what’s going on here.)

Not sure that I have a suggestion, but if you see what I’m saying, I’m sure you can figure it out!

“Start in RootViewController.swift by appending UISplitViewControllerDelegate to the comma-separated list of protocols in the class declaration." Superfluous "”.

Figure 83, the grey and white box colors are reversed from what is described in the text (which matches what actually appears in Xcode).

Bottom of page: a couple of superfluous semicolons.

“Finally, if our width isn’t big enough for the split view controller go to into side-by-side mode….” s/b “to go into”.

“On a sufficiently large device, the spilt view controller….” s/b “split view controller”.

“…but the gesture recognizer will become a top-level member of the of the scene….” A couple of extra words in there.

“Back in UserDetailViewController.wift….” s/b .swift

“…control drag from the “Done” button to the green Exit Segue button." “green” -> “orange”

“Start by going to the storyboard, going to the last scene….” I prefer explicitly identifying the scene, rather than the generic “last.”

“Bring up the Assistant Editor (the “tuxedo”
toolbar button…." The Assistant Editor button is no longer a tuxedo; it’s now two linked circles.

“Fortunately, we don’t have to use the members of CGAffineTransform directly. In fact, we almost never do.”

Might be a tiny bit more clear to add “here” to the end of the first sentence. As written, the first sentence sounds like a general statement. Then when you read the second sentence, which is definitely a general statement, the first sounds a little odd.

“This connection will call handlePanGesture:() when a pan gesture starts….” Is handlePanGesture:() Objective C syntax? For Swift, maybe just handlePanGesture?

The code line:
@IBOutlet var twitterWebView : UIWebView!

should read:
@IBOutlet weak var twitterWebView: UIWebView!

as the text states:
the “Storage” says “Weak”

It’s not stated in the text exactly where the third code snippet on this page (the one starting with “if sender.state UIGestureRecognizerState.Began || sender.state UIGestureRecognizerState.Changed {”) goes in the code. Presumably it comes immediately after the previous snippet, but this wasn’t clear (to me).

Very bottom of the page: “…and switch the type from id to UITapGestureRecognizer.” s/b, “…and switch the type from AnyObject to UITapGestureRecognizer.”

The Identity Transform

The code in this section works fine and makes sense, but the motivation set up in the text seems odd. I’m not sure how I would be able to drag the image off the screen. I couldn’t do it. And if I dragged it off the screen, how then would I be able to double-tap it?

When we delete the image view, we lose our constraint for the Done button. It might be worth at least a mention that we’ll have to fix that.

“Control-click on the user view controller to see its connections.” I think you meant the Size Class Overriding View Controller.

After entering the pragtweets: URL in Safari, the simulator took me directly to (the correct scene in) our app. IOW, it did not give the confirm dialog as to whether or not it should open our app.

“Use the x-button to delete the existing unwind segue, then control-drag from the button to the orange “Exit”
icon in the title bar atop the scene…."

I suggest, for clarity, “Use the x-button to delete the existing unwind segue, close the connections popup, then control-drag from the button to the orange “Exit” icon in the title bar atop the scene…."

After “installing” the new keyboard, the globe does not appear by the spacebar for me.

Seconded Stephen P Crozier’s comment about not knowing where the third code snippet on the page (although he labeled it 216, but it’s really 210) should go. I looked at the linked file online to figure it out. Without stating it, it seems like you’re editing the if condition from the previous snippet.

“Go to Xcode→Preferences or enter [command symbol], to access the Preferences window.” I’m not sure what enter [command symbol] means.

Lastly, go into the drop-down menu and select
“Active Window.” s/b “active window.”

The test says to “use its view controller icon in the scene list to give it a unique name to keep things straight (like “User Detail from URL Scene”)." I can’t find any way to change the scene name from “Use Scene” to anything else.

Seconded Stephen’s issue (his page 236) - Keyboard isn’t showing up in the list of keyboards after adding it in Settings.

Kindle location 2271: Code example says to use NSURL.URLWithString() - as far as I can tell this method doesn’t appear to exist, and instead I had to use NSURL (string: "blah").

Kindle loc. 2758 - Instructs the reader to create the ‘Twitter Classes’ group and move the ParsedTweet class into it, when these instructions are already given shortly before.

The word “parentheses” was mistakenly written in the book as “parnetheses”

Full context: “evaluate that expression inside the parnetheses, and insert that into the string“

I had great difficulty getting French to work in Xcode 6.1. Changing the local from the setting app caused crashes. In the end I created a new scheme and set the Application Language to French in the Options pane of the Scheme Editing dialog.

When declaring an NSURL (string: “”) xcode shows an error and suggests “value optional type NSURL? is not unwrapped, do you want ? or !”. Modified to NSURL (string: “”)! to fix the error2203

I don’t know if this is technical error or not but in the eighth paragraph it says that the editor button is a tuxedo but now it is interlocking circles.

6th paragraph it should be intertwined circles not tuxedo for editor x4

The assistant editor icon no longer looks like a tuxedo. It’s now more like a Venn diagram

The instructions on p89,90 are incomplete as follows:
delete self.reloadTweets() from viewDidLoad()
delete the entire reloadTweets function.
The ‘tableView:’, not ‘_tableView’ should be first the parameter for tableView(tileForHeaderInSection:), tableView(numberOfRowsInSection:) and tableView(cellForRowAtIndexPath:). (Just use CodeSense.)
testAutomaticWebLoad() must be deleted from WebViewTests.swift.

I am using XCode 6.1(6A1052d)

On page 97 we call reloadTweets(), but earlier on page 78 we call self.reloadTweets(). Both seem to work. Why one versus the other?

cell.textLabel!.text = parsedTweet.userName fails to build, should be cell.textLabel.text = parsedTweet.userName

I’m using Xcode Version 6.1 (6A1052d)

‘(Bool granted, NSError error) -> Void in’ should be
‘(granted: Bool, error: NSError?)’; NSError must be optional

NSURL.URLWithString(…) doesn’t seem to exist. The affect line should be:
let twitterAPIURL = NSURL (string: "'the url -hyperlinks are not allowed in errata")

I am using Xcode 6.1

Bullet item states “third party code no longer behaviors” should be “third party code no longer behaves”

Code in “Parsing the Twitter Response” won’t build. This works in Xcode 6.1:
func handleTwitterData(data: NSData!, urlResponse: NSHTTPURLResponse!, error: NSError!){
if let validData = data {
var parseError : NSErrorPointer = nil
if let jsonObject : AnyObject = NSJSONSerialization.JSONObjectWithData(validData, options: NSJSONReadingOptions.allZeros, error: parseError){
println(“JSON error: \\(parseError)\
JSON response:\\(jsonObject)”)
} else if parseError != nil {
println(“JSON error: \\(parseError)”)
}
} else {
println(“handleTwitterData received no data”)
}
}

Please disregard, my erratum for ‘Parsing the Twitter Response’. The code works as it appears.

Missing the period on end of the first paragraph of the Introduction (“…just because it’s there”).

‘create a new “Cocoa class” file’ should be ‘create a new “Cocoa Touch class” file’

In the final paragraph it should be “Localize…” button not “Localized…”

In the final paragraph it should be “Localize…” button not “Localized…”

The button for the Assistant Editor no longer looks like a tuxedo, but instead like some interlocking circles.

(The same “tuxedo” comment appears on three other pages as well: 57, 210, and 239.)

The Twitter API URL is listed two different ways:

+ in list above code: …/statuses/user_timeline.json

+ in code: …/statuses/home_timeline.json

On lines 12 and 13 of the code sample appears this closure:

{
(NSData data, NSHTTPURLResponse urlResponse, NSError error) -> Void in
self.handleTwitterData(data, urlResponse: urlResponse, error: error)
}

What about just using this instead?:

{ self.handleTwitterData }

In the code sample for creating the `parsedTweets` array, how about using `map` instead of a `for` loop?

parsedTweets = jsonArray.map { (tweetDict) -> ParsedTweet in
let userDict = tweetDict[“user”] as NSDictionary
return ParsedTweet(
tweetText: tweetDict[“text”] as String?,
userName: userDict[“name”] as String?,
createdAt: tweetDict[“created_at”] as String?,
userAvatarURL: NSURL (string: userDict["profile_image_url"] as String!))
}

In the section “Building Our Own Delegate”, we define a protocol with a single method signature. I’m left wondering what advantages there may be in [1] defining a delegate and passing an object reference and [2] passing in a closure with the proper type signature.

I’m not suggesting that the text is wrong to explore delegates, but because my natural inclination is to prefer simple functions over (unnecessary) object wrappers around functions, I’d love some discussion in the book as to how to choose one pattern over the other.

In second code sample on the page, there’s a superfluous comma at end of final statement.

“but we can override to [sic] to take some interesting action”

For Array and Dictionary type declarations, we can use a terser syntax:

Instead of:
Array<Dictionary<String, AnyObject>>

We can write:
[ [String:AnyObject] ]

In the OCUnit and XCTest box, The text references XCTFail in the first sentence and again in the third paragraph and implies that we have seen it before, but in this version of the book, we have not.

line 7 of code sample has a superfluous ‘;’

In the code example which runs off the bottom of the page, how about using a “if let” to unwrap the `tweetIdString` Option? That way, you can’t obviate the need for a ‘!’ later.

“With the Storyboard showing in the Editor area, go up to the toolbar and click the Assistant Editor button, which looks like a tuxedo.”

In the latest XCode the Assistant Editor button has two overlapping circles, and not a tuxedo.

The following typo (we) should be changed from:

Eventually, we’ll we have an app that looks and feels like a real Twitter client.
—-

To:

Eventually, we’ll (or we will) have an app that looks and feels like a real Twitter client.
—-

In the phrase “control-drag down to the orange box”, rather than “down”, I’d say “up”, since you’re going up the screen.

Substitute “println()” in place of “NSLog()”.

When creating the custom table cell the menu option should be FileNew>File…

When I run the code from the previous page and delete the twitterWebView declaration, I get a build error in WebViewTests.swift: “ViewController does not have a member named twitterWebView”. I get this even if I use Product|Build For|Running.
I think this is new to XCode 6.1.1. I am running through Beta 3 from the beginning on a fresh project.

XCode wants “cell.textLabel.text = parsedTweet.tweetText” to be “cell.textLabel?.text = parsedTweet.tweetText”. I presume this is because cell.TextLabel is a String?.

Xcode wants “cell.textLabel.text = parsedTweet.useName” to be “cell.textLabel?.text = parsedTweet.useName”. I also notice that if I change “cell.detailtextLabel!.text = parserTweet.tweetText” to “cell.detailtextLabel?.text = parserTweet.tweetText” everything still works.

dequeueReusableCellWithIdentifier(“CustomTweetCell”) should be dequeueReusableCellWithIdentifier(“ParsedTweetCell”). Figure 49 should also be updated.

typealias is repeated

for the IBAction of the Tweet button, it says the name should be “handleTweetButtonTapped()”. The action name should not have parentheses, should be “handlTweetButtonTapped”.

I think that "request.performRequestWithHandler ( {

- (NSData data, NSHTTPURLResponse urlResponse, NSError error) -> Void" should be request.performRequestWithHandler ( {
- (data: NSData!, urlResponse: NSHTTPURLResponse!, error: NSError!) -> Void

Array walking code lines 6 and 8 produce errors" “NSDictionary? does not have a member named ‘subscript’. Resolved this with ! operator, like so: useDict![”name“] and userDict![”profile_image_url"].

The following text is obsolete: “At first our table contains the three dummy values from before, then we see
in the Xcode window as the app logs the raw JSON and its array-of-dictionaries representation. And then it just sits there.” The code was removed on p127

The following instruction does not appear to be valid for my version of Xcode (Version 6.1.1 (6A2008a)):

Select the “Table View Cell”, visit its Attributes Inspector (Option+Command+4), and set its
style to “Subtitle”.
—-

The style “Subtitle” does not appear as an option. I only see two options: (1) Plain and (2) Grouped. Should “Subtitle” be another option, or am I not looking in the correction place?

Additionally, the instruction that follows:

Then, for the “Identifier”, we need a string value that we
can use to fetch this cell from our code. Let’s use “UserAndTweetCell”.
—-

There is no “Identifier” in the Attribute Inspector. Am I missing something?

The app starts with the detail view showing default text. Perhaps it show the first tweet or you could indicate how this is resolved later.

Also, minor item maybe to be left as an exercise for the reader. I’ve been entering the code changes from the start of B3. At this point the app still displays a section header (“Section 1”) which can be fixed by returning nil from RootViewController’s tableView(titleForHeaderInSection:) or deleting it.

On lines two and three of prepareForSegue, “segue!.identifier” should be “segue.identifier”. The current version produces the error: “Operand of postfix ‘!’ should have optional type: type is UIStoryboardSegue”.

para 2, “@class” should be “class”.

Line 8 should read
(Bool granted, NSError error)
not
(granted: Bool, error: NSError)
to stop a compiler error with Xcode 6.1.1

line should read
(Bool granted, NSError eror)
not
(granted Bool, error: NSError)
to stop Xcode 6.1.1 compiler error

I was briefly confused by “Select the tap gesture recognizer icon from the scene’s object list or the title bar under the scene”. In Interface Builder Help: Building User Interfaces, Apple refers to this as the “scene bar at the top of the scene”.

Inconsitent method name: In the code you have “@IBAction func unwindToSizeClassOverridingVC (segue: UIStoryboardSegue) {}”; in para 4, the method name is “unwindToSizeClassOverrideVC()”. I prefer the latter.

Page 113 says “enter a height of 100” but page 115 says to set the height to 125. I assume that page 113 should say 125.

Here we “Name the file KeyboardViewControllerStoryboard.storyboard”. On page 235 we set property list value NSExtensionMainStoryboard to PragmaticTweepsKeyboard.

cell.textLabel.text = “@\\(self.tweepNames[indexPath.row])” causes error “‘UILabel?’ does not have member named text. Change to ”cell.textLabel.text" to “cell.textLabel?.text”

There is a discrepancy in the code in figure 106 and the code in RootViewController. “let jsonString…” is in TweetDetailViewController and UserDetailViewController, but not in RootViewController. This remark also applies to figure 109 on p250 and to “Dead Objects Tell No Tales” on p255.
In general I found this chapter useful easy to follow.

Figure 116 “Show tab named Console in active window” differs from the text on p258 ‘In the text box, name it something appropriate, like “Debugging.” ’

Figure 116 “Show tab named Console in active window” differs from the text on p258 ‘In the text box, name it something appropriate, like “Debugging.” ’

The description and image of the “Container View” icon in the object library is incorrect, both describe/show the “View” object instead.

The container view icon is a grey box inside a white box inside a grey box.

I presume “we see see our changes” is not intentional.

Also, the “2 times” label is not showing up on Xcode 6.1.1

Twitter has changed the url for the new user “egg” icon. I had to use

aitchteeteepeeess:abs.twimg.com/sticky/default_profile_images/default_profile_6_normal.png

It would probably be better if the book didn’t depend on the “kindness of strangers” and used urls that pragprog rather than a 3rd party had control over.

In the third code block, the twiterParams are incorrect. The twitter api requires both user_id and screen_name parameters, although it allows the value of the screen name to be used as the user_id

So
let twitterParams = [“screen_name” : screenName!]

should be
let twitterParams = [“screen_name” : screenName!, “user_id” : screenName!]

the array contains at least Twitter account
->
the array contains at least one Twitter account

request.performRequestWithHandler ( {
(NSData data, NSHTTPURLResponse urlResponse, NSError error) -> Void in self.handleTwitterData(data, urlResponse: urlResponse, error: error)
})

can be written simpler as:

request.performRequestWithHandle(self.handleTwitterData)

var parsedTweets : Array = []
can be written shorter as:
var parsedTweets : [ParsedTweet] = []

In fact, take out the println()s… these were removed on P135 (pdf)

The closure format shown on page 116 was refusing to compile. I finally found a more terse syntax which worked properly:

cl.ly/image/27113i1I3L1G

This form doesn’t let me add links, but just an http.

P.S. This book is amazing!

The following compilation error is produced:
—-
Extra argument ‘completion’ in call
—-

Due to this block of code in the text:

1 func reloadTweets() {

- let accountStore = ACAccountStore()

- let twitterAccountType = accountStore.accountTypeWithAccountTypeIdentifier(

- ACAccountTypeIdentifierTwitter)
5 accountStore.requestAccessToAccountsWithType(twitterAccountType,

- options: nil,

- completion: {

- (granted: Bool, error: NSError) -> Void in

- if (!granted) {
10 println (“account access not granted”)

- } else {

- println (“account access granted”)

- }
- })
15 }
—-

The error is resolved, by modifying line: 8 to read:

- (granted: Bool, error: NSError!) -> Void in
—-

Forced unwrapping NSError resolved the error.

In “One thing we don’t see here is how the gesture recognizer is related to the image view. For that, go to the connections inspector (Alt-Cmd-7). ”

It should be Alt-Cmd-6

Sorry too lazy to figure out how to use the graphics for alt and 7 here

The photo is wrong! The TARDIS is supposed to be bigger in the inside!

Sorry, couldn’t resist.

After adding constraints to the link just like I did with the label, I didn’t get a blue box, still stayed orange indicating I need another constraint.

I’m using Version 6.1.1 (6A2008a) OSX 10.10.1 (14B25)

When starting to collapse and restore split views the RootViewController’s tableView(didSelectRowAtIndexPath:) breaks down. Suddenly there are cases with two view controllers where the second one is NOT a navigation controller and since that is the assumption in the code the selection is never handled and the app stops responding until the device is rotated.

You could perhaps mention that “() -> Void in” is superfluous at the start of a closure so that all the calls to dispatch_async can be simplified. For example,

dispatch_async(dispatch_get_main_queue(), {
() -> Void in
self.tableView.reloadData()
})

becomes

dispatch_async(dispatch_get_main_queue(), {
self.tableView.reloadData()
})

A small matter but I find that it improves readability.

Copy and paste of the WebViewTest.swift gives me an error in the compiler: “Use of undeclared type of ViewController”.

I think you need to add a step in the view controller where you include the target tests

Maybe you could explain that the name of an enum can be omitted when referring to one of its values so that

if sender.state UIGestureRecognizerState.Began || sender.state UIGestureRecognizerState.Changed {

becomes

if sender.state .Began || sender.state .Changed {

I find that the latter exposes the intent far better than the former.

“The careful proportioning of responsibilities between the view class and the controller …”
How about changing “proportioning” to “apportionment”?

“Since we want to send a tweet, we can enter twitter as the
search term, and we’ll find a whole “Twitter Framework
Reference”. Tempting, but take it from us that that’s old
news — it was a Twitter-only framework for iOS 5 that has
been supplanted by a new framework that works with multiple
social networks."

This tells the reader that the docs are not helpful for
finding the best framework. It would be be nice to have
some guidance as to find appropriate frameworks in future.
How should we do it? Google? Buy a recent book of recipes?
Email the authors of this book?

The text instructs: “Run this, tap “Show My Tweets” and check the console at the bottom of the Xcode window" but we no longer have a “Show My Tweets” to tap.

Suggested correction:

“Run this and check the console at the bottom of the Xcode window.”

I tried the code but got an error.
This seems to fix it:
stackoverflow.com/questions/25964901/6-0-1-and-table-changes-uilabel-does-not-have-a-member-named-text

As above, cell.textLabel.text = parsedTweet.userName gives an error
but putting in an ! seems to clear the error
cell.textLabel!.text = parsedTweet.userName

In the sentence:

change the URL it uses, like this:
Debugging/PragmaticTweets-14-1/PragmaticTweets/RootViewController.swift
let twitterAPIURL = NSURL.URLWithString(

Error message: ‘URLWithString’ is unavailable: use object construction ‘NSURL (string:)’

the original code was:
let twitterAPIURL = NSURL(string:

It might be worth mentioning setting the active schema back to PragmaticTweets from PragmaticTweepsKeyboard to prevent questions on why are breakpoints not working.

Sorry all my page references are from the Mac Preview app page numbering and not the page number printed top right corner. Here are the corrections:
139 = 131
249 = 246
254 = 251

When describing the transformations for two-sided print the scaling is said to be 50. This would allow four pages on one sheet. For A4 paper the factor is 1/sqrt(2) or about 71. I’m sure for letter size it is similar.

In transformations if a, b, c, and d are all set to the same value the result is NOT a scaling. For an aspect preserving scale a and b need to be equal and c and d must be 0.

Here too the identity transformation matrix should be a=b=1, c=d=0, tx=ty=0. If c and/or d had a value of 1 the transform would include some amount of rotation/stretching.

In ‘Dead Objects Tell No Tails’, you write:
For example, continue after the breakpoint, then set the breakpoint right after the line let jsonString = NSString (data: data, encoding:NSUTF8StringEncoding). Now pull-to-refresh to hit the breakpoint again.

this line does not exist, instead you could ask them to expand data and right click on _bytes which will produce the result you are looking for.

jsonString only exists in the detail views

The final paragraph of the App Lifecycle section states:

“If our app is backgrounded long enough, it will eventually be terminated. We’ll get this message via the app delegate’s applicationWillTerminate() method. If our app needed to save data for the next time it’s launched, this would be our last chance to do so.”

As far as I understand it, that’s not always the case. When an app is backgrounded, the OS can silently move it into a suspended state and then terminate it which will not call applicationWillTerminate(). It may be worth mentioning that in case people become confused about that function not always getting called.

“One other thing to watch for is orange markers indicating that an object it not in its correct position. ”

Thinking this should be: s/it not in/is not in/

presentViewController vs self.presentViewController: page 76 has the former, page 77 describes the latter and figure 20 shows the self prefix in the screenshot.

“Select Storyboard.main and again switch to the Assistant Editor.” should (perhaps?) be “Select Main.storyboard …”

‘click the “Localized…” button’ should be ‘click the “Localize…” button’ (omit the ‘d’). It’s correct a few sentences later. [Note, unlike my earlier reports where the pagenum was erroneously taken from the (variable) epub, this page number is from the pdf]

Tap “J’ai fini le projet” should be Tap “Envoyer Tweet”.

“As we saw earlier, the method in XCTest to assert a failure is XCTFail” - except that we haven’t seen XCTFail at all yet…

“Finally, if canSendTweet() returned false”

A `canSendTweet()` function is never defined and used in `
UserInterface/PragmaticTweets-2-1/PragmaticTweets/ViewController.swift`.

“We connected an outlet from the code to the UILabel in the storyboard…”

This task never happens in chapter 2.

“…Swift lets us chain the results of one statement as parameters to another…”

This is better described as function composition rather than [method] chaining.

Switch old GCD constants (DISPATCH_QUEUE_PRIORITY_DEFAULT) to new QOS constants (QOS_CLASS_DEFAULT).

You have:

Our first commit has set up the Git repository with initial versions of all the project files. Let’s make a change and see what that looks like.

At this point you have not checked out the project from git…

This page references TN2250 which is now “retired”. It appears to be superseded by TN2407.

Re the following text, is this really a “logic error” or rather a poor “business rule”? Those are different.

“Unit tests also expose logic errors in our code. In the Jurassic Park example, the code being run had a logic error that prevented the scientists from discov- ering the problem until it was too late.”

unintended use of semicolons… Swift can handle semicolons just fine so the code will run but I am sure the author did not intend on including them.

Repeated statement.

From Top of page 89 (after code block):

"Also, go ahead and delete the titleForHeaderInSection() method; we’ll only have a single section from here on, so the title is superfluous.

In this new version, we have a single section (and therefore can eliminate the entire tableView(titleForHeaderInSection) method), and the number…"

As of Xcode 6.3 (6D554n), Xcode complains about this line:

let cell = tableView.dequeueReusableCellWithIdentifier(“UserAndTweetCell”) as UITableViewCell

xcode suggests:

let cell = tableView.dequeueReusableCellWithIdentifier(“UserAndTweetCell”) as! UITableViewCell

The code presented here isn’t quite what we did in the previous chapter. Specifically, it adds in the optional prefixing “self” on ln6, which wasn’t in the chapter 2 sample code. Since it then goes on to say it’s not necessary and we won’t be doing it in future, it’s pretty much a wash, but it does tell us not to do something we weren’t doing in the first place

Seems like twitter has changed the default profile image urls. The provided one doesn’t work for me, but the ones in the twitter dev best practices still do. PragProg won’t let me paste a URL here.

Segue unwinding <>

Silly me. I chased this for 15 minutes because in my simpleton mind, I assumed that the unwind functionality for the UserDetailViewController would live in the — well: UserDetailViewController class (especially when seeing the drag within the context of the User Detail View Controller of the storyboard). After actually reading the book and cruising through the Apple Documentation, I found that it needs to be in the TweetDetailViewController (not entirely self evident to us novices).

Suggestion: emphasize in the text that it goes in the TweetDetailViewController — perhaps even has Joe Ask “Why does it belong in the TweetDetailViewController and not in the UserDetailViewController?” (he’s a pretty smart guy)

Sentence at middle of page:

But to show how flexible gesture recognizers, we’ll do functionally the same thing by giving the existing image view the ability to handle taps, thereby turning it into a de facto image button.

needs grammar correction:

But to show how flexible gesture recognizers are, …

or, perhaps:

But to show the flexibility of gesture recognizers, …

Nit: Yes, I know it should be obvious by now, but…

In the second sentence of the first full paragraph on the page, you tell us noobs to “Run the app” so we can jump into the debugger. Yes, you’ve implicitly changed the context by having us edit the RootViewController, and yes, that is NOT part of the keyboard extension that we were working in the last chapter, but…

I suggest that you put in a reminder to switch context back to “Pragmatic Tweets” so fools like me who are powering through the book like someone lost in the desert getting his/her first drink of water after a few days wandering won’t wonder why the keyboard extension came up. :)

Second paragraph from the bottom, first line reads (“D” below is the command key symbol as translated by copy/paste from Preview into this text box):

Go to Xcode→Preferences or press D to access the Preferences window.

I think you mean to bring up Preferences.

Last paragraph on page opens with:

Prior to running, let’s take a look at how all these app-signing pieces have come together. Click the project icon in the project window, select the Prag- maticTweets target, and choose the Build Settings tab.

::woof:: took a bit to grok what you meant by “project window”. You might try:

Prior to running, let’s take a look at how all these app-signing pieces have come together. In the Project Navigation window (<1>), select eh Pragmatic Tweets target, and choose the Build Settings tab.

“go up to the toolbar and click the Assistant Editor button, which looks like two linked circles”

The Assistant Editor icon no longer looks like two linked circles. It looks like the front jacket of a butler (“the smart assistant”?)

Just to be sure, I got curious and verified that it used to look like two linked circles, but no longer does, by checking some Google images of the old Xcode.

Please ignore the report for #78465 - after updating to the latest Xcode, it now has 2 circles instead of the “valet” icon.

There is no such statement in my ViewController.swift file:
if parsedTweet.userAvatarURL != nil

The page number is the Kindle location number. “Calling Up the SLComposeViewController” - I discovered that you need to add “import Social” in order to get the code to work.

In the section titled “Implementing the Next Keyboard Button”, the second sentence incorrectly refers to “KeyboardViewControllerStoryboard.storyboard”.
The correct name is “PragmaticTweepsKeyboard.storyboard”.

In Chapter 1, Xcode Playgrounds section, this paragraph is no longer the case:

“This makes the evaluation pane update again, but it just says “(2 times).” That tells us that it has executed these two lines of code. But it doesn’t give us a preview of the result, because evaluating these lines doesn’t give a different result for myLabel. We haven’t replaced myLabel; we’ve just changed what it looks like.”

Rather than showing “(2 lines)”, it does now show each individual line with the ‘Quick Look’ eye icon and also the ‘Result’ dot icon. (This is in Xcode Version 7.1.1 (7B1005), on El Capitan 10.11.1).

Please disregard previous errata I submitted, I put the wrong PDF page number. It should be page 4 of the PDF, not page 22.

In Chapter 1, Xcode Playgrounds section, this paragraph is no longer the case:

“This makes the evaluation pane update again, but it just says “(2 times).” That tells us that it has executed these two lines of code. But it doesn’t give us a preview of the result, because evaluating these lines doesn’t give a different result for myLabel. We haven’t replaced myLabel; we’ve just changed what it looks like.”

Rather than showing “(2 lines)”, it does now show each individual line with the ‘Quick Look’ eye icon and also the ‘Result’ dot icon. (This is in Xcode Version 7.1.1 (7B1005), on El Capitan 10.11.1).—Steve Holland

In the Coding the App - Logging section, the code example uses:

println (“handleTweetButtonTapped”)

In Xcode Version 7.1.1 (7B1005), this function has been renamed to ‘print’, so the example should now be:

print (“handleTweetButtonTapped”)