@fontadoni
16 years, 11 months ago
I just updated to version 1.0.2 and I’m getting this same error. Any clue on what might be going on or how can it be fixed?
