search

stratumauth / app

📱 Two-Factor Authentication (2FA) client for Android + Wear OS
https://stratumauth.com
GNU General Public License v3.0
3.15k stars 202 forks source link

Imminent removal from the Google Play Store #1162

Closed jamie-mh closed 1 month ago

jamie-mh commented 4 months ago

On the 3rd of September 2024, my Google Play developer account will be deleted by Google and Authenticator Pro will no longer be available on the Google Play store. In line with the new Play Store policy, unless I consent to publicly displaying my home address, I will no longer be able to publish apps.

image

The alternative is to register as an organisation, which involves renting a PO-box and a dedicated support phone number. Of course, this is unreasonable and unsustainable for a free app.

From September, Authenticator Pro will only be available through the F-Droid repos and from GitHub releases.

This is a heads-up for anyone wondering past this date.

OmarNazzal150 commented 4 months ago

Why is Authenticator Pro is getting removed from the Google Play Store 😢

DevynMonroe commented 4 months ago

Dear @jamie-mh,

Oh no! The main reason for this app is to not sell users' info, right? This is because your rating is higher than theirs and they want to intimidate. Like with all the alternative YT apps. It's ridiculous that they have to stomp out anyone who has something better than them. it's not like they don't own everything and that you have to succumb to using their play store. Oh well, we will promote everywhere else. I wouldn't want to be where the owners don't play fair anyways.

Always, L.

jfsawin commented 4 months ago

Does removal from the Play Store mean that Wear OS compatibility will break or be discontinued? I notice that the website's comparison says it's not supported in the F-Droid version. The Wear OS companion app is the only reason I chose to use Authenticator Pro.

MisterDams commented 4 months ago

Does removal from the Play Store mean that Wear OS compatibility will break or be discontinued?

WearOS app certainly needs to be signed to communicate. That actually is what makes Authenticator so great.

How much would you need for a PO-box ? Maybe we could help with the Donate button.

You could also contact a company or a non-profit organization, in France we have Framasoft that is a huge promoter of open source.

Edit : I read the policy, and as a personal developer, it indicates that only your country would be public and not the whole address (which is displayed for companies). At least in the French version (maybe our personal data are more protected by GDPR)

jpjonte commented 4 months ago

As @MisterDams said, according to Play Console help article (looks like a EU version of the article), Google Play will only show the country:

Google will display your legal name, your country (as per your legal address), and developer email address on Google Play. If you decide to monetize on Google Play then Google will display your full address.

I hope this calms your worries, @jamie-mh. If not, I respect your choice!

If you go through with the deletion, what will happen to the Wear OS app?

jamie-mh commented 4 months ago

The issue is that I've monetised apps on the account in the past. Despite them being unpublished, the rule applies to all apps, even to those created way before the policy was implemented. I've confirmed this with the Google Play developer support.

Since my account is tainted, the only option is to create a new one and republish the app under a different name. The app won't be removed from anyone's device though.

This sucks because of a few reasons:

I realise that Google Play is the only reasonable way to distribute the Wear OS app. You can sideload APKs but that's not exactly intuitive.

jpjonte commented 4 months ago

@jamie-mh I see, that's an unfortunate situation. I'd be fine with sideloading the Wear OS app, but I can see that others might be uncomfortable with that.

cheack commented 3 months ago

Did you already published your app to F-Droid? Maybe I missing something, but I'm unable to find it there.

upd: ah, sorry, found a repo - https://authenticatorpro.jmh.me/fdroid/repo/

fredgolightly commented 3 months ago

@jamie-mh Can the git release autoupdate from github or display a notification when there's an update?

icantremember commented 2 months ago

Any thoughts on allowing donations for PO box, etc? Hard for me to recommend this app when new users can't install it from the Play Store.

Thanks for all your work

Herman-n commented 2 months ago

What is the reason using a separated F-Droid repository instead of the "normal" F-Droid repository?

DoctorMcKay commented 2 months ago

I'm dealing with this myself on my own developer account. I believe you should be able to create a new unmonetized developer account and transfer the app to it. I'm happy to sponsor the registration fee for a new dev account if needed.

icantremember commented 2 months ago

@jamie-mh Can the git release autoupdate from github or display a notification when there's an update? You can use Obtanium. https://github.com/ImranR98/Obtainium

Seconding the recommendation of Obtanium. That's actually how I get and update Authenticator Pro, too.

icantremember commented 2 months ago

