The background is that I am converting an existing expo workflow application to be built via EAS in order to build an APK that will pass Google’s Families Policy Requirements.
eas-cli/0.17.0 win32-x64 node-v12.18.3
Expo Workflow: managed
The application uses
expo-sms and this works with the APK when built using the
expo build:android command.
However the new APK’s that we get from building it via
eas build results in a runtime error where the
sendSMSAsync promise fails with the message “No messaging application available”.
I think it might an issue with newer versions of android, as I get this error on my Pixel 5, but when I try the same APK on older devices it does work and the SMS application does opens up.
I have tried giving my application various permission via the android.permissions setting in app,json with no success. When I compare the android manifests from the two versions I did notice the old working one had a section
<intent> <action name='android.intent.action.SENDTO'> </action>
which is missing in the new one.
Is this a bug with EAS? Or is there some config I am missing for requesting that permission?