Hiya,

I've been looking for a nice method chain replacement for messy UIAlertController code for a while, so I gave yours a go! Unfortunately, I've run into a problem the first place I've tried to use it. =[ As part of performing Facebook login, I present a very simple dialog when all else fails as follows:

Alert(title: "Error", message: "Unable to log in using Facebook. Please check your internet connection and try again.")
.showOkay()

This is called as the final part of the async callback chain (when the user has initiated FB login and it fails) and gives me the following error:

Warning: Attempt to present <UIAlertController: 0x7fe3d35df020> on <FBSDKContainerViewController: 0x7fe3d5935af0> whose view is not in the window hierarchy!

I'm guessing that the FBSDKContainer view controller is either being dismissed or isn't the right place to be launching this alert from. I've had a brief look at the logic used to select the controller and it looks sane... but I'm not exactly an expert on this. =/ Not sure where to go from here other than pull it out unless you have any ideas?

Happy to help try and diagnose. I really like the simplicity of your approach.

Kind regards, Andrew

This adds simple convenience methods for adding textfields to a controller. Users can opt for a default textfield, optionally include placeholder text, or optionally configure the textfield for secure text entry.

I can't get the Cancel button to be on the right. I tried switching the order of addAction and I also played around with addAction(String) vs addAction(String, style, handler).

       Alert(title: "Add", message: "test")
                .addTextField(&nameField)
                .addTextField(&descriptionField)
                .addAction("Save", style: .default, handler: { _ in
                    print(nameField.text!)
                    print("Description: ", descriptionField.text!)
                })
                .addAction("Cancel")
                .show()

From Human Interface Guideline: In a two-button alert that proposes a potentially risky action, the button that cancels the action should be on the right (and light-colored). In a two-button alert that proposes a benign action that people are likely to want, the button that cancels the action should be on the left (and dark-colored).

This includes instructions for variations on text field initialization and chaining text fields with other Alert methods. Note: Don't merge this PR until https://github.com/lightningkite/LKAlertController/pull/18 is merged.

What do you think about adding functionality for styling? e.g. adding background color and tint color functionality? I'm not exactly sure what is and is not against the Apple guidelines for alerts.

Adding the required option for addTextField(). This will make the preferredAction action button disabled until there is text input.

Use case: You have an Alert+Textfield to name an object before saving, the name cannot be blank and you don't want to dismiss/reinit an alert to prompt the user for input again.

.addTextField(&nameField, required: true )

Note: only one required field is supported.

OP: Please check variable declarations, I'm new to iOS, feedback appreciated!

Loving this controller!

Can we only enable the "Save" button if the textfield has input? I think it would require exposing the UIAlertViewController's primary action? Is that ok?

Something like:

@discardableResult
    public func addTextField( _ textField: inout UITextField, required: Bool = false) -> Alert {
		var field: UITextField?
		
        alertController.addTextField { [unowned textField] (tf: UITextField!) -> Void in
            tf.text = textField.text
            tf.placeholder = textField.placeholder
            tf.font = textField.font
            tf.textColor = textField.textColor
            tf.isSecureTextEntry = textField.isSecureTextEntry
            tf.keyboardType = textField.keyboardType
            tf.autocapitalizationType = textField.autocapitalizationType
            tf.autocorrectionType = textField.autocorrectionType
            
            field = tf
        }
		
		if let field = field {
			textField = field
		}
        
        if(required){
            NotificationCenter.default.addObserver(forName: NSNotification.Name.UITextFieldTextDidChange, object: textField, queue: OperationQueue.main) { (notification) in
                self.action.isEnabled = field?.text!.length > 0
            }
        }
        
        return self
    }

based off: http://stackoverflow.com/questions/30596851/how-do-i-validate-textfields-in-an-uialertcontroller

After upgrading to Xcode 8.1 (now with Swift 3.0.1) I had to rebuild LKAlertController, so I used carthage update. codesign failed, and it has something to do with the cocoa pod tests.

Here are the relevant lines from the carthage-xcodebuild.xxxxxx.log file:

Signing Identity:     "-"

/usr/bin/codesign --force --sign - --timestamp=none /Users/home/Library/Developer/Xcode/DerivedData/LKAlertController-gfxpomyboovzwidrotfexklagyqa/Build/Products/Release-iphonesimulator/Pods-LKAlertController_Tests/LKAlertController.bundle
/Users/home/Library/Developer/Xcode/DerivedData/LKAlertController-gfxpomyboovzwidrotfexklagyqa/Build/Products/Release-iphonesimulator/Pods-LKAlertController_Tests/LKAlertController.bundle: bundle format unrecognized, invalid, or unsuitable
Command /usr/bin/codesign failed with exit code 1

I think the key here is .../Pods-LKAlertController_Tests/LKAlertController.bundle: bundle format unrecognized, invalid, or unsuitable

I got around this by forking your repo and removing the Pods-LKAlertController_Tests scheme.

If anyone else needs a hot fix, use

github "JamesPerlman/LKAlertController" "patch-1"

in your Cartfile.

I'm not sure how else to get around this, but I didn't spend too much time trying to figure this out.

Am I the only one who uses Carthage and this framework? :P

Significant change on line 287 in method:

public func addTextField(inout textField: UITextField) -> Alert {

to

public func addTextField(_ textField: UITextField) -> Alert {

Why was the textfield inout? From my understanding this only makes sense if you want to modify an Alert's value while it's being displayed?

When trying to invoke addAction on ActionSheet class instance with parameters title, style and handler, Xcode reports:

Ambiguous use of addAction(_:style:handler)

ActionSheet().addAction("Test", style: .Default, handler: { _ in print("Test") }).show()

I've tried to use LKAlertController instance and it works:

LKAlertController(style: .ActionSheet).addAction("Test", style: .Default, handler: { _ in print("Test") }).show()

For example

let action = UIAlertAction(title: "Sort By Month", style: .default) { (action) in } action.isEnabled = false ActionSheet(title: nil, message: nil).addAction(action).addAction("Dismiss").show()