starred/sms-backup-plus-jberkel
1
0
Fork 0
mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-25 17:05:59 +03:00
Code Issues 181 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #525] crashing after upgrade from 1.5.6-beta5 to 1.5.8 #444

New issue
Closed
opened 2026-02-26 01:30:35 +03:00 by kerem · 11 comments
kerem commented 2026-02-26 01:30:35 +03:00
Owner
Copy link

Originally created by @nomwerp on GitHub (Jan 18, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/525

any idea?

I/Timeline(  927): Timeline: Activity_launch_request id:com.zegoggles.smssync time:40687
I/ActivityManager(  588): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.zegoggles.smssync/.activity.MainActivity} from pid 927
I/ActivityManager(  588): Start proc com.zegoggles.smssync for activity com.zegoggles.smssync/.activity.MainActivity: pid=1936 uid=10067 gids={50067, 3003, 1028, 1015}
D/ActivityThread( 1936): handleBindApplication:com.zegoggles.smssync
D/SMSBackup+( 1936): onResume()
I/ActivityManager(  588): Displayed com.zegoggles.smssync/.activity.MainActivity: +546ms
I/Timeline(  588): Timeline: Activity_windows_visible id: ActivityRecord{41e698c8 u0 com.zegoggles.smssync/.activity.MainActivity t2} time:41433
D/SMSBackup+( 1936): using new contacts API
D/SMSBackup+( 1936): insecure store uri specified, trusting ALL certificates
E/AndroidRuntime( 1936): Process: com.zegoggles.smssync, PID: 1936
E/AndroidRuntime( 1936):    at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60)
E/AndroidRuntime( 1936):    at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102)
E/AndroidRuntime( 1936):    at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105)
E/AndroidRuntime( 1936):    at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87)
E/AndroidRuntime( 1936):    at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87)
W/ActivityManager(  588):   Force finishing activity com.zegoggles.smssync/.activity.MainActivity
W/ActivityManager(  588): Activity pause timeout for ActivityRecord{41e698c8 u0 com.zegoggles.smssync/.activity.MainActivity t2 f}
I/ActivityManager(  588): Process com.zegoggles.smssync (pid 1936) has died.
W/ActivityManager(  588): Scheduling restart of crashed service com.zegoggles.smssync/.service.SmsBackupService in 4028ms
I/WindowState(  588): WIN DEATH: Window{421f2e08 u0 com.zegoggles.smssync/com.zegoggles.smssync.activity.MainActivity}
I/ActivityManager(  588): Start proc com.zegoggles.smssync for service com.zegoggles.smssync/.service.SmsBackupService: pid=2173 uid=10067 gids={50067, 3003, 1028, 1015}
D/ActivityThread( 2173): handleBindApplication:com.zegoggles.smssync
D/SMSBackup+( 2173): using new contacts API
D/SMSBackup+( 2173): insecure store uri specified, trusting ALL certificates
E/AndroidRuntime( 2173): Process: com.zegoggles.smssync, PID: 2173
E/AndroidRuntime( 2173):    at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60)
E/AndroidRuntime( 2173):    at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102)
E/AndroidRuntime( 2173):    at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105)
E/AndroidRuntime( 2173):    at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87)
E/AndroidRuntime( 2173):    at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87)
I/ActivityManager(  588): Process com.zegoggles.smssync (pid 2173) has died.
W/ActivityManager(  588): Service crashed 2 times, stopping: ServiceRecord{41ea3ea8 u0 ```
Originally created by @nomwerp on GitHub (Jan 18, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/525 any idea? `````` I/Timeline( 927): Timeline: Activity_launch_request id:com.zegoggles.smssync time:40687 I/ActivityManager( 588): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.zegoggles.smssync/.activity.MainActivity} from pid 927 I/ActivityManager( 588): Start proc com.zegoggles.smssync for activity com.zegoggles.smssync/.activity.MainActivity: pid=1936 uid=10067 gids={50067, 3003, 1028, 1015} D/ActivityThread( 1936): handleBindApplication:com.zegoggles.smssync D/SMSBackup+( 1936): onResume() I/ActivityManager( 588): Displayed com.zegoggles.smssync/.activity.MainActivity: +546ms I/Timeline( 588): Timeline: Activity_windows_visible id: ActivityRecord{41e698c8 u0 com.zegoggles.smssync/.activity.MainActivity t2} time:41433 D/SMSBackup+( 1936): using new contacts API D/SMSBackup+( 1936): insecure store uri specified, trusting ALL certificates E/AndroidRuntime( 1936): Process: com.zegoggles.smssync, PID: 1936 E/AndroidRuntime( 1936): at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60) E/AndroidRuntime( 1936): at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102) E/AndroidRuntime( 1936): at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105) E/AndroidRuntime( 1936): at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87) E/AndroidRuntime( 1936): at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87) W/ActivityManager( 588): Force finishing activity com.zegoggles.smssync/.activity.MainActivity W/ActivityManager( 588): Activity pause timeout for ActivityRecord{41e698c8 u0 com.zegoggles.smssync/.activity.MainActivity t2 f} I/ActivityManager( 588): Process com.zegoggles.smssync (pid 1936) has died. W/ActivityManager( 588): Scheduling restart of crashed service com.zegoggles.smssync/.service.SmsBackupService in 4028ms I/WindowState( 588): WIN DEATH: Window{421f2e08 u0 com.zegoggles.smssync/com.zegoggles.smssync.activity.MainActivity} I/ActivityManager( 588): Start proc com.zegoggles.smssync for service com.zegoggles.smssync/.service.SmsBackupService: pid=2173 uid=10067 gids={50067, 3003, 1028, 1015} D/ActivityThread( 2173): handleBindApplication:com.zegoggles.smssync D/SMSBackup+( 2173): using new contacts API D/SMSBackup+( 2173): insecure store uri specified, trusting ALL certificates E/AndroidRuntime( 2173): Process: com.zegoggles.smssync, PID: 2173 E/AndroidRuntime( 2173): at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60) E/AndroidRuntime( 2173): at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102) E/AndroidRuntime( 2173): at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105) E/AndroidRuntime( 2173): at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87) E/AndroidRuntime( 2173): at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87) I/ActivityManager( 588): Process com.zegoggles.smssync (pid 2173) has died. W/ActivityManager( 588): Service crashed 2 times, stopping: ServiceRecord{41ea3ea8 u0 ``` ``````
kerem 2026-02-26 01:30:35 +03:00
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jan 18, 2015):

