It looks like you've set up everything correctly, but there are a few things you can check and try to troubleshoot why you're not receiving the response from DataWedge. Let's go through them step by step:

1. Check DataWedge Logging for Errors

Since DataWedge is not sending a response, check if the GET_PROFILES_LIST intent is being processed at all:

• Open DataWedge > Settings > Enable DataWedge Logging.

• Use ADB Logcat to check if any errors appear when you send the intent:

  adb logcat -s DataWedge
  

• If there’s an issue with intent handling, you should see relevant logs.

2. Verify Broadcast Receiver Setup

Ensure that your broadcast receiver is actually running and listening to the correct intents. Some things to check:

• The response from DataWedge should contain an Intent action of com.symbol.datawedge.api.RESULT_ACTION. Your receiver should be listening for this.
• Ensure your receiver is properly registered.

Try registering it dynamically instead of using intentShim:

Test with Java/Kotlin

If possible, test with native Java/Kotlin code to check if the issue is with intentShim:

BroadcastReceiver dataWedgeReceiver = new BroadcastReceiver() {
    @Override
    public void onReceive(Context context, Intent intent) {
        if (intent.getAction().equals("com.symbol.datawedge.api.RESULT_ACTION")) {
            Bundle extras = intent.getExtras();
            if (extras != null && extras.containsKey("com.symbol.datawedge.api.RESULT_GET_PROFILES_LIST")) {
                ArrayList<String> profiles = extras.getStringArrayList("com.symbol.datawedge.api.RESULT_GET_PROFILES_LIST");
                Log.d("DataWedge", "Profiles: " + profiles);
            }
        }
    }
};

// Register the receiver dynamically
IntentFilter filter = new IntentFilter();
filter.addAction("com.symbol.datawedge.api.RESULT_ACTION");
context.registerReceiver(dataWedgeReceiver, filter);

If this works, the issue may be related to how intentShim is handling broadcasts.

3. Ensure DataWedge Has Permission to Send Broadcasts

Starting from Android 12+, broadcast receivers need explicit permissions to receive implicit broadcasts.

Try adding the following to your AndroidManifest.xml:

<receiver android:name=".DataWedgeReceiver"
    android:exported="true">
    <intent-filter>
        <action android:name="com.symbol.datawedge.api.RESULT_ACTION"/>
        <category android:name="android.intent.category.DEFAULT"/>
    </intent-filter>
</receiver>

Also, request RECEIVE_BROADCAST permission:

<uses-permission android:name="android.permission.RECEIVE_BROADCAST"/>

4. Force DataWedge to Send Result via "SEND_RESULT"

In some cases, DataWedge doesn’t send responses automatically. You can explicitly request a response using the SEND_RESULT flag.

Modify your GET_PROFILES_LIST request like this:

const intent = {
   action: 'com.symbol.datawedge.api.ACTION',
   extras: {
       'com.symbol.datawedge.api.GET_PROFILES_LIST': '',
       'SEND_RESULT': 'LAST_RESULT'
   }
};

This forces DataWedge to send the response as the last known result.

5. Check If DataWedge is Running in Foreground

Sometimes, DataWedge might not process requests properly if it is inactive or crashes in the background.

Try restarting DataWedge manually:

1. Open the DataWedge app.
2. Go to Settings > Disable DataWedge > Enable DataWedge.
3. Restart your app and try again.

6. Verify That Other Intents Work

To determine if the issue is with GET_PROFILES_LIST specifically, try sending another API request, such as GET_VERSION_INFO:

const intent = {
   action: 'com.symbol.datawedge.api.ACTION',
   extras: {
       'com.symbol.datawedge.api.GET_VERSION_INFO': ''
   }
};

If this also doesn’t return a response, the problem may be with the broadcast setup.

7. Try Using "START_ACTIVITY" Instead of "BROADCAST"

As a last resort, switch from BROADCAST to START_ACTIVITY in your DataWedge configuration:

intent_delivery: 'START_ACTIVITY'

This will open your app when a scan is received.

Next Steps

• ✅ Enable DataWedge logging and check logs with adb logcat -s DataWedge.
• ✅ Test GET_VERSION_INFO to see if any API calls work.
• ✅ Register a native broadcast receiver in Java/Kotlin and check if the issue is with intentShim.
• ✅ Add the necessary permissions in AndroidManifest.xml.
• ✅ Explicitly request a response with SEND_RESULT.

. . . . .