Relaunching the app if it initially fails to activate should fix this. This is a known issue and we're looking at ways to resolve this. Sorry for the inconvenience!

Did this answer your question?