Not sure what's causing this one. Reloading the Table View brings back the classes, but it definitely needs to be fixed.

My hunch is that TSAuthenticatedReader is somehow getting deallocated / released, because I'm not sure what the retain / release life cycle is for global variables.

Why does it have to run the login-check on the main thread? I feel like there was a reason but it doesn't seem like that's how it should be.

Investigate alternatives, specifically using the TSNetworkQueue instead of the main thread.

don't let me steal it

Storing usernames and passwords in NSUserDefaults is a really, really bad idea, even if you're encrypting them: https://www.andyibanez.com/nsuserdefaults-not-for-sensitive-data/. You should always store credentials in the iOS keychain instead.

All data stored in NSUserDefaults is saved in plain text, which makes it really easy for an attacker to retrieve the info they need to get a user's credentials. And while encrypting the passwords yourself might seem like a good idea, it gets bad quickly when the inputs used to encrypt and decrypt this data are readily accessible:
Key: Cal<3sEncryption
IV: TrustMePlsssssss

This is why letting iOS handle these things is a good idea.