Skip to content
Discussion options

You must be logged in to vote

Hi there! This is caused by a critical bug introduced in version 1.7.5.2, which has already been followed in issue #1625 .
You can avoid this problem by deploy in full version instead of speed version. (Choose 2 not 1 in deploy.sh)

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by Phinease
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants