-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.lang.IllegalArgumentException: bad utf-8 byte dc at offset 000000eb #37
Comments
Thank you for including the problematic dex file. It is a very small dex with only 5 strings, and looking at the encoding it is indeed an illegal encoding. Dumping the bytes of the 5 strings gives:
The two bytes I have landed https://r8-review.googlesource.com/c/r8/+/90260 to give a bit more information on the decoding issue. |
See google/smali#37 Change-Id: Idd099efb61b3115b38598b8c5835a4e9ce0d9f52
thanks! I'll close this out when I see it land in GitHub |
The R8 source is not in GitHub, but on googlesource.com. Change with better error reporting is in 8.4.21-dev. |
Thanks apologies - I was so used to just watching smali in GitHub and was unaware of parent dependencies and how they played out in Google ecosystem. |
That said, let's keep this open, and I will extend the error messages in |
Thanks for the reference/link to R8 @sgjesse - I had no idea it worked for regular Java projects. I moved Apktool over and it seems to have solved my last remaining issues on the way to making reproducible builds - iBotPeaches/Apktool#3559 |
I frequently am finding dex files like this and previously it was fixed in smali 2.3. Though since in this same application
classes13.dex
is a completely empty file - I'm partial to believing this is just a corrupted useless file.context: iBotPeaches/Apktool#3503
file above: classes1.zip
The text was updated successfully, but these errors were encountered: