Hacked By Sipahiler

iOS 8 has changed how location services are handled. First, there are two levels of location monitoring now allowed. From the Apple Docs on CLLocationManager:

• kCLAuthorizationStatusAuthorizedAlways
  • This is the exact same as kCLAuthorizationStatusAuthorizedAlways in iOS 7. Your app can register to monitor regions and significant location changes, and it can actually launch itself in response to these events!
• kCLAuthorizationStatusAuthorizedWhenInUse
  • This is new in iOS 8, and it’s a restricted level of authorization that only allows your app to access location services when it’s running in the foreground. It does not allow region monitoring and significant location changes.

Previously, apps could ask the user for authorization by starting to use location services in your app:

self.locationManager = [[CLLocationManager alloc] init];
// This should open an alert that prompts the user, but in iOS 8 it doesn't!
[self.locationManager startUpdatingLocation];

Now, it does nothing.

Here are the steps to getting your app back to its former glory:

1. If your app needs kCLAuthorizationStatusAuthorizedAlways, go to your app’s info.plist and add the NSLocationAlwaysUsageDescription key:  
2. If your app needs kCLAuthorizationStatusAuthorizedWhenInUse, go to your app’s info.plist and add the NSLocationWhenInUseUsageDescription key:
   
3. Add a description to this key that describes why your app is requesting for location services. This is a really good practice to explain to users why they should give you permission. If you don’t provide any context to this, your users will tend to be distrustful of you invading their privacy!
4. In your app, request for permissions:

       // iOS 8 - request location services via requestWhenInUseAuthorization.
       if ([self.locationManager respondsToSelector:@selector(requestWhenInUseAuthorization)]) {
           [self.locationManager requestWhenInUseAuthorization];
       } else {
           // iOS 7 - We can't use requestWhenInUseAuthorization -- we'll get an unknown selector crash!
           // Instead, you just start updating location, and the OS will take care of prompting the user
           // for permissions.
           [self.locationManager startUpdatingLocation];
       }
   

5. Implement the delegate method that alerts you when the user has accepted permissions.

   - (void)locationManager:(CLLocationManager *)manager didChangeAuthorizationStatus:(CLAuthorizationStatus)status
   {
       // We only need to start updating location for iOS 8 -- iOS 7 users should have already
       // started getting location updates
       if (status == kCLAuthorizationStatusAuthorizedAlways ||
           status == kCLAuthorizationStatusAuthorizedWhenInUse) {
           [manager startUpdatingLocation];
       }
   }

The workflow works like this:

• Your app makes a call to requestWhenInUseAuthorization if it’s available (in iOS 8), or it uses the old iOS 7 method to maintain backwards support.
• requestWhenInUseAuthorization displays an alert-style dialog if your app’s info.plist includes the NSLocationWhenInUseDescription or NSLocationAlwaysUsageDescription. The dialog has the text value from the plist. (See Localizing Property List Values to localize your info.plist strings.)
• If the user declines, the CLLocationManager status becomes kCLAuthorizationStatusDenied. If the user accepts, the CLLocationManager status becomes kCLAuthorizationStatusAuthorizedAlways|WhenInUse.
• The CLLocationManagerDelegate receives a message when the status changes, which is a great place to kick off location monitoring. Since the request/accept is asychronous, you can’t start monitoring until you’re certain that the user has accepted.

In Objective-C, a subclasses can override its superclass’s private methods. If you accidentally name a method the same as something in its parent, it will obscure it. This is a very bad thing.

The one killer feature I had in mind with ColorMyWorld was to have it do real-time color analysis: point the video camera at an object, grab a sample swatch from the video frame, find its average color, and display the closest matching color. I never implemented this because the app seemed good enough without it, but the absence of this killer feature gnawed at my soul.

Armed with a few more months of iOS/Obj-C experience, I’ve finally circled back to ColorMyWorld to give it the attention it deserves. It’s been given a big code refactoring, but more importantly, I’ve taken a swing at implementing real-time analysis. That means working with the AVFoundation framework.

It was encouraging to see how quickly I was able to finish the first iteration of the feature. It took me a few hours to get the closest color to print to the debug console, and another few hours to get the camera to display on the screen and to allow the user to lock and unlock the sampling mode by holding their finger to the screen.

At this point, everything was looking pretty darn functional, but there was a problem I expected: rotating the device really messed things up. I expected the camera to rotate when I rotate the device. It didn’t.

To explain what happened, I’ll have to explain what I know about AVFoundation.

With AVFoundation, you set up a session to capture input from the device’s camera or the microphone (AVCaptureSession, AVCaptureDevice, and AVCaptureDeviceInput). You then set up the session with one or more ways to output the captured data (AVCaptureOutput, AVCaptureVideoDataOutput, etc.). The session then uses connections (AVCaptureConnection) to send data from the inputs to its outputs.

To display what the camera sees, you have to use a preview layer. A preview layer is a CALayer subclass that displays the video that the camera input is capturing. You basically create a preview layer, add it as a sublayer to a view, and set it to receive data from the capture session. Pretty basic stuff, only a few lines of code.

The problem is that rotating the view in which the preview layer exists does not rotate the preview layer. There is a deprecated way of rotating the preview layer, but the Apple-approved method is to grab the connection between the session and the preview layer and set its videoOrientation property. Okay, so in your view controller’s viewDidLayoutSubviews method, have it access the preview layer’s connection to its session and set this to the UIDevice’s orientation.

But I discovered something else that was weird: the image output from the camera was oriented differently than it was in the preview layer. My mind was boggled. Why is this happening? I already set the connection to the correct orientation!

Well, there’s a very good explanation for why this is: your AVCaptureSession captures raw data from the camera, but it has a few different ways of outputting that data. One way is to render that data in the preview layer, and another way is to send the data to a buffer that you can read and transform into UIImage instances.

These two things use different connections! That’s why setting the preview layer’s connection to orient the image did not change the image output’s orientation. To do that, you have to access the video data output, get its connection to the session, and change its videoOrientation as well.

And as you can see, I’ve been working with iOS unit testing frameworks XCTest and OCMock.

It does feel a little bit like unit testing is a second-class citizen in iOS, at least compared to Rails. Or maybe I’m trippin’.

I don’t know. I have consciously chosen not to have too entrenched of an opinion about programming topics. There are one million ways to skin a cat, and each way has its pros and cons.