We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
Sorry… I don't remember if I closes the window or clicked in "Don't authorize" or tried to change accounts.
Now, I can't try to create an account with Google in Safari.
Sorry… I don't remember if I closes the window or clicked in "Don't authorize" or tried to change accounts.
Now, I can't try to create an account with Google in Safari.
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
We've caught that bug 1 or 2 times while QA before official release, but we can't recreate it all the time.. We'll take a closer view on that by the end of the week and include fix in the next release.
Update: the problem is solved in 1.0.1
Replies have been locked on this page!