I'm dealing with this myself on my own developer account. I believe you should be able to create a new unmonetized developer account and transfer the app to it. I'm happy to sponsor the registration fee for a new dev account if needed.

No idea what the fee is but I'd be willing to contribute as well.

bahuma20 commented 2 months ago

Did someone already manage to sideload the app to WearOS without play store?

Struggling a little bit here... Is there some tutorial?

jacob153 commented 2 months ago

That kind of stinks, I was wondering why it was no longer installed on my device. Heads up for anyone that does have it installed via playstore, it may auto uninstall so make sure you have backups.

fredgolightly commented 2 months ago

That kind of stinks, I was wondering why it was no longer installed on my device. Heads up for anyone that does have it installed via playstore, it may auto uninstall so make sure you have backups.

Wow this is super scary if it auto uninstalls, does this actually happen?

cheack commented 2 months ago

That kind of stinks, I was wondering why it was no longer installed on my device. Heads up for anyone that does have it installed via playstore, it may auto uninstall so make sure you have backups.

I doubt it was removed automatically. From https://support.google.com/googleplay/answer/12246761?hl=en:

If an app is removed from Google Play, will the app be removed from my device? No, the app will not be removed from your device. You can continue to use the app, however you will not be able to update your app. If you remove the app from your device, you will not be able to redownload the app unless the developer is able to republish it to Google Play.

jacob153 commented 2 months ago

That kind of stinks, I was wondering why it was no longer installed on my device. Heads up for anyone that does have it installed via playstore, it may auto uninstall so make sure you have backups.

Wow this is super scary if it auto uninstalls, does this actually happen?

Mine did on my phone anyway, I had to re-download from my f-droid client and restore my backup. This also makes me wonder about the watch app and if there will be an easy way to download it or if it will have continued support. I personally use the watch app on a daily basis.

jacob153 commented 2 months ago

That kind of stinks, I was wondering why it was no longer installed on my device. Heads up for anyone that does have it installed via playstore, it may auto uninstall so make sure you have backups.

I doubt it was removed automatically. From https://support.google.com/googleplay/answer/12246761?hl=en:

If an app is removed from Google Play, will the app be removed from my device? No, the app will not be removed from your device. You can continue to use the app, however you will not be able to update your app. If you remove the app from your device, you will not be able to redownload the app unless the developer is able to republish it to Google Play.

I would assume the same. I am only posting my experience which is this morning I could no longer find the app installed on my device. I am the only person that has access to my device. There should be no reason an app should uninstall automatically, but it was clearly not installed on my phone(S24U) anymore and I did not remove it as I depend on it on a daily basis. Maybe I just ran into a bug, or something else has caused this strange behavior, but regardless of if it happened to me it could happen to others.

Edit: To clarify what I mean above, there are circumstances that the google play store may automatically remove an app from a device after it being removed from the google play store which includes actions of the developer, possible security concerns, users device policies, etc. Being an authentication app there could be the "security concerns", or because the dev isn't agreeing to the new policy(which I understand and support devs decision) it could fall under "developers actions". Where I mention users device policies and that I could possibly have had something else go wrong is I do have work policies installed to my phone that is required for security reasons by my work and it does monitor for valid apps and it could have possible decided that it was not a safe app to have installed.

fredgolightly commented 2 months ago

I've imported all my codes from here to 2fas and apart from grid view it's just as good.

JVKeller commented 2 months ago

Make a new account and make a "Pro" version of the app. Charge $1 or $2 for the Pro version (Or the watch app?!)!!

I think we'd all be happy to chip in to help you find a way to cover you on this!

geekthought commented 2 months ago

Please republish with a new account and just add a 15$ price tag. I'll gladly pay again for your app. Sure others will too...

nuttylmao commented 2 months ago

WearOS looks like it doesn't work anymore. I sideloaded the APK on my watch and I get the dreaded blue cloud.

Lowburn2 commented 2 months ago

@nuttylmao Make sure you're using the correct apks. I just got a new phone and ran into the same issue initially but all is working well now.

https://github.com/jamie-mh/AuthenticatorPro/releases/tag/1.25.2

You'll want the "me.jmh.authenticatorpro.apk" for your phone and "me.jmh.authenticatorpro.wearos.apk" for your watch.

JVKeller commented 2 months ago

WearOS looks like it doesn't work anymore. I sideloaded the APK on my watch and I get the dreaded blue cloud.

The phone app connection to the wearOS doesn't work on the fdroid or other version so make sure you grab the ones NOT labeled as such.

me.jmh.authenticatorpro.apk me.jmh.authenticatorpro.wearos.apk