Somehow the crash reason is obscured in this stacktrace, is there anything else in the logs ?

<!-- gh-comment-id:70412707 --> @jberkel commented on GitHub (Jan 18, 2015): Somehow the crash reason is obscured in this stacktrace, is there anything else in the logs ?
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@nomwerp commented on GitHub (Jan 18, 2015):

sorry was filtering on "SMS" here is the full log:
issue seems to be Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init> this the build from f-doird maybe something went wrong there?

(crash happens when pressing "backup")

I/ActivityManager(  588): Start proc com.zegoggles.smssync for service com.zegoggles.smssync/.service.SmsBackupService: pid=10129 uid=10067 gids={50067, 3003, 1028, 1015}
I/dalvikvm(10129): Enabling JNI app bug workarounds for target SDK version 10...
D/ActivityThread(10129): handleBindApplication:com.zegoggles.smssync
D/ActivityThread(10129): setTargetHeapUtilization:0.75
D/ActivityThread(10129): setTargetHeapMinFree:2097152
D/SMSBackup+(10129): using new contacts API
W/dalvikvm(10129): VFY: unable to resolve static field 2284 (DEFAULT) in Lorg/apache/james/mime4j/field/address/AddressBuilder;
D/dalvikvm(10129): VFY: replacing opcode 0x62 at 0x000f
E/dalvikvm(10129): Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init>
W/dalvikvm(10129): VFY: unable to resolve new-instance 133 (Lcom/beetstra/jutf7/CharsetProvider;) in Lcom/fsck/k9/mail/store/imap/ImapStore;
D/dalvikvm(10129): VFY: replacing opcode 0x22 at 0x004a
D/dalvikvm(10129): DexOpt: unable to opt direct call 0x013f at 0x4c in Lcom/fsck/k9/mail/store/imap/ImapStore;.<init>
D/SMSBackup+(10129): insecure store uri specified, trusting ALL certificates
D/AndroidRuntime(10129): Shutting down VM
W/dalvikvm(10129): threadid=1: thread exiting with uncaught exception (group=0x418d9ce0)
E/AndroidRuntime(10129): FATAL EXCEPTION: main
E/AndroidRuntime(10129): Process: com.zegoggles.smssync, PID: 10129
E/AndroidRuntime(10129): java.lang.NoClassDefFoundError: com.beetstra.jutf7.CharsetProvider
E/AndroidRuntime(10129):    at com.fsck.k9.mail.store.imap.ImapStore.<init>(ImapStore.java:356)
E/AndroidRuntime(10129):    at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60)
E/AndroidRuntime(10129):    at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102)
E/AndroidRuntime(10129):    at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105)
E/AndroidRuntime(10129):    at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87)
E/AndroidRuntime(10129):    at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87)
E/AndroidRuntime(10129):    at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2726)
E/AndroidRuntime(10129):    at android.app.ActivityThread.access$2100(ActivityThread.java:144)
E/AndroidRuntime(10129):    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1302)
E/AndroidRuntime(10129):    at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(10129):    at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(10129):    at android.app.ActivityThread.main(ActivityThread.java:5146)
E/AndroidRuntime(10129):    at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(10129):    at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(10129):    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732)
E/AndroidRuntime(10129):    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566)
E/AndroidRuntime(10129):    at dalvik.system.NativeStart.main(Native Method)
W/InputMethodManagerService(  588): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42bf6158 attribute=null, token = android.os.BinderProxy@41dd3260
I/Process (10129): Sending signal. PID: 10129 SIG: 9
I/ActivityManager(  588): Process com.zegoggles.smssync (pid 10129) has died.
W/ActivityManager(  588): Service crashed 2 times, stopping: ServiceRecord{42ac0ac8 u0 com.zegoggles.smssync/.service.SmsBackupService}
W/GooglePlayServicesUtil( 1056): Google Play services is missing.
<!-- gh-comment-id:70416180 --> @nomwerp commented on GitHub (Jan 18, 2015): sorry was filtering on "SMS" here is the full log: issue seems to be `Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init>` this the build from f-doird maybe something went wrong there? (crash happens when pressing "backup") ``` I/ActivityManager( 588): Start proc com.zegoggles.smssync for service com.zegoggles.smssync/.service.SmsBackupService: pid=10129 uid=10067 gids={50067, 3003, 1028, 1015} I/dalvikvm(10129): Enabling JNI app bug workarounds for target SDK version 10... D/ActivityThread(10129): handleBindApplication:com.zegoggles.smssync D/ActivityThread(10129): setTargetHeapUtilization:0.75 D/ActivityThread(10129): setTargetHeapMinFree:2097152 D/SMSBackup+(10129): using new contacts API W/dalvikvm(10129): VFY: unable to resolve static field 2284 (DEFAULT) in Lorg/apache/james/mime4j/field/address/AddressBuilder; D/dalvikvm(10129): VFY: replacing opcode 0x62 at 0x000f E/dalvikvm(10129): Could not find class 'com.beetstra.jutf7.CharsetProvider', referenced from method com.fsck.k9.mail.store.imap.ImapStore.<init> W/dalvikvm(10129): VFY: unable to resolve new-instance 133 (Lcom/beetstra/jutf7/CharsetProvider;) in Lcom/fsck/k9/mail/store/imap/ImapStore; D/dalvikvm(10129): VFY: replacing opcode 0x22 at 0x004a D/dalvikvm(10129): DexOpt: unable to opt direct call 0x013f at 0x4c in Lcom/fsck/k9/mail/store/imap/ImapStore;.<init> D/SMSBackup+(10129): insecure store uri specified, trusting ALL certificates D/AndroidRuntime(10129): Shutting down VM W/dalvikvm(10129): threadid=1: thread exiting with uncaught exception (group=0x418d9ce0) E/AndroidRuntime(10129): FATAL EXCEPTION: main E/AndroidRuntime(10129): Process: com.zegoggles.smssync, PID: 10129 E/AndroidRuntime(10129): java.lang.NoClassDefFoundError: com.beetstra.jutf7.CharsetProvider E/AndroidRuntime(10129): at com.fsck.k9.mail.store.imap.ImapStore.<init>(ImapStore.java:356) E/AndroidRuntime(10129): at com.zegoggles.smssync.mail.BackupImapStore.<init>(BackupImapStore.java:60) E/AndroidRuntime(10129): at com.zegoggles.smssync.service.ServiceBase.getBackupImapStore(ServiceBase.java:102) E/AndroidRuntime(10129): at com.zegoggles.smssync.service.SmsBackupService.backup(SmsBackupService.java:105) E/AndroidRuntime(10129): at com.zegoggles.smssync.service.SmsBackupService.handleIntent(SmsBackupService.java:87) E/AndroidRuntime(10129): at com.zegoggles.smssync.service.ServiceBase.onStartCommand(ServiceBase.java:87) E/AndroidRuntime(10129): at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2726) E/AndroidRuntime(10129): at android.app.ActivityThread.access$2100(ActivityThread.java:144) E/AndroidRuntime(10129): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1302) E/AndroidRuntime(10129): at android.os.Handler.dispatchMessage(Handler.java:102) E/AndroidRuntime(10129): at android.os.Looper.loop(Looper.java:136) E/AndroidRuntime(10129): at android.app.ActivityThread.main(ActivityThread.java:5146) E/AndroidRuntime(10129): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(10129): at java.lang.reflect.Method.invoke(Method.java:515) E/AndroidRuntime(10129): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732) E/AndroidRuntime(10129): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566) E/AndroidRuntime(10129): at dalvik.system.NativeStart.main(Native Method) W/InputMethodManagerService( 588): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42bf6158 attribute=null, token = android.os.BinderProxy@41dd3260 I/Process (10129): Sending signal. PID: 10129 SIG: 9 I/ActivityManager( 588): Process com.zegoggles.smssync (pid 10129) has died. W/ActivityManager( 588): Service crashed 2 times, stopping: ServiceRecord{42ac0ac8 u0 com.zegoggles.smssync/.service.SmsBackupService} W/GooglePlayServicesUtil( 1056): Google Play services is missing. ```
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jan 18, 2015):

