Troubleshooting Xcode is a handbook for software developers of all levels creating applications for iOS and OS X using both Objective-C and Swift.
If you’ve struggled in the past to make Xcode work as expected, to solve problems that defy logic, and to understand Xcode’s misleading or cryptic error messages and unexpected crashes, Troubleshooting Xcode is for you.
Troubleshooting Xcode is great for the developer wanting to extend his or her knowledge about obscure problems and limitations involving the use of Xcode, Objective-C, and Swift as well as how to use automation to increase productivity and make some repetitive tasks easier.
WHAT YOU’LL LEARN
- Learn about some classical bugs and limitations of iOS, OS X, and Xcode and how to solve or avoid them.
- Know when you should never use Storyboards for your OS X application.
- Discover several workarounds you can use to bypass some of the hardest problems you may face.
- Know how to use scripts to automate repetitive tasks like the creation of in- app purchase packages or icons for your application.
- Understand how you can create images that are better compressed and smaller.
- Learn how to avoid falling into common pitfalls.
- Learn how to use C to workaround some Objective-C limitations.
WHO THIS BOOK IS FOR
iOS and OS X developers who need to troubleshoot problems and limitations with Xcode. Developers with all levels of experience will find helpful information in Troubleshooting Xcode.
TABLE OF CONTENTS
- Xcode crashing when opening a project file
- The identity used to sign the executable is invalid
- Xcode fails to compile and blames “SBPartialInfo”
- No matching provisioning profiles found
- Compressing images better than Photoshop
- Creating packages for in-app purchases
- Reduce up to 75% of the compiling time
- Declaring impossible “constants” in Objective-C
- Concurrency with Core Data
- Creating icons for your apps from Terminal
- UINavigationBar tint not working
- Debugging an insanely hard Quartz error
- Adding objects to a mutable array concurrently
- The app is damaged and can’t be opened
- Application failing to obtain a receipt
- Classes with the same name on different targets
- A case against Base Internationalization
- Checking for missing Localizable.strings
- You are declaring your NSString wrong
- CocoaPods: /Manifest.lock: No such file or directory
- Asset Catalogs bug
- App crashing without giving you clues
- NSUserDefaults not working for a sandboxed app
- Interface elements not updating
- Find and replace using regex
- Extracting a dictionary from an array
- Magical way of counting elements on an array
- OS X app not launching with the correct size
- Detecting the application target
- Disabling a method
- Deprecating a method
- Xcode “beachballs” when opening a project
- UIButton not grayed out
- Catching memory corruption
- SpriteKit crashing on didBeginContact:
- SpriteKit object not respecting boundaries
- A case against using Storyboards for Cocoa apps
- UIView Classes with independent rounded corners
- Making NSViews compatible with UIViews
- Detect with the UIPickerView stops spinning
- “Insane” NSDates
- Localizing the application name
- Centering views horizontally with Auto Layout
- Elements grayed out on Storyboard after copying
- Debugging Core Data
- “The package does not contain an Info.plist”
- Check the version of an app on the App Store
- Power tips: Beyond Xcode
|BUY ON AMAZON||BUY ON APRESS||BUY ON B&N|