You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After creating an MMS/SMS app myself for a few months we've run into issues where we have to query the mms table and we always get the current users phone number back in the list of addresses. I'm not sure why but in Klinker it's filtering the current user for when creating or getting the threadid but the address table is updated with all of the unfiltered addresses.
This logic is in PduPersister.loadRecipients
The text was updated successfully, but these errors were encountered:
Also i'm not sure if this is a big issue but it looks like were not checking the subscription id when checking the line1number so on dual sim phones the loadRecipients may not work properly.
After more thought, this would cause us to not know if it's a group message or not I believe, if we could know if it's a group than passing the addresses into the ADDR table would be unnecessary.
After creating an MMS/SMS app myself for a few months we've run into issues where we have to query the mms table and we always get the current users phone number back in the list of addresses. I'm not sure why but in Klinker it's filtering the current user for when creating or getting the threadid but the address table is updated with all of the unfiltered addresses.
This logic is in PduPersister.loadRecipients
The text was updated successfully, but these errors were encountered: