I will fix it on 0.3.7, I experienced that bug while testing v0.3.6 and I didn't know how to fix it that time