i think this is an f-droid issue: https://github.com/jberkel/sms-backup-plus/issues/523

cc @RealRancor

<!-- gh-comment-id:70417619 --> @jberkel commented on GitHub (Jan 18, 2015): i think this is an f-droid issue: https://github.com/jberkel/sms-backup-plus/issues/523 cc @RealRancor
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@nomwerp commented on GitHub (Jan 18, 2015):

yes definitely looks like it, thank for looking into it.

<!-- gh-comment-id:70417761 --> @nomwerp commented on GitHub (Jan 18, 2015): yes definitely looks like it, thank for looking into it.
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (Jan 18, 2015):

Thanks for the notification, disabling the update for now until we found a better way to build the k9libs.

<!-- gh-comment-id:70418011 --> @ghost commented on GitHub (Jan 18, 2015): Thanks for the notification, disabling the update for now until we found a better way to build the k9libs.
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@kLeZ commented on GitHub (Mar 13, 2015):

It is still happening. Anyone can provide some info on how to solve it?

<!-- gh-comment-id:79233732 --> @kLeZ commented on GitHub (Mar 13, 2015): It is still happening. Anyone can provide some info on how to solve it?
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Mar 13, 2015):

@kLeZ You have to uninstall and reinstall using f-droid

<!-- gh-comment-id:79234556 --> @jberkel commented on GitHub (Mar 13, 2015): @kLeZ You have to uninstall and reinstall using f-droid
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@kLeZ commented on GitHub (Mar 13, 2015):

