Imminent removal from the Google Play Store

[jamie-mh]

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.

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]

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

[DevynMonroe]

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]

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]

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]

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]

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:

• There are restrictions in place for new Google Play accounts - I guess to prevent spam. Not sure how difficult this is to adhere to.
• Users will stop receiving updates and they won't be notified that the app is no longer available. To migrate, they would need to uninstall the old one, install the new one and restore a backup.

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]

@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]

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]

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

[icantremember]

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]

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

[DoctorMcKay]

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]

@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]

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]

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

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

[jacob153]

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]

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]

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]

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]

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]

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

[JVKeller]

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]

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]

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

[Lowburn2]

@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]

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

[nuttylmao]

@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]

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

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

[JVKeller]

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

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]

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]

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

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]

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

[smmcdonald]

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]

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.