image

nuttylmao commented 2 months ago

@nuttylmao Make sure you're using the correct apks. I just got a new phone and ran into the same issue initially but all is working well now.

https://github.com/jamie-mh/AuthenticatorPro/releases/tag/1.25.2

You'll want the "me.jmh.authenticatorpro.apk" for your phone and "me.jmh.authenticatorpro.wearos.apk" for your watch.

I'm almost positive that's what I did. I'm definitely using that APK for my watch because I just got a new watch today and it was the only way to get it on the watch since it's not on the Play Store anymore.

nuttylmao commented 2 months ago

WearOS looks like it doesn't work anymore. I sideloaded the APK on my watch and I get the dreaded blue cloud.

The phone app connection to the wearOS only works with the play store

image

It's not on the Play Store anymore which was my point.

JVKeller commented 2 months ago

WearOS looks like it doesn't work anymore. I sideloaded the APK on my watch and I get the dreaded blue cloud.

The phone app connection to the wearOS only works with the play store image

It's not on the Play Store anymore which was my point.

Yeah, I didn't word it quite right. I fix my comment.

I did have the same issue at first... I installed both and added the tile and saw the no connection cloud. BUT! Just now I OPENED THE APP on my watch, rather than just going to the tile, and all is fine.

Did you launch the app once after you installed it, before you went to the tile?

JVKeller commented 2 months ago

I'm dealing with this myself on my own developer account. I believe you should be able to create a new unmonetized developer account and transfer the app to it. I'm happy to sponsor the registration fee for a new dev account if needed.

No idea what the fee is but I'd be willing to contribute as well.

Looks like it's only $25 to register

@jamie-mh, have you decided what you'd like to do yet? We'll get your $25 back and then some! 🤘

nuttylmao commented 2 months ago

WearOS looks like it doesn't work anymore. I sideloaded the APK on my watch and I get the dreaded blue cloud.

The phone app connection to the wearOS only works with the play store image

It's not on the Play Store anymore which was my point.

Yeah, I didn't word it quite right. I fix my comment.

I did have the same issue at first... I installed both and added the tile and saw the no connection cloud. BUT! Just now I OPENED THE APP on my watch, rather than just going to the tile, and all is fine.

Did you launch the app once after you installed it, before you went to the tile?

I just installed the APK over the top of my Google Play install. As a last resort, I just uninstalled and reinstalled it and it works now!

jamie-mh commented 2 months ago

I have a new developer account now. I'm looking into what it takes to republish.

image
smmcdonald commented 2 months ago

Special thank you to @JVKeller and @nuttylmao for the steps to get the WearOS version working. I was about to lose my mind after getting a new smartwatch, as I rarely have my phone on me, but I almost always have my watch.

Here are the steps that worked for me:

  1. Create a backup file on the phone app.
  2. Download the APKs for the phone and watch here: https://github.com/jamie-mh/AuthenticatorPro/releases/tag/1.25.2 (me.jmh.authenticatorpro.apk and me.jmh.authenticatorpro.wearos.apk in my case). Note: it's easier with these steps to download the APK files on the smartphone rather than computer.
  3. Uninstall Authenticator Pro on both the phone and smartwatch.
  4. Install the primary APK (me.jmh.authenticatorpro.apk) on the phone.
  5. Restore the primary app using the backup file in step 1.
  6. Install the WearOS APK (me.jmh.authenticatorpro.wearos.apk) via sideload. I used Wear Installer 2. This requires knowledge of using Android wireless debugging.
  7. Open the Authenticator Pro app (not the tile) on the smartwatch. At this point the watch app loaded and successfully fetched the OTPs.

@jamie-mh Thank you very much for your work on this application. I want you to know that it is literally life-changing for me, and I'm sure for many others.

KlosiakMK commented 2 months ago

I have a new developer account now. I'm looking into what it takes to republish.

Good to hear. Today I had to reset my WearOS watch and wanted to download again the app but it wasn't there. Started to looking and found this posts thread. In general Google and its policies stinks. I am happy that you decided to create a new account there. Hope both Android and WearOS apps will be available there soon. Looking forward for that.

Good luck and cheers for the great job that you don with Authenticator Pro app.

jamie-mh commented 2 months ago

Hello everyone,

I've published a new version to my new Google Play account, and it's been approved. However, in line with Google's new app testing requirements, I must perform a closed test with at least 20 users for 14 days before the app becomes generally available.

