Is view and controller coupled to each other in iOS mvc design pattern?

I have read lot of articles on MVC. I came to one conclusion. M- it's a model object represents business logic. V- it's basically a view. Example any class that represents itself a view or subclass of a view. C- it helps to communicate between model and view.

But I have read multiple answers for mvc in iOS where it says view and controller tied to each other. That's the reason it is usually called viewcontroller? In other article it just says it follows proper mvc which I described it above. Please help me guys which is true. Any kind of help is appreciated.