Bad bytecode when optimizer enabled

[revonateB0T]

Exception in thread "main" java.lang.VerifyError: Bad return type
Exception Details:
  Location:
    okio/Okio__OkioKt.buffer$43c083be(Lokio/Sink;)Lokio/RealBufferedSink; @17: areturn
  Reason:
    Type 'okio/BufferedSink' (current frame, stack[0]) is not assignable to 'okio/RealBufferedSink' (from method signature)
  Current Frame:
    bci: @17
    flags: { }
    locals: { 'okio/Sink' }
    stack: { 'okio/BufferedSink' }
  Bytecode:
    0000000: 2a12 01b8 000b bb00 0859 2ab7 000d c000
    0000010: 05b0                                   

        at top.kagg886.pmf.util.FileLogger.<init>(log.kt:2001)
        at top.kagg886.pmf.AppKt.setupEnv(App.kt:53907)
        at top.kagg886.pmf.MainKt.main(main.kt:2020)

FAILURE: Build failed with an exception.

See kagg886/Pixiv-MultiPlatform#83
Artifacts: https://github.com/kagg886/Pixiv-MultiPlatform/actions/runs/14911979685

[rubenpieters]

Hey @revonateB0T ! As far as I can tell, you are using R8 in your android build, as can be seen in your build logs here: https://github.com/kagg886/Pixiv-MultiPlatform/actions/runs/14911979685/job/41888362053#step:8:475 . I would suggest to submit your bug report to R8's issue tracker here: https://issuetracker.google.com/issues?q=componentid:326788 .

I'll close this issue for now.

[revonateB0T]

Hey @revonateB0T ! As far as I can tell, you are using R8 in your android build, as can be seen in your build logs here: https://github.com/kagg886/Pixiv-MultiPlatform/actions/runs/14911979685/job/41888362053#step:8:475 . I would suggest to submit your bug report to R8's issue tracker here: https://issuetracker.google.com/issues?q=componentid:326788 .

I'll close this issue for now.

Yeah, We are using r8 for android build, but proguard is used for compose desktop build(linux, win, mac)

[revonateB0T]

I'm saying the linux artifacts have bad bytecode https://github.com/kagg886/Pixiv-MultiPlatform/actions/runs/14911979685/artifacts/3088122752
Obfuscate & shrink both works, but optimizer cause bad bytecode.
@rubenpieters can you reopen it?

[rubenpieters]

I see, thanks for the clarification. I noticed that disabling the method optimizations, by adding the following to the proguard-rules.pro file:

-optimizations !method/**

Is able to work around your issue.