Android : SMSManager - Attempt to get length of null array

Question

I have a bug from the SMSManager when I try to send a message with the method sendTextMesasge. It returns me a java.lang.NullPointerException: Attempt to get length of null array.

There is my code :

        // Constructs the message
        TelephonyManager mTelephonyMgr = (TelephonyManager) getSystemService(Context.TELEPHONY_SERVICE);     
        String myPhoneNumber = mTelephonyMgr.getLine1Number();
        String destNumber = taskManager.getHelpCenterNumber();
        String message = getResources().getString(R.string.call_me_message) + " " + myPhoneNumber+".";

        // Sends the message
        SmsManager smsManager = SmsManager.getDefault();
        smsManager.sendTextMessage(destNumber, null, message, null, null);

The LogCat receives this message :

08-03 09:59:10.548: E/AndroidRuntime(19825): FATAL EXCEPTION: main
08-03 09:59:10.548: E/AndroidRuntime(19825): Process: com.solarsquareretailer.view, PID: 19825
08-03 09:59:10.548: E/AndroidRuntime(19825): java.lang.NullPointerException: Attempt to get length of null array
08-03 09:59:10.548: E/AndroidRuntime(19825):    at android.os.Parcel.readException(Parcel.java:1546)
08-03 09:59:10.548: E/AndroidRuntime(19825):    at android.os.Parcel.readException(Parcel.java:1493)
08-03 09:59:10.548: E/AndroidRuntime(19825):    at com.android.internal.telephony.ISms$Stub$Proxy.sendText(ISms.java:1428)
08-03 09:59:10.548: E/AndroidRuntime(19825):    at android.telephony.SmsManager.sendTextMessage(SmsManager.java:305)
08-03 09:59:10.548: E/AndroidRuntime(19825):    at com.solarsquareretailer.view.MainActivity.onOptionsItemSelected(MainActivity.java:245)

score 5 · Accepted Answer · answered Jan 11 '16 at 13:30

5

Found my destNumber was null and not correct (Not a phone number). It's why I have a java.lang.NullPointerException.

answered Jan 11 '16 at 13:30

Sigvent

297
4
17

score 1 · Answer 2 · edited May 23 '17 at 12:08

I've found this several of times in my app in the wild (but never on my tests), and tried to find a solution for months. So far I could not find a test case that reproduces it.

Using the Sms.sendMultipartTextMessage method:

SmsManager sms = SmsManager.getDefault();
ArrayList<String> parts = sms.divideMessage(msg);
sms.sendMultipartTextMessage(number, null, parts, null, null);

Does not help either - as internally it ends up calling sendTextMessage if the message has only one part - but anyway, it might be a good idea if you switch to it just in case you have longer messages.

I ended up wrapping the code in a try-catch and reporting to a server whenever it happens. And from what I've seen, seemingly 'normal' messages seem to trigger it.

There is a similar case here, but in that case the message has a PendingIntent for sent. You might want to try that.

I try your method to check where is the problem :) – Sigvent Aug 03 '15 at 09:54 — Sigvent, Aug 03 '15 at 09:54

score 1 · Answer 3 · answered Aug 03 '15 at 09:22

1

First , you need permission in AndroidManifest.xml for read Phone State

<uses-permission android:name="android.permission.READ_PHONE_STATE"/>

Then try to get Mobile Number of Device in Try Catch Block .

It may happen that getLine1Number() return null value . So you need to handle exception

try 
{
    myPhoneNumber = mTelephonyMgr.getLine1Number();
}
catch(NullPointerException ex)
{
}

answered Aug 03 '15 at 09:22

Kiran Choudhary

1,125
7
15

Yes, i have this line on my AndroidManifest. – Sigvent Aug 03 '15 at 09:54

Android : SMSManager - Attempt to get length of null array

3 Answers3