Looks like the last version (4.6.2) fixed the issue
Topic:
Developer Tools & Services
SubTopic:
Swift Playground