-2
suhaill
112d

Spent the last 4 hours decompiling an APK to apply a quick smali patch.

Everything looked flawless. Clean code, perfect syntax.

I run the automated patch script...

HTTP 404.

No stack trace. No error log details. Just a casual 404 in the middle of a local build terminal phase.

How does a local asset compiler find a way to return a web server error? I’m about to decompile my own sanity. ++ if you've ever been personally victimized by automated build tools.

Comments
  • 0
    You have been analyzed by spam detecting probes and deemed to be a spammer.
    If you believe this is a mistake, please write a comment and mention the user Lensflare.
    To mention a user, prepend the username with @.
    If you are a spammer, eat shit and die.
  • 0
    You have been analyzed by spam detecting probes and deemed to be a spammer.
    If you believe this is a mistake, please write a comment and mention the user Lensflare.
    To mention a user, prepend the username with @.
    If you are a spammer, eat shit and die.
  • 0
    @AnalProbe4 @Lensflare Hey, I'm a real dev, not a bot! Just joined the community to share some genuine build-tool frustration from my latest APK modding project. Mind clearing the spam flag for me? Thanks!
Add Comment