-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WANTED: Google Play Testers #120
Comments
Update: Play Console shows me that there are already more than the needed 20 users, so thanks for everyone who opted-in :) |
FYI: I released |
Closed Testing has now been finished, just some more application forms to go for the release on Google Play. |
Get well soon. |
Awesome. I had no idea of this app until discovered it accidentally few days ago, so I couldn't have any idea of your way to Google Store. I'm glad you have found enough testers. |
Unfortunately, Google rejected my application for production access, I have no idea why exactly. This seems to happen to many developer, the requirements are very vague and arbitrary. This means we will have to do another Closed Test (which automatically starts if there are 20 testers opted-in, currently since 2 days) for another 14 days, after which I can apply again, but I dont know if I am going to have more luck then. So for anyone who wants to continue testing it via Google Play, it would be great if you do, I will release any new versions immediately to the closed testing as well as F-Droid and Github. Other than that I dont think there is much I can do other than hope that after the next Closed Testing Google will accept the 2nd application |
I'm in. Should I avoid references to Google apps (Keep in this case) when testing? ;) |
Who knows, maybe they dont want another competitor 😂 I guess one thing that would be good if you guys leave a review on google play in the next 14 days, maybe they want to see the testers actually provide feedback, since I dont think they will have a look into the Github issues here |
Done. Without reffering to any them particular apps. |
Didn't they include a rejection reason? Often ui elements or something hard to imagine is the reason? I never left the testing program . |
You get a very generic feedback: I have no idea, maybe they want me to do much more updates in those 14 days or whatever. |
FYI: I released |
FYI: I re-applied for production access on Google Play today 🙂 |
Good luck! 🫡 |
Update: Unfortunately, my 2nd application was also declined, with the same "reasoning" as before. I guess its just too few people with too little app usage and feedback via Google Play Store reviews. |
Oh god what a nightmare What the hell do they want? I reviewed the app on play store and send my sample feedback over the testers app I mean it can't just be that Makes no sense How a Dev could gather audience is there app is not on store in the first place 20 testers gathered and used the app what else? |
I have no idea. The funny thing is about a week ago I saw this: So at least the number of minimum testers is now decreased to 12. I also found some reddit threads from other developers who have no idea why their applications get rejected, seems to be a quite frustrating process. My best guess is they wanna see more tester engagement/feedback of some sort, but its not obvious to me what kind of metrics they use. For now I guess theres not much we can do about it, the internal testing will go automatically, in theory I can re-apply in 14 days if enough testers stay opted-in, but with christmas and new year coming up there wont be much developing from my part the next few weeks. If I release new versions I will continue to release them in the internal testing track on Google Play as well. |
I just deployed v6.3.0 to Google Play internal testing track, should be released in ~1 hour. Merry Christmas 🎄 |
I have this message when trying to join the google group
|
Oh interesting, this group was created from the https://www.testerscommunity.com/, but I guess they violated some google policy. @ippocratis @rafnov I am not sure if you have to join the new group, since you already signed into the closed testing before. FYI I just release a |
Who the h$ll reported the app as spam for f@ck shake? What's wrong with people? |
Found an update in google store via aurora store. 😁 It gives me good thoughts. 2 apps corresponding 😂 |
I just deployed v6.4.0 to Google Play internal testing track, should be released in ~1 hour Happy Weekend 🙂 |
No another reaction here but I would show: 😯😲😯 |
Omigod. I forgot to backup notes, but Droid-ify told me to uninstall newer version before installing older that was working fine. |
Automatic backups on saving note was suggested in #203, which I am working on |
FYI I released |
I just got an email from Google Play Support, NotallyX has been granted production access to Google Play 😳🎉 |
In order to be able to publish NotallyX on the Google Play Store, I have to do a
Closed Test
with at least 20 People opted-in for 14 days (see App testing requirements for new personal developer accounts)I have setup the
Closed Testing
for the upcomingv6.1
via a public Google Group NotallyX App, that means anyone who has joined this group (no further actions needed) can opt-in into the closed test.It works like this:
So it would be great if as many people as possible could use this opportunity to a) help me get the app ready to publish and obviously b) to get further feedback on the current version.
FYI: I cannot see any information about you or what you do in the app if you opt into the test.
The text was updated successfully, but these errors were encountered: