Yep, I know.
Is it possible to fix this bug and release it in with a 3.0.2 update?
Because it’s quite important for me right now.
Looks like Sander wasn’t right while the previous build was on production.
Yep, I know.
Is it possible to fix this bug and release it in with a 3.0.2 update?
Because it’s quite important for me right now.
Looks like Sander wasn’t right while the previous build was on production.