mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #333] WhatsApp Label still showing up #272
Labels
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 $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#272
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @JoshAshby on GitHub (Jul 3, 2013).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/333
My phone just updated to the latest version of this in the market, and I have WhatsApp backup turned off, however the label in gmail is still getting created. This isn't a big problem for me, however it is a pretty big nuisance as I'm rather picky about my labels. From the way the GUI is setup, it disabled the label name editor for WhatsApp when that option to backup is turned off, as a result, I feel like the label shouldn't be created since the GUI option is disabled.
@agrberg commented on GitHub (Jul 3, 2013):
👍
@jberkel commented on GitHub (Jul 3, 2013):
will get fixed in the next update, sorry about that
@jberkel commented on GitHub (Jul 7, 2013):
fixed in
f81a126da9@jberkel commented on GitHub (Jul 7, 2013):
please try out the latest beta (1.5.4-BETA) (https://github.com/jberkel/sms-backup-plus#beta) and give feedback, should be fixed there.
@JoshAshby commented on GitHub (Jul 7, 2013):
Awesome, thanks! I'll try it out.