Hacker News Reader

Comment by lucasar | Hacker News Reader

I am an iOS developer and most likely the problem is related to configuration and basic analytics, not "siphoning" app data.

Offending code :

if (restrictiveParams[eventName][@"is_deprecated_event"]) {

        [deprecatedEventSet addObject:eventName];

}

So, the iOS library does not check for nil, and whatever the server is returning does not have the expected content. Lame.

View on HN

Looks like that would've probably been caught if it were written in Swift.

    if (restrictiveParams[eventName] as! [String: Any])["test"] != nil

In Swift, now hopefully you wouldn't write this code but it's not entirely unlikely too. In fact the above Objective-C snippet is one of the few cases where Objective-C's forgiving `nil` behaviour doesn't save you from a crash.

Reply on news.ycombinator.com