Because I am working on a chat software, I found that users reported receiving garbled images, as shown below:
MediaItem{mOriginalPath='/storage/emulated/0/Pictures/Screenshots/Screenshot_xxxxxx.jpg', mThumbPath='', origId=46907, generateDate=1690439895000, dateTag=null, isChecked=false, mMimeType='image/jpeg', mLongitude='181.0', mLatitude='91.0', mBusinessTag='null'}
Looking at the database, this message is stored in text format, not file format. I thought it was some file-related keyword that caused the sender to fail to send the image, so I directly sent the locally concatenated JSON to the server. But later, I realized that this format has nothing to do with the format of images in my app! These keywords are not even in my system. So I searched the internet and found that many platforms have the same format of text, almost always occurring when sending images, including but not limited to Douyin, Xiaohongshu, Baidu Tieba, Chunyu Doctor, etc. (as shown in the following images)
Then my first instinct was that it was caused by sharing from the local album, where the system might have received the wrong format or there might be a delimiter in the file name. So I immediately investigated, but couldn't find any relevant content. I looked at the text information above again and found that it contains mLongitude, mLatitude, and mBusinessTag, which are longitude and latitude information and business tags. Normally, the local album would even specifically erase this information, so it shouldn't be there.
But after continuous searching, I finally found the problem. The concatenation code for this string was found in multiple decompiled WeChat repositories (information from the internet, please see the link below for details):
It turns out to be the concatenation format when WeChat sends images.
However, it is still unknown why this appears in our app and other major apps. But it can still be determined that this is another 💩 pulled by the 🐉 inside the phone.