tkporter/react-native-sms

Google Declaration Form on SMS Restrictions

Opened this issue · 8 comments

With Google's new restrictions on sms/call log permissions, how do you recommend filling out the permissions declaration form when submitting your new APK to use react-native-sms.

I'm also having this issue - I don't need the "success tracking" that presumably READ_SMS is required for, I just want to send SMS's.

What we can do for this issue?

Is it possible to use the module to initiate SMS requests without requiring the READ_SMS permission? Presumably the READ_SMS permission is used to track the sent/success status, but this may not be required for many developers.

Deadline to remove read_sms from apps on the app store is coming up in 2 days - ideally I'd like to avoid removing the whole package, anyone figure something out? @isurugajasinghe @murdocke

We started using platform specific code. For IOS we kept with react-native-sms and for Android we installed react-native-send-intent. We don't know if the message was truly sent or cancelled (so we just assume you sent the message) for Android users but at least they can still send out an sms. @dancherb

Alguma solução quanto a isso?

nihp commented

Same here. Any other solution

I managed to bypass this issue by passing this option allowAndroidSendWithoutReadPermission: true and changing the permission from <uses-permission android:name="android.permission.READ_SMS" /> to <uses-permission android:name="android.permission.SEND_SMS" />. In my case I only need to send SMS, hopefully it helps someone.