I'm sorry, I think it's too late and I'm confusing your words... Did you meant that re-install the package solves the problem? I use f-droid as my sole package manager, thus I've already installed smsbackup+ from there.

<!-- gh-comment-id:79257189 --> @kLeZ commented on GitHub (Mar 13, 2015): I'm sorry, I think it's too late and I'm confusing your words... Did you meant that re-install the package solves the problem? I use f-droid as my sole package manager, thus I've already installed smsbackup+ from there.
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@ghost commented on GitHub (Mar 13, 2015):

@kLeZ
Yes, you need to uninstall the app on f-droid and then install it again.

<!-- gh-comment-id:79258068 --> @ghost commented on GitHub (Mar 13, 2015): @kLeZ Yes, you need to uninstall the app on f-droid and then install it again.
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Mar 13, 2015):

f-droid published a broken version, and they can't autoupdate people who are on the old version, so you have to reinstall

<!-- gh-comment-id:79258242 --> @jberkel commented on GitHub (Mar 13, 2015): f-droid published a broken version, and they can't autoupdate people who are on the old version, so you have to reinstall
kerem commented 2026-02-26 01:30:36 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Mar 13, 2015):

i'm going to publish a new version soon which should fix the problem in the future (it will force updates on f-droid)

<!-- gh-comment-id:79259017 --> @jberkel commented on GitHub (Mar 13, 2015): i'm going to publish a new version soon which should fix the problem in the future (it will force updates on f-droid)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
cyber1000-docker
multisim
update-build-process
gh-pages
jcrben-patch-1
workmanager
jcrben-patch-2
old-sms-backup
1.6.0-BETA2
1.6.0-BETA1
1.5.11
1.5.11-BETA22
1.5.11-BETA21
1.5.11-BETA20
1.5.11-BETA19
1.5.11-BETA18
1.5.11-BETA17
1.5.11-BETA16
1.5.11-BETA15
1.5.11-BETA14
1.5.11-BETA13
1.5.11-BETA12
1.5.11-BETA11
1.5.11-BETA10
1.5.11-BETA9
1.5.11-BETA8
1.5.11-BETA7
1.5.11-BETA6
1.5.11-BETA5
1.5.11-BETA4
1.5.11-BETA3
1.5.11-BETA2
1.5.11-BETA1
1.5.10
1.5.10-BETA1
1.5.9
1.5.9-BETA6
1.5.9-BETA5
1.5.9-BETA4
1.5.9-BETA3
1.5.9-BETA2
1.5.9-BETA1
1.5.8
1.5.8-BETA2
1.5.8-BETA1
1.5.7
1.5.7-BETA2
1.5.7-BETA1
1.5.6-DEBUG
1.5.6
1.5.6-RC1
1.5.6-BETA11
1.5.6-BETA10
1.5.6-BETA9
1.5.6-BETA8
1.5.6-BETA7
1.5.6-BETA6
1.5.6-BETA5
1.5.6-BETA4
1.5.6-BETA3
1.5.6-BETA2
1.5.6-BETA1
1.5.5
1.5.5-BETA2
1.5.5-BETA1
1.5.4
1.5.4-BETA2
1.5.4-BETA1
1.5.3
1.5.2
1.5.1
1.5.0
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.1
1.3.2
1.3
1.2
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1
1.0.11
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0
Labels
Clear labels   
AM+RCS

   
FAQ

   
awaiting response

   
backup

   
bespoke

   
bug

   
calendar

   
call log

   
cannot reproduce

   
cloudless

   
device-specific

   
documentation

   
dual- & multi-SIM

   
duplicate

   
feature-request

   
fixed in beta

   
good first issue

   
half-missing

   
help wanted

   
helpful

   
meta

   
misattribution

   
mms

   
other message sources

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
rejuvenation

   
restore

   
schedule

   
security

   
stale

   
task

   
thanks

   
v1.5.1

   
v1.5.10

   
v1.5.11

   
v1.5.2

   
v1.5.3

   
v1.5.3

   
v1.5.4

   
v1.5.4

   
v1.5.5

   
v1.5.5

   
v1.5.6

   
v1.5.7

   
v1.5.8

   
v1.5.9

   
v1.6β

   
xoauth

   
~$ bounty $~
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#444
No description provided.