frimtec / secure-sms-proxy Goto Github PK

I have a third party messaging app which I registered to the S2MSP application. The registration is done with no problem and the application shows on registered apps with the phone numbers that I specified. Once I add the SMS receiving implementation to my SMS Listener, the app stops receiving messages from all numbers even the registered ones.

my on receive function:

List<Sms> receivedSms = getSmsFromIntent(context, intent);
receivedSms.stream().filter(sms -> SecureSmsProxyFacade.PHONE_NUMBER_LOOPBACK.equals(sms.getNumber()));
for (Sms sms : receivedSms) {
       ......
}

my getSmsFromIntent function:

  private static List<Sms> getSmsFromIntent(Context context, Intent intent) {
    SecureSmsProxyFacade s2msp = SecureSmsProxyFacade.instance(context);
    return s2msp.extractReceivedSms(intent, null);
  }

The secret is null because I did not define it in the registration
Hope someone can show the exact steps to implement the SMS receiving function

I reported a bug and you think I'm playing games? I don't even play with my kids let along grown-ups.

When I installed the latest version it was not working until I deleted the contacts from Operations Center and had to re-add them. This didn't happen on my Android 9 phone, only on my Android 13 OnePlus 8T. Even the send test Sms wasn't working until I deleted contacts. Whether you add the feature (to delete contacts individually or all at once) or not I know how to improvise. This is what I do, test software, report bugs and go about my day. Nothing more nothing less.

P.S

Imagine having an app on your phone full of contacts stored and the only way to remove old or non-working numbers is to have to delete them all because that's how the app is designed. I guess in the world of programming/developing it is the ideal thing. Anyways thanks for a good app.👍

On some devices the buttons allow and reject are too close together.

S2MSP should support alphanumeric short code SMS phone numbers as of feature request in pikett-assist (frimtec/pikett-assist#475).

What needs to be changed:

• Enhance formatting for displaying numbers in the UI (currently only "null" is rendered).
• Prevent sending any SMS to an alphanumeric short code SMS phone number by just skipping the send request. Alphanumeric short code SMS phone numbers can only be used for receiving SMS.

Hello, can you please suggest me some java-based SMS messengers where this project can be implemented?
Thanks for your help and sorry for bothering

DB handling in content provider:

• create in onCreate()
• move definition in manifest to bottom

Please explain in layman's terms. Thank you. I really just started getting into the phone scene. I've mostly been on Linux and Windows. Thanks again.

Hint: https://docs.gradle.org/current/userguide/publishing_maven.html

Issue

In some environments (could be the carrier or LineageOS) the SMS deliverd from the OS to S2MSP are not in the international but only in the local format.
S2MSP currently can only match international numbers.
See also frimtec/pikett-assist#412 from @rck.

Fix idea

S2MSP should try to identify local numbers and extend them with country prefix of the SIM owner before matching them to applications.

Do you think it's possible to add Google Voice Support? A feature to import all the contacts at once instead of individually? Thanks for the great app. Also maybe add a backup feature import/export settings.

Whenever I install a new update it doesn't work until I delete numbers in the Operations Center. This is why I asked to not have all the numbers tied to the delete button. So every update I have to delete all the contacts just to add them all back. This is only on Android 13 OnePlus 8T but works fine on Android 9

In some sender and receiver carrier combinations the "+" in the SMS origin address is missing.
S2MSP can then not match the number to the correct application.

The Google code analyse does not like the hard coded initialization vector in the API class.
We may better use asymmetric encryption to get rid of this warning.

Hello,
is it possible please to mention the implementation steps in a kotlin based SMS messenger?
Thanks for your efforts