SMS send block causing NullPointerException

[Henrik "The Developer" Lindqvist]

On some devices the SMS send block will fail with the following error:

java.lang.NullPointerExeption: Attempt to read from field 'java.lang.String android.content.pm.PackageInfo.packageName' on a null object reference

This is Android or manufacturer ROM bug. It seems to be cause by the app "thread" (ActivityThread) not being properly initialized, cause yet unknown.
The only workaround, for now, is to use the MMS send block instead.

Conclusion of testing so far:

• It doesn't seem to be caused by sending from a background (non-main) thread.
• It doesn't seem to be caused by the SEND_SMS permission being in the separate add-on app.
• Multiple user profiles (device users) running Automate on the same device.
  
• The use of sharedUserId, i.e. sharing a single uid (app user space) for multiple apps, as Automate does to facilitate the permissions add-ons.
  
• The use of a separate process for background work, as Automate does to reduce memory usage.
  
• Binder caller uid/pid "leakage".
  

Reportedly affected devices:

• Android 5.1 on a Meizu M2 with Flyme OS 4.5.3.2C
• Doogee X5 with stock ROM v18 and several custom ROMs
• P8000 phone on Android 6 (working on Android 5.1)
• Philips Xenium v377
• Android 6.0 on Lenovo A7000
• acer/T03_emea_gen1/acer_t03:5.1
  

Please post your device manufacturer/model, Android version and custom ROM name, if used.

Alpha version 1.6.0a1 include a new workaround, please test:
https://play.google.com/apps/testing/com.llamalab.automate

A workaround has been found! Enable the SMS send workaround option if settings.

[Henrik "The Developer" Lindqvist]

New test app created!
Please run the attached debug app to help me test if the use of a background process is the cause of the issue.

[schurli...@gmail.com]

Hi Henrik,

just tested your app and I tried sending myself and my girlfriend the test sms and both WORKED.

Congratulations, do you need any info, logs?
I am the Meizu guy ;-)

[giovann...@gmail.com]

This app on Xiaomi Mi5, works fine!

[brai...@gmail.com]

On Tuesday, January 3, 2017 at 3:19:26 AM UTC+2, Henrik "The Developer" Lindqvist wrote:

New test app created!
Please run the attached debug app to help me test if the use of a background process is the cause of the issue.

It worked! "SMS send without issue"!

Device: Lenovo A7000-a

Android version: 6.0

Build number: A7000-a_S228_160621_ROW

It seems that you found a workaround to the bug, so we hope to get soon a new "Automate" version!

And again, congratulations for your fine application.

Constantin Teodorescu

[Henrik "The Developer" Lindqvist]

Thanks for testing, and reporting back.
Sadly, a successfully sent SMS is not was i was hoping for since it means we still haven't found the cause.
I'll post another test app soon.

[Henrik "The Developer" Lindqvist]

New test app created!
Please run the attached debug app to help me test if the use of sharedUserId (including a background process) is the cause of the issue.

[saffl...@gmail.com]

Medion E5004 with Android 5.1

[brai...@gmail.com]

On Wednesday, January 4, 2017 at 2:56:54 AM UTC+2, Henrik "The Developer" Lindqvist wrote:

New test app created!
Please run the attached debug app to help me test if the use of sharedUserId (including a background process) is the cause of the issue.

This second new test app worked also for me: "SMS send without issue" , received it on another phone!

Same Device: Lenovo A7000-a

Android version: 6.0

Build number: A7000-a_S228_160621_ROW 

Teo

[Henrik "The Developer" Lindqvist]

Okay, i'll make some other changes.

[otakim...@gmail.com]

Am having the same problem, tried several messaging apps, always flow reports '1 SMS sent to...' but does not arrive. Tried the second smsbug test app and worked OK, SMS received OK on destination phone!

Device: Lenovo A3600-d

Android version: 4.4.2

Build number: A3600-d_S161_141210_CU_verter.org 

On Friday, December 30, 2016 at 11:01:47 AM UTC+13, Henrik "The Developer" Lindqvist wrote:

On some devices the SMS send block will fail with the following error:

java.lang.NullPointerExeption: Attempt to read from field 'java.lang.String android.content.pm.PackageInfo.packageName' on a null object reference

This is Android or manufacturer ROM bug. It seems to be cause by the app "thread" (ActivityThread) not being properly initialized, cause yet unknown.
The only workaround, for now, is to use the MMS send block instead.

An initial round of testing has been done, conclusion so far:

• It doesn't seem to be caused by sending from a background (non-main) thread.
• It doesn't seem to be caused by the SEND_SMS permission being in the separate add-on app.

Possible causes still to be tested, see attached APKs below:

[Henrik "The Developer" Lindqvist]

