-
-
Notifications
You must be signed in to change notification settings - Fork 45
Pm-fix direction issue with password , "null" issue, #3091
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
Conversation
| delivery.entityName = json.getString(META_ENTITY_NAME); | ||
| delivery.reason = json.getString(META_REASON); | ||
|
|
||
| delivery.reason = JsonExtensions.optStringSafe(json, META_REASON, ""); |
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 we want this to default to null, not empty string. Later we check for null and show pending flags instead when no reason is provided
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.
See here
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.
| delivery.entityName = json.getString(META_ENTITY_NAME); | ||
| delivery.reason = json.getString(META_REASON); | ||
|
|
||
| delivery.reason = JsonExtensions.optStringSafe(json, META_REASON,null); |
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.
formatting is off here.
| ((ConnectIdActivity)activity).forgotPassword=false; | ||
| ((ConnectIdActivity)activity).forgotPin=false; | ||
| SmsRetrieverClient client = SmsRetriever.getClient(getActivity());// starting the SmsRetriever API |
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 this something we missed during merge or an existing regression ?
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.
no i think this was existing flow this is nothing we have missed
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 mean it's not a regression with current beta ?
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.
It came up in nitin notice from there, i Have to reconfirm that is case in current beta or not because as per the code i have seen it should be existing bug because it is a special scenario when user is clicking back on secondary phone verification during recovery it happens only then
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.
if it's not a regression, I am fine with not fixing this.
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.
need ur final verdict that should remove this or remain as it is
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.
Just saw Mary's comment on https://dimagi.atlassian.net/browse/QA-7738 and given that we should not resolve it, I am worried this might open another bug here or there.
…llable DB column)
Product Description
Fixed qa bugs
QA-7735
https://dimagi.atlassian.net/browse/CCCT-607
https://dimagi.atlassian.net/browse/QA-7738
Technical Summary
Feature Flag
Safety Assurance
Safety story
Automated test coverage
QA Plan
Labels and Review