Whenever limiting text input, you also want to consider the user experience. Will people get frustrated because you aren't telling them why they can't type more?
You have a few options here
1.) Just don't let them type any extra characters. This isn't necessarily bad, especially if you're in time cruch and just need to ship the product.
2.) When they type extra characters, interrupt them with an alert. This can have its place if the type of data they've entered doesn't match what the app expects, and you need to explain why. For example a text input for number of minutes in the hour, and they enter "600" Well there aren't 600 minutes in an hour, so you might want to interrupt them and tell them to enter a number smaller than 60.
3.) Let them type the extra characters. When they go over the limit, show a red label with the number of characters they have gone overboard (A.K.A. Twitter sytle). This is my personal favorite because it's so much less intrusive. It gives people a visual so they can solve the problem in front of them. All they need to do is decrease the red number to zero. Then you validate their input once they try to save the data.
I have a framework out on github with a protocol you can use to get the third behavior. You might want to check it out.
https://github.com/TheoBendixson/CharacterLimited