Android Messages removing leading 0 from numbers

[JascaDucato]

Hi all,

Since upgrading my Sony Xperia XZ Premium to Andorid 9, I've been encountering an issue with Android Messages where the app is removing the leading 0 from the contact number, thereby rendering the number unreachable (I've highlighted "the app" because I am not 100% certain it is Messages fault, and not tied to O2 in some way or Sony's update).

This issue never occured before updating to Android 9, so I am fairly confident that this is factoring into the issue in some way - it is also worth noting that whilst uninstalling and reinstalling the app's updates resolves the issue temporarily, when I just received a text from "02" (note the zero, rather than the letter O) the problem returns. Indeed, when I look at my SMS log for that particular contact, it says I am in a "conversation with 2".

I know this is a user forum, but I am wondering if anybody else has encountered this issue, regardless of device model, or if it has been reported to O2 already? I should also point out that I have also been having trouble with an O2 mast being down in my area for the last two weeks, so my initial assumption was that it was tied to that in some way, but it doesn't appear to be the case.

Many thanks in advance for your responses,

[MI5]

@viridis?

[gmarkj]

I'll tag the resident Sony expert @viridis - any ideas?

[viridis]

Not seen anything like this, let me forward it and get back to you.

[viridis]

Hi, is it possible to test using a different messaging app such as textra etc.
Do you see the full number then?

Also, is it all contact numbers ? Or just this "02"(which isn't O2 btw)

[JascaDucato]

The only SMS messaging app I use is the stock one, so I haven't tried it on any others as yet. Annoyingly, this appears to be the worst day to attempt any sort of testing, but I shall give it a go tonight.

That being said, it has just now occurred to me that this might be related to the SMS Widget I installed to replace the stock widget being phased out (god knows why!) A quick look at some reviews for it on Play Store shows others complaining about the same problem. Given that I only installed it after Android 9 (to replace stock) it seems that this is the most likely culprit.