SMS Backup+ removed from Google Play Store

al-right commented 10 months ago

Note added by @kurahaupo 2024-02-13:

As far as we can tell, @jberkel (Jan Berkel, the principal maintainer) has closed his Google PlayStore account (or allowed it to lapse). This has resulted the app being dropped from PlayStore, meaning it is now only available on F-Droid. Jan has also ceased active development of this project; if you would like to contribute to rejuvenating it, please see #1059.

Original submitted ticket follows:

Expected behaviour

Go to https://play.google.com/store/apps/details?id=com.zegoggles.smssync&hl=en&gl=US&pli=1 and you will be able to see SMS Backup+ in Google Play Store and install the app.

Actual behaviour

Go to https://play.google.com/store/apps/details?id=com.zegoggles.smssync&hl=en&gl=US&pli=1 and you will be greeted with the message:

We're sorry, the requested URL was not found on this server.

Also https://play.google.com/store/apps/developer?id=Jan+Berkel&hl=en&gl=US does no longer show dev info on Jan.

Reproduce by

No response

Android version

13 (2022)

Phone brand

Samsung

Phone model number

S23

SMS Backup+ version

v1.5.11

Messaging app

No response

Other details

Actually I run android 14 (but not possible to select in github). Re. SMS Backup+ version I simply select a random version as to be able to fill the bug form.

Is someone able to fix the problem or is there an easy way to install the app through some other trusted channel?

Thanks

danyfire commented 10 months ago

I'm confused the app is discontinued?

amuagarwal commented 10 months ago

It seems that app come under google store policy of non-maintance and security for OAuth issues. Now it will bck only once the app get some update and fix for OAuth issues as per new APIs

codebuk commented 9 months ago

As a workaround I have sideloaded and it works ok.

kurahaupo commented 9 months ago

This pushes up the priority of #1059.

If Jan is no longer contactable, that leaves me as one of the few with write access to this repo, but I still couldn't push to the PlayStore repo even if it still existed.

At least this gives a new project a clean slate with Google.

kurahaupo commented 9 months ago

@al-right thanks for the heads-up.

cluehaven commented 9 months ago

This pushes up the priority of #1059.

I imagine there are a fair few long time freeloaders (aka users) like me who would love to see this working again. My techie skills are modest and stale but I'm happy to be on videoconf/call/chat to review what help would make the task less of a burden and in that there may be something I can do (if only co-ordinating to find others to pitch in as wanted).

CaTeNdrE commented 9 months ago

I miss this app. Not sure what I can do to help but willing.

BenJewell commented 8 months ago

Just wanted to share an update on this effort.

My boyfriend is an Android developer and after the scheduler in this app broke, he tried writing me a new backup app, not realizing that the source code for this one was available.

After many hours of effort, he was unable to read and write RCS messages properly. Although we could modernize this app (probably more like a re-write since it's so old), it would not be worth the time and effort without RCS support, as SMS/MMS are slowly fading away.

Android seems to store RCS messages in its database in some weird way, possibly due to the end-to-end encryption. And there is not a documented method for interfacing with it.

Does anyone know of another open source backup app that DOES support RCS that we might be able to analyze? I don't know of any that are open source unfortunately.

al-right commented 8 months ago

@BenJewell Thanks to you and your boyfriends efforts! :) Very much appreciated. It seems as a larger project to get something going. Maybe some of the links below can be of some sort of help.

There seems to be these docs about RCS:
- https://www.gsma.com/futurenetworks/wp-content/uploads/2019/10/RCC.07-v11.0.pdf
- https://www.gsma.com/newsroom/wp-content/uploads//RCC.14-v8.0-5.pdf , from https://www.reddit.com/r/Android/comments/wm18td/stop_telling_people_that_rcs_is_an_open_standard/
"The RCS-e stack is an open source implementation of the Rich Communication Suite standards for Google Android platform. This implementation is compliant to GSMA RCS-e Blackbird standards. ...": https://github.com/android-rcs/rcsjta
"Messaging in RCS": https://realtimecommunication.wordpress.com/2014/11/14/messaging-in-rcs/
"What is RCS messaging? Everything you need to know about the SMS successor": https://www.digitaltrends.com/mobile/what-is-rcs-messaging/
Wiki-article on RCS: https://en.wikipedia.org/wiki/Rich_Communication_Services

chadcancode commented 8 months ago

