PeoplePicker returns no results with webAbsoluteUrl and ensureUser

[argofgra]

Category

[ ] Enhancement

[X] Bug

[ ] Question

Version

Please specify what version of the library you are using: [ 3.15.0 ]

Expected / Desired Behavior / Question

When setting webAbsoluteUrl prop to a different site and setting ensureUser = true results are expected to be returned.

Observed Behavior

No results are returned.

If both the webAbsoluteUrl prop is pointing to a different site than the current one, and ensureUser is set to true, no results are returned in the picker. Instead, the console shows the error: PeopleSearchService::searchTenant: error occured while fetching the users.

A deeper error says Cannot read properties of undefined (reading 'push'), which I've tracked down to PeopleSearchService.ensureUser:295. The object cachedLocalUsers assumes it already contains the webAbsoluteUrl as a key but it does not.

Steps to Reproduce

1. Add PeoplePicker control to a component
2. Provide a webAbsoluteUrl value that points at a different site than the current one
3. Set ensureUser={true}
4. Attempt to search for users in the people picker

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[github-actions]

Thank you for submitting your first issue to this project.

[NishkalankBezawada]

Hello @argofgra

I replicated the issue. I will be creating a PR on this soon.

@joelfmrodrigues or @AJIXuMuK kindly assign this to me.

Thanks,
Nishkalank Bezawada

[NishkalankBezawada]

Hello @argofgra

I have created a PR #1693 which will resolve the issue.

The solution is as below.

Solution

When checked, in the method ensureUser, the user object is pushed into this.cachedLocalUsers. But this is empty because the user is given webAbsoluteUrl to fetch the users from other site collection, for which it is erroring out as Cannot read properties of undefined (reading push) as shown in the below figure.

By checking if this.cachedLocalUsers and initializing it as empty array (as below), this is working as expected.

Screenshot with working example

Thanks,
Nishkalank Bezawada

[michaelmaillot]

Hi @argofgra & @NishkalankBezawada, fix has been merged to dev branch, it should be available soon in the next beta release!

Thanks to both of you 🙂