also please consider following @kotlin on Twitter ...
# android
y
also please consider following @kotlin on Twitter - the issue and its fix were covered there