I’m trying to send a broadcast command with `ProcessBuilder`. It “works”, but the output is differen...

# compose-desktop

[Guilherme Delgado]

I’m trying to send a broadcast command with ProcessBuilder. It “works”, but the output is different if I run the same command via terminal:

~ adb shell am broadcast -p com.sample -a sample.action -e "extra" "bla bla"

produces (correctly):

Broadcasting: Intent { act=sample.action flg=0x400000 pkg=com.sample (has extras) }
Broadcast completed: result=0

but the same command via ProcessBuilder produces:

Broadcasting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x400000 pkg= -p }
Broadcast completed: result=0

any idea why? 🤔

[Kirill Grouchnikov]

What has this to do with compose desktop?

[Guilherme Delgado]

I’m running it in a compose desktop app, I know this is “pure java”, but in the past I had some problemas calling specific java operations in compose desktop and I wish to remove some false positives. So I asked.

[jim]

Compose desktop apps, when built as JVM apps, are just JVM apps. I'd be very curious to understand what problems you had calling specific java operations in compose desktop, because that intuitively such problems seem unlikely to be compose related (although could possibly be jlink related, since Compose packaging uses jlink by default, see: https://github.com/JetBrains/compose-jb/blob/master/tutorials/Native_distributions_and_local_execution/README.md#configuring-included-jdk-modules).

[Guilherme Delgado]

yup my bad, the issues I had in the past where related to missing modules like you said. In this case in specific was a bit different, but i thought it could also be related to a missing import. Sorry for the off-topic.