-
Notifications
You must be signed in to change notification settings - Fork 32
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
If logged in user doesn't have a first or last name in their profile, the form will fail to load if the app is configured to auto-populate fields using this information #532
Comments
@sumitzarkar could you please assess the level of effort to fix this issue? |
|
I unfortunately added my firstName and lastName to my user when testing and can no longer reproduce. It is really easy to reproduce in debug though, just remove the firstName or lastName property from the user object returned from REST. |
We are able to repro the case after deleting firstName and lastname from the object and we have fixed this issue. |
Dev Checklist
Impact Analysis Report
|
### Implemented - Esri#532
Delivery for Crowdsource Reporter AGOL10.2 - #532
This issue is related to #512. I hit this issue during testing in Enterprise, I was using a portal with IWA. I deployed Citizen Problem Reporter and logged-in using my esri account. When I attempted to submit a new report the form was blank and there were a couple console errors.
I found through troubleshooting that in the portals/self request that my logged in user did not have a first or last name, but the app had been configured to pull the first and last names of the logged in user into the form. It appears we are not checking if the properties exist on the user profile and is throwing an exception. It is difficult to replicate this because the UI doesn't allow you to create an account without a first and last name.
However, if you use on of the Enterprise 11 release machines with IWA authentication and deploy Citizen Problem Reporter you should be able to reproduce the issue.
The text was updated successfully, but these errors were encountered: