How do I make Pocket Casts work without a Google Play Store account?

Questions
1

TL;DR: Pocket Casts has stopped working on my Android phone. It is now required that I use the Google Play Store. How do I fix it?

I have been using Pocket Casts as my main podcast app for many years now, and I have done so without the Google Play Store. I have a regular stock Android phone on which I use the Aurora Store. It is not linked to any Google account.

I was listening to a podcast on Pocket Casts at one o’clock in the morning while I was doing dishes. I wake up today to see that it has stopped working, even though the app wasn’t updated overnight. I have no clue what happened. Every time I open it, I am redirected to the screen below:

POCKET CASTS_Requires Google Play
POCKET CASTS_Requires Google Play738×1456 23.7 KB

Any advice on why it’s doing that and how to fix it?

2

Try installing from their github releases.

If it still doesn’t work, I suggest antennapod as a good alternative.

3

Thanks for the advice. I tried that, and it didn’t work. In fact, something really weird happened. As I was about to install Pocket Casts’ APK from GitHub, I got the following warning:

GOOGLE PLAY PROTECT_Harmful App Blocked 001
GOOGLE PLAY PROTECT_Harmful App Blocked 001738×1425 63.7 KB

After I clicked install, I got a quasi-identical warning, asking me to confirm with my PIN that I wanted to install it. My phone also wouldn’t let me take a screenshot of that warning, so I had to take a picture with an old phone.

GOOGLE PLAY PROTECT_Harmful App Blocked 002
GOOGLE PLAY PROTECT_Harmful App Blocked 0021121×1582 218 KB

This leads me to believe that maybe the issue is with a recent update of Google Play Services and the Google Play Store.

  1. What do you think?

I also noticed something quite peculiar, and it’s that none of the alternative app stores (Aurora, Aptoide, APK Mirror, UptoDown) have the current latest version of Pocket Casts. Some are only one version behind, while others are several versions behind.

Moreover, the version numbers don’t match. Aurora’s latest version of Pocket Casts is v8.13 and was released in May 2026. UpToDown’s latest version is v.8.3 and was released in January 2026. Aptoide and APK Mirror’s latest version is v8.12 and was released in June 2026. This doesn’t make sense to me.

It’s one thing for alternative stores to not have the latest version of Pocket Casts. It’s another if the version numbers and release dates contradict each other and not match the release dates on the GitHub or the Google Play store.

I suspect this is something that happens with many apps on alternative stores.

  1. Does anybody have any idea why?

  2. Could it be a MicroG issue?

It’s my understanding that Pocket Casts is compatible with MicroG, which means I should be able to use it without the Google Play Store.

I’ve had MicroG installed on my phone since I bought it last year, and I did not have any issues until this morning.

I just installed the MicroG Repo into F-Droid just now, and it does not seem to make a difference either.

  1. Could it be an Android OS issue?

I have a Samsung Android phone running on Android 16/One UI 8.5. It was last previously updated in late May 2026, but I noticed a new update was available, and I updated it. It made no difference. Pocket Casts is still asking me to sign into the Google Play Store, even though it didn’t ask me that yesterday, or at any point since I have owned this phone.

4

Aurora and APK Mirror match at v8.13, Aptoide is still at v.8.12, but you are likely thinking that UpToDown means v8.30, not v8.3, there are ten minor versions after that.

5

It’s a feature that the app developer has enabled called PairIP: Prevent unauthorized redistribution with automatic protection and prompt users to get your app on Google Play - Play Console Help

6

Thanks for this. By app developer, do you mean the people behind Pocket Casts?

If yes, that doesn’t explain my situation because I didn’t update the app. I went to bed at 1am today. I was doing dishes between midnight and one and listening to a podcast on Pocket Casts. I woke up the same morning, around 7 am, and the app didn’t work.

What changed in those short hours?

As far as I can tell, nothing.

Did you mean Google when referring to the app developer?

If yes, that makes a little bit more sense. I heard about Google forcing app developers to register their ID with them, even if their apps are exclusively made available outside the Play Store.

However, I don’t remember doing anything in the last 24 hours that would have made Pocket Casts work on my phone.

7

By developers I mean the developers of the app and the page is injected by Google Play Services.

8

If you are correct, if Pocket Casts enabled this feature, why would they make their app available on their GitHub?

Because I had not updated Pocket Casts since last month, I don’t think this is a feature they recently enabled. If it was, the app would have stopped working a while back. It’s been literally less than 24 hours. Less than 24 hours ago, the app was working fine.

9

UPDATE: PROBLEM SOLVED!

I reached out to Pocket Casts’ support team, and they told me this bug is due to a change made by the Google Play Store and/or Google Play Services. So as I suspected, it wasn’t them. It was Google.

Although the issue has not been fixed in the latest stable release of Pocket Casts, it has been fixed in one of their beta releases, specifically v8.14-rc-2. I downloaded it from their GitHub, and it works. I am no longer prompted to sign into the Google Play Store. Thank God!

Note: Pocket Casts v8.14-rc-2 is not the latest beta release. It’s the penultimate one. But since their support team told me the issue was fixed in this release specifically, I erred on the side of caution by downloading v8.14-rc-2 instead of 8.14-rc-3, especially since Android doesn’t allow downloading older versions of an app while later ones are still installed. I have too many podcasts already downloaded, and I don’t want to have to download them again.

WHAT ABOUT OTHER APPS?

I suspect this is going to happen more often with apps, and I hope developers address it.
I know for a fact that 1Password does not officially support downloads outside the Google Play Store on Android, and never has.

On my Android phone I constantly experienced minor but still annoying bugs. And some of them are still present on my current phone. For example, every odd update, 1Password’s logo doesn’t appear properly. This is what it looks like now:

1PASSWORD_No Logo
1PASSWORD_No Logo738×169 17.4 KB

I am grateful to Pocket Casts for addressing this issue, because 1Password has no intention of doing it. They told me as much a couple of years ago. If their app works without a Google account, that’s great, but if it doesn’t they are not going to make any effort to address it. They’re practically a billion dollar company. Shame on them. Pocket Casts is worth infinitely less, and yet, they are making an effort.

1Password feels the exact same way about supporting their browser extension outside of Chrome, Brave, Firefox, MS Edge, and Safari. Many people are unaware of this, but just because an extension works in Chrome or Firefox, doesn’t necessarily mean it will work in one of their forks (Vivaldi/Waterfox).

We must compel developers who won’t support their apps outside Google and Apple’s ecosystems to change. Otherwise, this is going to keep happening. Even if we lose, let’s make our voices heard.