Prevent contact number NPE#5460
Conversation
//FREEBIE
|
@cascheberg Great, thank you for the fix! |
|
Got also an SMS that caused the crash described in #5454, this fixes it for me. After compiling my own Signal apk with this patch applied, I am able to access all my messages again including the SMS that caused the crash. Thank you, hope this will be merged into the main-branch soon. |
|
Is there any way I can apply this to an existing installation? My messages are trapped due to #5454 :-( Or, any details on when this will be merged & released? |
|
If you have compiled Signal yourself or you have root you can do that. But it's better to ask help for those at https://whispersystems.discoursehosting.net/ |
|
Thank you, I now did verify, this PR is correct solution for problems discussed in #5454 |
Both invite links now work over `https` -- yes I tested :-) More info: EFForg/https-everywhere#4505 http://webmasters.stackexchange.com/questions/87163/do-bitly-branded-short-domains-support-https/92407#92407 PS: https://sgnl.link/1IvurmD also works. Closes #5460 Fixes #4060 // FREEBIE
Closes signalapp/Signal-Android#5460 Fixes signalapp/Signal-Android#5454 //FREEBIE Upstream commit: signalapp/Signal-Android@49a539a
Closes signalapp/Signal-Android#5460 Fixes signalapp/Signal-Android#5454 //FREEBIE Upstream commit: signalapp/Signal-Android@49a539a
Closes signalapp/Signal-Android#5460 Fixes signalapp/Signal-Android#5454 //FREEBIE Upstream commit: signalapp/Signal-Android@49a539a
Contributor checklist
FREEBIEin my commit messageDescription
I can't reproduce the crash in #5454, but this should fix it: if the returned contact phone number is
null, fall through to return defaultRecipientDetails.It's still not clear to me which result is actually returned.
I have some "numberless" SMS in my stock messaging app, and there I can't even add the sender to my contacts.
//FREEBIE