For this, I will need your help. If you would like to test the app, the procedure is as follows:

  1. Join the testing Google Group
  2. Join the test using one of the following links: from Android: https://play.google.com/store/apps/details?id=com.stratumauth.app , from the Web: https://play.google.com/apps/testing/com.stratumauth.app
  3. Download the app and test for 14 days

For clarification: the package name is different, so it can be installed alongside the original app. And yes, the name of the app has changed for 2 reasons : (1) because of Google Play's "impersonation" policy and (2) many scam apps have similar names and, I get a lot of emails from people who confuse mine with them, so it's probably for the best.

Cheers

KlosiakMK commented 2 months ago

@jamie-mh I can help with testing. Can I import backup from the old app to the new one?

hokascha commented 2 months ago

Great, works. Does it already have the wear os companion?

DoctorMcKay commented 2 months ago

It's the same app, just with a different name. Backups from the old version import fine and it runs fine on WearOS, since it's the same app.

hokascha commented 2 months ago

Play Store didn't offer to install on the WearOS device when trying from my phone. Using the web play store works though.

blizbling commented 2 months ago

Hello is there a limitation with the link it's not working on my side i don't know if you have 20 people already

Thank You Capture d’écran 2024-09-25 132627 Capture d’écran 2024-09-25 132721

jamie-mh commented 2 months ago

Hello is there a limitation with the link it's not working on my side i don't know if you have 20 people already

Have you joined the Google Group? There is no limit.

blizbling commented 2 months ago

my mistake i had click the group didn't join it done thank you verry much of your time, your app help me alot in my day to day work

KlosiakMK commented 2 months ago

Joined a group too and installed Stratum app on my phone and WearOS watch. Let the testing begin ;)

I have restored my latest backup from the previous app and everything worked fine.

phbasler commented 2 months ago

Just to be sure: This is the same code as the previous play store deployment? So except for deployment/setup issues we shouldn't expect to find anything out of the ordinary?

jamie-mh commented 2 months ago

Just to be sure: This is the same code as the previous play store deployment? So except for deployment/setup issues we shouldn't expect to find anything out of the ordinary?

It's built from the repub branch. Same code base with stuff renamed and a few small tweaks.

JVKeller commented 2 months ago

@jamie-mh

Hey Jamie. So far so good. No issues to report other than you can only install the WearOS version with the Web version of Play. (you probably already knew that by now.)

Ran side by side for a day and now I've removed AP and running just the new app.

Before you start to get flooded with even more messages... Do you plan to migrate to a new Repo? We could start a discussion there to share updates...

KlosiakMK commented 2 months ago

Same here...tested today in the morning...codes given by new app worked as usual, everything works like on the old app. I have restored everything from the backup done on the old app.

myrddral commented 2 months ago

Woohoo, I have it up and running again on my phone and my freshly reset GW6 💚 A few hours ago I was quiet desperate about loosing the best feature of this app.

Sooo... is there anything we should do as testers (like feedback, reporting, whatever) or is it just a matter of using the app for at least the given period? @jamie-mh

Thank you for your work, really appreciate it! I meticulously migrate all my account's security to use 2FA (where applicable), meaning I have to reach for the authenticator at least 4-5 times on a daily basis but at random times. Ever since I've got my watch, I got so used to not having my phone on me all the time... but your app with the wearOS companion makes using 2FA painless :)

jamie-mh commented 2 months ago

Before you start to get flooded with even more messages... Do you plan to migrate to a new Repo? We could start a discussion there to share updates...

Here is fine, I'm not going to change the repo.

Sooo... is there anything we should do as testers (like feedback, reporting, whatever) or is it just a matter of using the app for at least the given period?

As far as I can tell, the requirement is just to have at least 20 people with the app installed for 14 days. If you have any issues, you can of course report them here.

image
Gravemind2015 commented 2 months ago

Joined the group, installed on my Samsung M51. Restored a fresh backup from Authenticator Pro (from Izzy), works perfectly fine so far. Huge thanks for keeping up with google's weird policies :-P. I'll be keeping it installed and updated until the app gets a full release at least.

I guess the name for the Izzy repo one would be changed as well, to streamline the naming scheme across Izzy and Play? Hopefully that goes smoothly as well.

P.S: I think it might be too late to mention this, considering I can't find the play store entry for Authenticator Pro already but what if a final update was pushed to google play users notifying them (via a dialog popup or something) that the app would be published under a new name and that users needed to manually migrate etc.? I am not aware of the whole procedure about re-publishing so if that required older one to be unpublished first somehow, then probably nothing can be done :-/