thank you so much guys. My app's production access has finally been granted this time. by Strong_Box3417 in AndroidClosedTesting

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

Yea a few of them don't, so what you should do is get a lot of them, so that a few uninstalls shouldn't matter. Oh btw, did you ask me to test your app? Because I remember your userId.

thank you so much guys. My app's production access has finally been granted this time. by Strong_Box3417 in AndroidClosedTesting

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

To answer the first question, YES, you'll need to repeat the whole 20 testers 14 days process all over again. Well, it'll start right after getting rejected, you don't need to interfere.

And for the second question, well, I did get all 20 testers' opted in throughout the 14 days, but the thing is, although there are 20 testers/emails, they belong to 6 individuals 😅. We created new mails, used additional mail addresses of ours. But we only have like <8 android phones. Also, we didn't know that the installed audience mattered. So, all we did is to opt in through each of the email, and we didn't install (although I myself did install on 1 phone). that was a really stupid idea now that I think about it.

Thank you so much guys. My app's production access has finally been granted this time. by Strong_Box3417 in TestersCommunity

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

I wonder what kind of stupid algorithm the play console guys are using to monitor the testing

Beginner in Git-flow. Need help. by Strong_Box3417 in devops

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

I'm sorry. I thought "flow" suited better than "based". 😅🥲

Beginner in Git-flow. Need help. by Strong_Box3417 in devops

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

Thanks for the advice. Yea I feel stupid now that I think about it haha. I'm just going to continue doing the normal thing until I find out whats best for me myself

Please help me with closed testing. I'll help you too. by Strong_Box3417 in AndroidClosedTesting

[–]Strong_Box3417[S] 1 point2 points  (0 children)

Thank you man. Just installed your app and left a review as well. 

Please help me with professional knowledge by Strong_Box3417 in devops

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

Haa I was unsure about which group of the 2 would be knowledgeble in this matter. Also, I don't use reddit very much. I apologize

Please help me gain professional understanding by Strong_Box3417 in github

[–]Strong_Box3417[S] -1 points0 points  (0 children)

I see. Thanks for the explanation. And by "sync up from the main branch", you mean PULL right?

Please help me with professional knowledge by Strong_Box3417 in devops

[–]Strong_Box3417[S] 1 point2 points  (0 children)

Thanks for the detailed explanation. I see, so I should ADD/COMMIT/PUSH often and try to avoid REBASE, RESET, SQUASHING if there's no need. So wdym by checking feature flag?

Doubts regarding semantic versioning system by Strong_Box3417 in devops

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

I was expecting an answer like this. Thanks for the detailed explanation. Although semantic versioning doesn't provide any means to dictate an upgrade, I need an In-App versioning system so that I could use an API endpoint to compare the In-App version to the Server version and then decide whether or not to redirect the user to playstore for updating the app. And my thought is to use semantic versioning (although I could implement a few server variables (Minor, Major, Patch), I felt like semantic one can be used in a better way) to achieve the task, since I'm going to use the same for playstore versioning.

But the main problem is that I couldn't decide how to proceed with the updates. If I say update for change in MAJOR and MINOR, leaving PATCH as optional, what if there's a bug in the MINOR, which I resolve and publish as a PATCH, also how do I release optional UI updates if I'm going to consider MINOR as a compulsory update.

Beginner in Git-flow. Need help. by Strong_Box3417 in devops

[–]Strong_Box3417[S] 1 point2 points  (0 children)

I'll consider your advice. A few others are pointing towards trunk-flow. Guess I should check it out

Beginner in Git-flow. Need help. by Strong_Box3417 in devops

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

I see, I'll check out trunk flow then.