owios7 / android-sms

Automatically exported from code.google.com/p/android-sms
0 stars 0 forks source link

Application crashes when trying to backup a certain message #77

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Install and launch SMS Backup.
2. Enter your credentials.
3. Start a backup.

What is the expected output? What do you see instead?
Expected: Completely backup all 92 SMS messages to Gmail.
Actual: SMS Backup syncs about half of them, then crashes. Restarting it
and doing a backup again makes it crash immediately. Uninstalling and
reinstalling makes it crash again after syncing the number of messages to
Gmail.

What version of the product are you using? On what operating system?
Version 1.1.1 on an HTC Hero (Android 1.5).

Stack trace below (the main part of the phone number has been removed for
privacy reasons, but it's an actual phone number of someone I have received
SMS messages from and sent to):
04-11 13:37:45.604: ERROR/AndroidRuntime(1147): Uncaught handler: thread
Thread-7 exiting due to uncaught exception
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):
java.lang.IllegalArgumentException: Unknown URL
content://contacts/phones/filter/+49171/[valid 7-digit phone number removed]
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:129)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:111)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
android.content.ContentProviderProxy.bulkQuery(ContentProviderNative.java:279)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
android.content.ContentProviderProxy.query(ContentProviderNative.java:298)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
android.content.ContentResolver.query(ContentResolver.java:149)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.CursorToMessage.lookupPerson(CursorToMessage.java:180)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.CursorToMessage.messageFromHashMap(CursorToMessage.java:126)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.CursorToMessage.cursorToMessageArray(CursorToMessage.java:101)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.SmsSyncService.backup(SmsSyncService.java:313)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.SmsSyncService.access$2(SmsSyncService.java:239)
04-11 13:37:45.624: ERROR/AndroidRuntime(1147):     at
tv.studer.smssync.SmsSyncService$1.run(SmsSyncService.java:156)

Original issue reported on code.google.com by hheimbue...@gmail.com on 11 Apr 2010 at 11:44

GoogleCodeExporter commented 8 years ago
Deleting all messages from and to this contact allowed me to proceed backing 
up. I
had to repeat this with another two contacts to complete the backup.

I can't really determine what these contacts or messages have in common with 
each
other, but not with those contacts/messages that could be backed up. But I 
might be
able to confirm or disconfirm theories.

Original comment by hheimbue...@gmail.com on 11 Apr 2010 at 11:54

GoogleCodeExporter commented 8 years ago
I already discovered this bug and fixed it in my patch attached to issue 31! 
Sorry
for putting that in that other patch, but it seemed too small a problem to open 
its
own issue ;)
This is caused by telephone numbers containing slashes. What my patch does is 
filter
out all slashes from a number and then search for it. Otherwise the search gets 
confused.

Original comment by felix.kn...@googlemail.com on 21 Apr 2010 at 5:19

GoogleCodeExporter commented 8 years ago
Oh, and this is probably a duplicate of issue 72

Original comment by felix.kn...@googlemail.com on 21 Apr 2010 at 5:24

GoogleCodeExporter commented 8 years ago
How can a crash bug be 'too small a problem'. ;) But I see what you mean.

I can confirm that it looks like a duplicate of issue 72. I currently don't 
have the
time to make my own build, but I might be able to restore the offending 
messages and
retest when a new build is released.

Original comment by hheimbue...@gmail.com on 21 Apr 2010 at 6:14