This was occuring if a title has no properties set initially, but then are configured later. The title image data would go from [NSNull null] to nil, breaking this check.
By comparing against both values, we can ensure the correct logic for all behaviors.
To save new RNN users some trouble, I've updated the recommended Obj-C that the installation guide tells us to paste over our App Delegate. I think the old one is obsolete because the #import and one of the Obj-C methods has change. Also removed a potentially misleading warning that might now cause users to wrongly blame their NPM version for trouble instead of these new changes. Anyway this new version works for me though someone might want to double check.
Reference to function confusing and unnecessary (#2959)
Removed reference to - (BOOL)application:(UIApplication *)application... The way it's worded makes it seem like you only need to overwrite what's in the function, not the entire file's code.
There's a roundabout manner of obtaining the react context on initialisation that is null on some instances (https://github.com/wix/react-native-navigation/issues/2695), including errors on startup that prevents debugging on console. (For instance, throwing an error on index before starting the app)
It is solved by sending the same context given on method onReactContextInitialized, instead of discarding it and calling getReactContext.