For me, this will still backup when manually initiated. I would love to see the scheduler working again. There appears to be a 3rd party approach to triggering the backup by broadcast intents but I don't know how to trigger these.

kurahaupo commented 8 months ago

@BenJewell I spent a long time looking into RCS support options, and (at the time) searching for "RCS API" always took me to pages offering server side support (usually for a fee), intended for companies to send bulk RCS messages without actually using a phone at all.

It became obvious that Google simply don't provide a new API to deal with RCS messages on a phone, but the consensus (among the very few with any technical information) seemed to be RCS messages were accessible using the existing Android API for dealing with SMS and MMS messages.

From the links provided by @al-right it appears that that's only partly correct; we need an interpretation layer over the top; it's not clear whether SMS-Backup actually needs such a layer, since it's not presenting messages, merely storing them.

(Personally I've been leaving RCS turned off on my phone precisely to ensure that all my messages continue to be backed up until this is sorted.)

I would like to see a wider community effort rather than get stuck again with a single developer who goes silent. We need a new architecture to support a range of related tasks:

back-up and restoration (note that backing up a phone to a Google account now covers this use case, but that does not suit everyone);
treating phone logs as "just another message type";
record phone calls (probably using a separate app, since it would have to be gated by jurisdiction to be legal) and link them to the relevant phone log entries;
allowing messages to be stored in various ways, including (as now) any IMAP account (including GMail), but as future options, re-enabling XOAuth access to GMail, and building a capability to store messages locally on the phone, or forwarded by SMTP. Also allow messages to be saved into a calendar, selectable by message type.
allowing a unified archive search of sent and received SMS, MMS, & RCS messages alongside email and perhaps other message types (despite its name, that's actually the principal use-case for many existing users of SMS-Backup+, including myself).

opello commented 7 months ago

FYI, Re: RCS: #1097 -- I haven't tested it, read through it when I saw it and it seemed pretty good though, for whatever that's worth.

Mibou commented 6 months ago

Sad that it's been removed from Google Play, I've been using it for years and discovered it was removed after my phone got stole and that I tried to reinstall the app on a new phone. Reinstalled the app from F-droid, works perfectly, thanks for the tip.

BacchusFLT commented 2 months ago

Never paying for the app, never submitting any relevant change requests, and still using it, I am fully aware that I am in no position to request anything. Just humbly ask.

It's just that I have given up only using my corporate SIM in my private phone whereas using an eSIM for my private subscription in my corporate phone works fine. With the catch that the corporate phone is device managed where a policy blocks side loading. So SMS Backup+ not being on Google Play is a brick wall type of problem for me.

Any hope that anyone would make the effort to remove the obstructing parts and repost it?

tamarw commented 1 month ago

The primary issue here is that on September 30th, which is 22 days away, app passwords will not longer work. And therefore we have no choice but to use oauth.

However, Jan is gone and it seems that nobody is able to replicate the code. I know I can't and I know I'd be willing to pay for it because I am highly dependent upon searching my emails for communications and use the search to find call and MMS logs more often than not.

So we could all be sideloading the app, but we have less than 4 weeks before this app will no longer work for any of us.

I really hope somebody can realize how important this is and hopefully come up with an application that does the same thing leveraging oAuth. I honestly do not understand why Jan stopped supporting oauth and became dependent on app passwords, but that was a frustration in itself many years ago. (I've been a user forever.)

Let's hope we can get something soon, I am going to be completely lost without this app. It is among my top apps that I'm completely dependent upon.

sshaikh commented 1 month ago

Do you have a source for that? My understanding is that account username and password access will cease to function via third party apps. But generated "app passwords" will still work. Would appreciate a confirmation!

tamarw commented 1 month ago

I'm not sure what the difference is? Wouldn't that be basically the same thing?

https://www.forbes.com/sites/daveywinder/2024/09/05/new-gmail-app-access-password-deadline-you-have-4-weeks-to-comply/.

chadcancode commented 1 month ago

Do you have a source for that? My understanding is that account username and password access will cease to function via third party apps. But generated "app passwords" will still work. Would appreciate a confirmation!

This is my understanding as well. Some article I read even suggested app passwords as a workaround. I'm hoping Google doesn't remove that support as well.

sshaikh commented 1 month ago

I'm not sure what the difference is? Wouldn't that be basically the same thing?

https://www.forbes.com/sites/daveywinder/2024/09/05/new-gmail-app-access-password-deadline-you-have-4-weeks-to-comply/.

No, what's going away is being able to use your name@gmail.com and password123 credentials to access your Gmail via an email client.

Going into your security settings and generating a unique password for an app to use Gmail is not going away (and how you should be using smsb+ already).

tamarw commented 1 month ago

Got it, thanks. I know it's a matter of time though. We need an oAuth alternative sooner rather than later.

gunamoi1 commented 3 weeks ago

As I understand, the requirement for OAuth is only for Gmail email accounts. Until recently I was still able to use SMSBackup with my personal server email address, which still accepts username/password and SSL. My problem is that my old phone finally crashed on Sunday, and since the app is no longer available on Play Store or Fdroid, I have no way to reinstall on my new phone. Can anyone tell me where I can find an apk of the most recent SMSBackup version, that I can manually install on the new phone? regards,

opello commented 3 weeks ago

@gunamoi1 Did you check the releases for this project?

https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.11

The version number matches that which I still have installed.

BenJewell commented 3 weeks ago

SMS Backup+ With RCS Fix.zip

This is the one I use... Someone added RCS backup support a while back.

opello commented 3 weeks ago

It looks like that's the SMS backup plus with RCS fix v2.apk.zip from #1097?

BenJewell commented 3 weeks ago

Yeah. I guess it would have been easier to just find that and link to it than to pull the APK off my phone.

gunamoi1 commented 3 weeks ago

@opello : Thanks for that link. I saw the source code but somehow missed the APK link. It's been over 10 years since I did an android app, and I wasn't sure I've still got the capability to do my own APK from source. But I've downloaded the 1.5.11 APK and installed on the new phone and it works exactly as it did on the old phone. Many thanks.

@BenJewell: Thanks for that. I don't currently need RCS, so I won't install that one. But I've downloaded and archived just in case. regards.

chadcancode commented 3 weeks ago

I didn't realize there was a newer, RCS version. I'm still running 1.5.11 and have had issues where my messages aren't grouped in the same threaded backup as the person I'm talking to. I'm curious now if this will fix it.

What's the upgrade path? If I just remove the old app and sideload the new apk, will it re-backup all my old messages or only new messages going forward? I prefer to not create a whole bunch of duplicates in GMail.

Also, I'm curious if there will be issues in the GMail login. I can't recall but I think I'm using a GMail app password combo with IMAP b/c iirc, OAuth in the app wasn't working. Is that still the workable route for new installs?

opello commented 3 weeks ago

I'm still running 1.5.11 and have had issues where my messages aren't grouped in the same threaded backup as the person I'm talking to.

My understanding is that the threading is fixed in the RCS version too, but I never made the jump to it to see. It was mentioned in d9ef19f543ea6577a685f31d2235e8dfb2eb4898 in a review comment.

I'm not sure what the upgrade path is beyond the signing issue mentioned in the pull request--since the APK is signed by a different key the OS won't let you "upgrade" as a security measure, so that seems more like uninstall/reinstall.

As I understand the login issue, it's not a problem because "app passwords" can still be used. It's been discussed in this issue along with the misunderstanding that app passwords might go away. If that affects new setup I'm not sure, it'd be worth trying in an emulator or something before abandoning an existing install. I just haven't gone down that path just yet. I'm just a fan/user here so all I have is what I've gleaned from these issues and pull requests.

locofocos commented 1 week ago

I'm the author of #1097. Honestly it's working great for me 😀 I have perfect backups across SMS, MMS, group MMS, RCS, etc. I compiled the latest code in that PR and attached a zip file here, but honestly you're trusting me, an internet stranger, a lot 🤷

The scheduling still works for me, on my pixel 3a running Android 10. Maybe it's broken in newer versions of Android, I don't know. Perhaps it will work if you keep your phone plugged in and connected to wifi.

Regarding app passwords vs oauth, I've been using this workaround for years: https://www.androidpolice.com/2019/08/12/sms-backup-is-now-broken-due-to-gmails-api-changes-but-theres-a-workaround/ and it's still working today. I hope that helps!

flyoffacliff commented 1 week ago

For what it's worth, the scheduling was broken for me in Android 13 and 14 in the last official release, but it's fixed in the version with the RCS fix. Been working flawlessly on Android 14 for months. :)

Thank you to whoever fixed it, lol.

jberkel / sms-backup-plus