mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #564] Remove whatsapp code from app #479
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#479
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 @jberkel on GitHub (Jun 12, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/564
@tatablack commented on GitHub (Jul 5, 2015):
@jberkel, would it be possible for you to add a comment to this thread with the rationale for this decision? I tried to find a discussion about it here and on G+ but couldn't find much. Thanks in advance.
@jberkel commented on GitHub (Jul 7, 2015):
@tatablack i understood that some users would be disappointed about this decision, it was not easy but makes more sense in the long run, i don't really want to support a feature which does not work for 95% of users. here's a repost of a comment on #434
@tatablack commented on GitHub (Jul 7, 2015):
Thanks, @jberkel .
Having to play catch-up with some other app (without being able to sync with their changes beforehand) is never nice, I agree. And I guess a fork is a good idea, let's hope someone picks it up. 👍
@nibelungen commented on GitHub (Sep 5, 2016):
Hey,
did this ever get picked up by a fork??
Tried to find it - with no success so far.
Best regards
@jberkel commented on GitHub (Sep 5, 2016):
@nibelungen don't think so! is it still possible to read whatsapp backups these days, or has it been fixed?
@nibelungen commented on GitHub (Sep 6, 2016):
Hi @jberkel - yes its still possible, but since some month the backup does not include images, maybe its caused by using foldermount?! Just got my new phone and will try it again, but have to use an titanium backup because it looks like whatsapp crypt extractor does not work at the moment.... Give some feedback later on it when im done withe the new device.
best regards
@nibelungen commented on GitHub (Sep 10, 2016):
Hey @jberkel,
After Backup of ~50000 messages (nearly all duplicates) i can confirm it still works.
But as mentioned above, media files are not backed up anymore. With or without foldermount. If you have some hint i will try it. But i also accept your decision if you wont support this.
Best regards,
andreas
@Destix commented on GitHub (Sep 21, 2017):
Hi @nibelungen have you found any solution to backup media files?
@kleisauke commented on GitHub (May 24, 2018):
As a workaround we reintroduced the WhatsApp-code in our fork. When you build the APK from our source you can backup WhatsApp-messages again, but needs assistance of another app to re-crypt the .crypt12 files of WhatsApp to .crypt (OmniCrypt will do).
https://github.com/andrieslouw/sms-backup-plus
Backing-up media files is not supported.
@nibelungen commented on GitHub (May 24, 2018):
Hi @kleisauke is there anything better than using the latest version that supports whatsapp?
Do you know why Backing-up media fails? It also occurs with the latest version that supports whatsapp.
best regards
@Conan179 commented on GitHub (Jun 29, 2019):
I have a litte problem with
https://github.com/andrieslouw/sms-backup-plus
Where can I report it? There is no issue section there.
(cand coose a Calender)