Backbutton while SCLAlertView is shown causes zombie views

[deanq]

When you have an alert shown, and the back button is clicked to take the User back to the parent view, the entire view controller stays in memory and never goes away. The way you can test this in simulator is to print a line in your deinit or didReceiveMemoryWarning for the child view. You'll notice that child views that pop back to root without an alert shown will deinit, and a line will not print when you didReceiveMemoryWarning. In contrast, if you have a child view with an alert shown and hit back, you will not see the deinit line and didReceiveMemoryWarning will print a line for that child view.

    deinit {
        NSLog("deinit \(self)")
    }

    override func didReceiveMemoryWarning() {
        super.didReceiveMemoryWarning()
        NSLog("didReceiveMemoryWarning \(self)")
    }

[deanq]

I have a work-around for this, and I'd like to share it in case someone else out there is seeing this problem:

class MyViewController: UIViewController {
    // retainer
    var alertView: SCLAlertView!

    override func viewWillDisappear(animated: Bool) {
        super.viewWillDisappear(animated)

        if alertView != nil && alertView.isViewLoaded() {
            // zombie killer
            alertView.hideView()
            alertView = nil
        }
    }

    // factory-ish
    func getDialog() -> SCLAlertView {
        alertView = SCLAlertView()
        // my uniformed customization below
        alertView.backgroundType = .Blur
        alertView.hideAnimationType = .FadeOut
        alertView.showAnimationType = .FadeIn

        return alertView
    }

    func doingSomethingHere() {
        let dialog = getDialog()

        dialog.addButton("Yes", target: self, selector:"fooBar")
        dialog.addButton("No", target: self, selector: "notfooBar")

        dialog.showInfo(self,
            title: "My Title",
            subTitle: "lorem ipsum",
            closeButtonTitle: "Cancel",
            duration: 0)
    }

}

... let ARC work for you.

[dogo]

@deanq
I have to ask, why you are programming in swift? I think you are using the wrong version, this is the Objective-C version

the Swift version is this one
/~https://github.com/vikmeup/SCLAlertView-Swift

[deanq]

Oh, it works fine on Swift using bridging header file. I’m using Cocoa Pod for my project. Tthe Swift version of this library doesn’t compile yet (it’s a cocoa pod problem). Until that is fixed, I’ll continue to use the objective-c version with a bridging header file.

On Nov 6, 2014, at 4:55 PM, Diogo Autilio notifications@github.com wrote:

@deanq
I have to ask, why are you programming in swift? I think you are using the wrong version of the library, this is the Objective-C version

the Swift version is this one
/~https://github.com/vikmeup/SCLAlertView-Swift

—
Reply to this email directly or view it on GitHub.

[dogo]

Duh! I'm so dumb! hahaha, I'll take a look later on this issue

[dogo]

@deanq
Seems fine here (Tested with a UINavigationController Sample)

Tested with :
iPhone 6 Simulator

iOS 8.1.1
iPhone 5s Real world device :P

Please take a look
https://dl.dropboxusercontent.com/u/12595498/dealloc.mov

[deanq]

I guess it only happens in Swift. Deinit does not get called at all unless I kill the reference. I have updated to the :head build, and it's still a zombie for me.

[dogo]

@deanq May I close this issue? since it is a swift error

[deanq]

Sure. Go ahead.