I cannot Speak to Jetpack Compose - And how it is using the Intent API in general.

But I would suggest a few things:

1. Disable the default profile (Profile0) - Normally used for barcode capture via a KeyStroke output - but this DW profile can be inadvertently used when the Barcode Trigger (especially when setup as "terminal scanner") will activate Datawedge, and "Profile0" may be stepping on the app. 
2. If you use / understand the principles of the Datawedge Demo here in TechDocs (This is for Android Studio btw. )
   Starting here: https://techdocs.zebra.com/datawedge 
   Development Samples here: https://techdocs.zebra.com/datawedge/latest/guide/samples/ 
   And this Git Repo for these same Samples here: https://github.com/ZebraDevs/DataWedge-Android-Samples
3. I may suggest looking at the code for the "BasicIntent1" - and Reading Carefully for the steps to create the "BasicIntent1" Datawedge profile. (TLDR - you need to follow these steps: https://techdocs.zebra.com/datawedge/15-0/guide/samples/basicintent1/   Make sure you create this and test it and understand it. )

Because I suggest the "Profile0" to be disabled - then when you work on the Datawedge profile for Jetpack - and your profile is correctly assigned to send its intent to that app - then you can also get the Read Events and manage these as you see fit.

The RFID capture can also be turned on in this profile (You can disable the Barcode Capture - and turn on the RFID Capture.)

( FYI - on RFD40 / RFD90 - the "Scan Trigger" Can be setup to be usable for "Barcode Scanning" and the RFID Trigger can be setup for RFID Scanning.)  - I tested this on TC27+RFD40 via eConnex Sled.  And BasicIntent1 - captures both barcode and RFID Data.