Description:

We are currently using your component and working on creating an expose API that returns all the Player IDs associated with specific clients. We have a table that links clients to the OneSignal device_id.

The issue arises when we attempt to retrieve the Player ID using the available action — it returns incorrect results. The root cause seems to be that your table allows multiple device_id entries, as long as they are associated with different application_ids (please see the attached screenshots for reference).

Proposed Solution:

We suggest to create a new action that accept both device_id and application_id as input parameters. This would ensure the query retrieves the correct record corresponding to the specific application context.

Please let us know if this enhancement is possible, or if you can suggest an alternative solution.