Obsolete
Status Update
Comments
as...@gmail.com <as...@gmail.com> #2
interesting is thread creates for one number or for one contact? (one contact can
have more than one phone number)
have more than one phone number)
as...@gmail.com <as...@gmail.com> #3
Good question - since the "corrupting MMS" in this case comes from an e-mail address,
the thread is created using the sender's e-mail address. I'm looking through the
code now to understand how the SMS/MMS messages are stored in the SQLite database -
perhaps this sender's e-mail address or the sheer length of the MMS message causes an
mishandled corner case?
Let me know if I need to clarify further here...
the thread is created using the sender's e-mail address. I'm looking through the
code now to understand how the SMS/MMS messages are stored in the SQLite database -
perhaps this sender's e-mail address or the sheer length of the MMS message causes an
mishandled corner case?
Let me know if I need to clarify further here...
gk...@google.com <gk...@google.com> #4
Hello,
I just wanted to comment that I am having the same issue.
I only realized it was happening after I added a few new contacts or responded to
numbers that were not in my contact list before I received the
announcements@t-mobile.delivery.net... (i'm assuming this is the culprit)
As a result, any reply I make to someone that was newly added or not in my contact
list will not actually send to them (it just starts a thread that is listed as
announcements@t-mobile.delivery.net) and instead sends to the first number on my
contact list...(I have changed this to my own number...)
I don't want to hard reset bc then I will have to reinstall all of my progs...
If I don't reset, I will be annoyed with responding to all new recipients as if they
are a new number being entered into an sms, for each individual reply...
Please fix this...
Thanks
Nehemiah Richardson
I just wanted to comment that I am having the same issue.
I only realized it was happening after I added a few new contacts or responded to
numbers that were not in my contact list before I received the
announcements@t-mobile.delivery.net... (i'm assuming this is the culprit)
As a result, any reply I make to someone that was newly added or not in my contact
list will not actually send to them (it just starts a thread that is listed as
announcements@t-mobile.delivery.net) and instead sends to the first number on my
contact list...(I have changed this to my own number...)
I don't want to hard reset bc then I will have to reinstall all of my progs...
If I don't reset, I will be annoyed with responding to all new recipients as if they
are a new number being entered into an sms, for each individual reply...
Please fix this...
Thanks
Nehemiah Richardson
ry...@google.com <ry...@google.com> #5
This issue is really annoying.
As you can probably tell, it can get you into alot of trouble.
i.e. you texting one of your buddies a joke and your girlfriend ends up getting it
instead. Yeah. Not a happy time.
As you can probably tell, it can get you into alot of trouble.
i.e. you texting one of your buddies a joke and your girlfriend ends up getting it
instead. Yeah. Not a happy time.
ry...@google.com <ry...@google.com>
[Deleted User] <[Deleted User]> #6
For those of you following this issue:
I need to have some test cases that "break" the phone. If you have experienced the
issue reported above, please copy/paste the entire txt of the "corrupting MMS" to
this thread (please feel free to X out any personal information that you don't want
posted here). Most importantly, we need the exact text of:
* The recipient
* The subject of the MMS (if there was one)
* The body of the MMS
Some of this info is available when you long press on the offending MMS and go to
"View Message Details".
As an example, the one I received was sent by "onlinebanking@alert.bankofamerica.com".
Also, if you or anyone else you know has been affected by this issue, please ask them
to leave their info here. I'm hoping that if enough of us leave messages, this will
get looked at by the Google engineers. Please also mention the link to this bug in
other forums that have been reporting this problem. Thanks.
I need to have some test cases that "break" the phone. If you have experienced the
issue reported above, please copy/paste the entire txt of the "corrupting MMS" to
this thread (please feel free to X out any personal information that you don't want
posted here). Most importantly, we need the exact text of:
* The recipient
* The subject of the MMS (if there was one)
* The body of the MMS
Some of this info is available when you long press on the offending MMS and go to
"View Message Details".
As an example, the one I received was sent by "onlinebanking@alert.bankofamerica.com".
Also, if you or anyone else you know has been affected by this issue, please ask them
to leave their info here. I'm hoping that if enough of us leave messages, this will
get looked at by the Google engineers. Please also mention the link to this bug in
other forums that have been reporting this problem. Thanks.
ry...@google.com <ry...@google.com>
we...@gmail.com <we...@gmail.com> #8
I'm getting the same problem as stated on the post. This happens when I receive MMS from
Innercircle@marketinginnovators.com this is really really annoying, you can't reply, you have to create a
new thread in order for you to reply
Innercircle@marketinginnovators.com this is really really annoying, you can't reply, you have to create a
new thread in order for you to reply
Description
1. Use range.setValue() or range.setValues() inside a loop
2. Note that all write operations occur only once the loop has completed, rather than in real-time.
What is the expected output? What do you see instead?
Range values used to update in real-time, a useful feature for providing the user a sense of progress as a Spreadsheet-bound script processes specific rows of data...as in a merge. This used to be the way this function worked...
If possible, provide the code for a small sample script that reproduces the
issue:
function myFunction() {
var ss = SpreadsheetApp.getActiveSpreadsheet();
var sheet = ss.getSheets()[0];
for (var i=0; i<100; i++) {
Utilities.sleep(500);
sheet.getRange(i+1, 1).setValue("This is a test " + i);
}
}
Run this function and you will see that all write operations appear on the spreadsheet only once the loop has terminated.