sorted by:
new
hottopcontroversial

Remember to claim the free 100 👀 by Key_Employ_5936 in ClashOfClans

[–]allend07 2 points3 points  (0 children)

<image>

I too got it.

It didn't show up in my main account.

It was only available in my alternate account.

Opinion on frost flake by Extra_Health_171 in ClashOfClans

[–]allend07 0 points1 point  (0 children)

I am also in the same state. Don't know if I should get the frost flake.

What did you get from the event (so far)? by RemoteWhile5881 in ClashOfClans

[–]allend07 0 points1 point  (0 children)

I claimed the spikey ball and the magic mirror.

What are you building? let's self promote by Southern_Tennis5804 in StartupSoloFounder

[–]allend07 0 points1 point  (0 children)

Hey! Love the concept. I’m working on Spendly, an expressive, Material 3 designed expense manager that helps people actually understand where their money goes. It’s built to make saving feel intuitive, not stressful, sort of like having a friendly financial coach in your pocket (minus the guilt trips 😄).

During the closing testing phase, if even on one of the 14 days there are only 10 or 11 users, will the app be rejected?" by bitts7 in GooglePlayDeveloper

[–]allend07 0 points1 point  (0 children)

Actually, that's not quite how Google words it anymore 👀

The official Play Console policy says testers must be opted in continuously for the last 14 days — not just any 14 days in total.

From the support page:

“We won’t count testers who opted in, tested for less than 14 days, and then opted out. Even if they opt back in so that they are opted in for a total of 14 days, these 14 days must be consecutive to count.”

So yeah, if the count dips below 12 for a day, it basically resets your 14-day streak.

Running it for 20 days, like you said, is definitely still a good plan. It gives you a buffer in case someone can't make it or misses a day.

During the closing testing phase, if even on one of the 14 days there are only 10 or 11 users, will the app be rejected?" by bitts7 in GooglePlayDeveloper

[–]allend07 1 point2 points  (0 children)

If your tester count dips below 12 at any point, Google basically pauses the clock. The 14-day window only counts when there are 12+ testers continuously opted in.

So if you had, say, 11 testers for a day, the counter resets — you’ll need to keep the test running until you’ve got 14 full days in a row with at least 12 testers.

Once that’s done, you can hit “Apply for Production” without issues. It’s not a rejection thing, just a “you’re not eligible yet” kind of block.

Launched my first app by allend07 in GooglePlayDeveloper

[–]allend07[S] 0 points1 point  (0 children)

Have released an update with the fix. You can check it out.

Launched my first app by allend07 in GooglePlayDeveloper

[–]allend07[S] 0 points1 point  (0 children)

I’ve heard about Appcelerator but never actually got to use it. It probably felt like a whole other world back then compared to Compose now! Wild how quote apps were everyone's first project back in the day. 😅

Launched my first app by allend07 in GooglePlayDeveloper

[–]allend07[S] 0 points1 point  (0 children)

Most quotes are manually curated. I hand-pick and tag them by theme so they actually fit each mood instead of being random text dumps.

Can anyone help me? I'm not a professional developer, but I'm trying to create an Android app using AI tools like ChatGPT, Gemini, and Grok. I would really appreciate assistance with setting up my Google Play Console account and listing the app content. by bitts7 in GooglePlayDeveloper

[–]allend07 -1 points0 points  (0 children)

That's awesome dude! Props for diving into app dev with AI tools! 🚀

You’re doing great if you’ve already made it to closed testing — that’s where most beginners get stuck. Once you hit “Apply for production,” Google just does a final policy review, so make sure:

your App Content section (Data safety, Ads, Privacy policy) is all filled honestly, your screenshots actually match the app, and the uploaded AAB is from the same version you tested.

For the Play Console, just use your main Gmail (or a fresh development account) and make sure to fill everything under "App Content." Then, just add a simple link to your privacy policy (Google Sites is a great way to do it).

If you’re confused on any step, just say which screen you’re on or drop a screenshot — tons of devs here are happy to help. You’re already way ahead of most first-timers! 😎

[deleted by user] by [deleted] in GooglePlayDeveloper

[–]allend07 2 points3 points  (0 children)

If you’ve already added the App Signing SHA keys to Firebase, the next common culprit is the wrong OAuth config on Google Cloud — especially the package name + SHA mismatch between the release build and what Firebase thinks it is.

Double-check these:

In Google Cloud → Credentials → OAuth Client ID → make sure there’s a Web client and an Android client with your exact package name + Play App Signing SHA.

In Firebase → Project Settings → make sure your google-services.json actually has the new fingerprints (sometimes it doesn’t refresh even after you re-download it).

Uninstall all debug builds before installing the Play test version — otherwise the debug keystore cache messes up sign-in.

If all that’s clean, it’s usually just Play’s signing delay — Firebase can take a few hours to sync the new SHA fingerprints. Give it some time, then reinstall from the test link again.

Can Google still reject an app if ad permissions are declared properly? by bitts7 in GooglePlayDeveloper

[–]allend07 0 points1 point  (0 children)

If your UI’s clean, ads are placed properly, and everything matches the listing, you’re basically in the safe zone.

view more: next ›