-
Notifications
You must be signed in to change notification settings - Fork 617
Removing sign in tester from checkForNewRelease #3397
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -252,9 +252,15 @@ public synchronized Task<AppDistributionRelease> checkForNewRelease() { | |
LogWrapper.getInstance().v("Response in progress"); | ||
return cachedCheckForNewReleaseTask; | ||
} | ||
if (!isTesterSignedIn()) { | ||
return Tasks.forException( | ||
new FirebaseAppDistributionException( | ||
Constants.ErrorMessages.AUTHENTICATION_ERROR, AUTHENTICATION_FAILURE)); | ||
} | ||
|
||
cachedCheckForNewReleaseTask = | ||
signInTester() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you remove the comment that starts on line 155? With this PR, we no longer need to qualify why we call signIn before calling checkForNewRelease There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. done |
||
.onSuccessTask(unused -> this.newReleaseFetcher.checkForNewRelease()) | ||
this.newReleaseFetcher | ||
.checkForNewRelease() | ||
.onSuccessTask( | ||
appDistributionReleaseInternal -> { | ||
setCachedNewRelease(appDistributionReleaseInternal); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the status works but I don't think the message is accurate. Could it be something like "Tester not signed in"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is "Failed to authenticate the tester" incorrect? The sentence seems pretty accurate. If the tester is not signed in you cannot authenticate them. This message is also used in getExceptionForHttpResponse in the testerAPiClient and the tester sign in manager. Changing it too "Tester not signed in" could work for those, but it doesn't fit as well as the current message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, maybe it's not technically inaccurate, but it's not very helpful. It's true we couldn't authenticate the user, but it's so vague that we're not helping them understand why or resolve the problem.
In the other cases you mention (we get back a 401, or we fail to get a FID) we might not even understand the reasons ourselves, so vague is probably OK. In this case though, we know the reason: the tester wasn't signed in. So I think we should say that in the error message.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is your thought to make a new status that is "Tester not signed in" or to change the message that is being shown in the other cases. In option two the other message is "Failed to authorize the tester". Which I am ok using for the generic cases if we don't make a new message