Update 2 (Follow this approach)
You shouldn’t do this now. Instead fix all the errors. This is only a workaround until it’s removed. After that, you’ll need to fix errors manually anyways.
Try to update your gradle plugin to 3.3.0-alpha06 to check if that fixes your issue.
Update 1:
Non-ascii characters issues have been fixed in AAPT2 and android gradle plugin now (yay!). Instead of disabling AAPT2 now you can just use android gradle plugin version 3.2.0-alpha11 or newer and you should not encounter this error anymore.
Original Answer
Aapt2 is enabled by default when you use android plugin for gradle 3.0.
This is to
improve incremental resource processing
as stated here.
But if you are facing issues with it, you can switch back to previous version by adding this in gradle.properties
android.enableAapt2=false