Trying a new workaround in Alpha 1.6.0a1:
https://plus.google.com/u/0/b/110165001747691845730/110165001747691845730/posts/ZgetBzG9Kdt

Please let me know if it works, or as most likely, it doesn't.

[saffl...@gmail.com]

404 error on that link

[saffl...@gmail.com]

Forgive the stupid question, how do i manually install test apps? - I thought the only way was via google play lol.

[Henrik "The Developer" Lindqvist]

Odd, link work find for me. Yes Alpha/Beta version are distributed by the Google Play Store but you'll have to opt-in at:
https://play.google.com/apps/testing/com.llamalab.automate

[google user]

you need to download the apk like any other file from a host, then open it from your file viewer.
Since it's an unknown, unvetted file, android will refuse it. You'll have to activate "install from unknown sources"
http://gs4.gadgethacks.com/forum/enable-unknown-sources-android-install-apps-outside-play-store-0150603/

[Henrik "The Developer" Lindqvist]

Anyone testing the workaround? Feedback please!

[saffl...@gmail.com]

Disappointingly that test app worked. I hoped it would fall so that you would have a better clue about what's going wrong.

[saffl...@gmail.com]

I did join the test group until I realised that the new version would replace my existing version so I had to leave again. Sorry about that. If you can make it possible to run both somehow then I will join again.

[Henrik "The Developer" Lindqvist]

Which app did you test?

Please test the Alpha:
https://play.google.com/apps/testing/com.llamalab.automate

You can have either the Alpha or the public (1.5.1) version installed. 

[Henrik "The Developer" Lindqvist]

Due to the lack of feedback, i'm now forced to remove the experimental workaround implement in Alpha version 1.6.0a1 before public release.

[jeremy.n...@gmail.com]

Hi have the same issue on my WIKO LENNY 3 (Android 6.0).
Can you please notify me when the experimental workaround is available in the alpha version.
If you want I can try your test app ?
Thanks

[Henrik "The Developer" Lindqvist]

It's already available in the currently published Alpha version 1.6.0a1. Enable it in Automate settings.
Download at: https://play.google.com/apps/testing/com.llamalab.automate

[jeremy.n...@gmail.com]

I have a good news for you, the workaround is perfect !
Video : https://drive.google.com/file/d/0B59uGPL2RIChX3NIMTdwTGZ2OEk/view?usp=drivesdk

[Henrik "The Developer" Lindqvist]

THANK YOU!
Great, finally a working solution. So the use of separate processes is the culprit.

[saffl...@gmail.com]

Confirmed. Workaround in the options works for me too although it does perhaps need to be made clearer that this option is available.

[prasada...@gmail.com]

I too had the same issue in XIOMI Redmi Note 4(Android 6.0.1). So can you please post the workaround?

On Friday, December 30, 2016 at 3:31:47 AM UTC+5:30, Henrik "The Developer" Lindqvist wrote:

On some devices the SMS send block will fail with the following error:

java.lang.NullPointerExeption: Attempt to read from field 'java.lang.String android.content.pm.PackageInfo.packageName' on a null object reference

This is Android or manufacturer ROM bug. It seems to be cause by the app "thread" (ActivityThread) not being properly initialized, cause yet unknown.
The only workaround, for now, is to use the MMS send block instead.

Conclusion of testing so far:

• It doesn't seem to be caused by sending from a background (non-main) thread.
• It doesn't seem to be caused by the SEND_SMS permission being in the separate add-on app.

• Multiple user profiles (device users) running Automate on the same device.
  
• The use of sharedUserId, i.e. sharing a single uid (app user space) for multiple apps, as Automate does to facilitate the permissions add-ons.
  
• The use of a separate process for background work, as Automate does to reduce memory usage.
  
• Binder caller uid/pid "leakage".
  

Reportedly affected devices:

• Android 5.1 on a Meizu M2 with Flyme OS 4.5.3.2C
• Doogee X5 with stock ROM v18 and several custom ROMs
• P8000 phone on Android 6 (working on Android 5.1)
• Philips Xenium v377
• Android 6.0 on Lenovo A7000
• acer/T03_emea_gen1/acer_t03:5.1
  

Please post your device manufacturer/model, Android version and custom ROM name, if used.

Alpha version 1.6.0a1 include a new workaround, please test:
https://play.google.com/apps/testing/com.llamalab.automate

A workaround has been found! Enable the SMS send workaround option if settings.

[Henrik "The Developer" Lindqvist]

As the doc say, enable the "SMS send workaround" option in Automate settings.

[aman.v...@gmail.com]

Getting this error. As you can see the Device is Redmi 5A and the version is 7.1.2.

What could be the reason of this error?

The Permissions are given. I think this is internal and device dependent.