This has been reported by another person a year ago:
According to its name and meaning, it should only be triggered when the keyboard is/isnt visible anymore.
Is this intended behavior or a bug?
2 Likes
3 posts were merged into an existing topic: When Screen.Keyboard Visible Changed => function is called continuously