Avatar Shop Returning Results of the Incorrect Asset Type

Reproduction Steps

I have found this problem whilst searching for Classic Clothing. Incorrect asset types are returned when you search for specific texts.

Repro:

local SearchParams = CatalogSearchParams.new()
SearchParams.SearchKeyword = 'Dress' --[[You can also try "Sweater", "Shorts", "Shoe" and probably more keywords]]
SearchParams.AssetTypes = {Enum.AvatarAssetType.Shirt,Enum.AvatarAssetType.Pants,Enum.AvatarAssetType.TShirt}
local CatalogPages = game:GetService('AvatarEditorService'):SearchCatalog(SearchParams)

for i,v in pairs(CatalogPages:GetCurrentPage()) do
    print(v.AssetType or (v.BundleType .. 'Bundle'))
end

AvatarEditorService must be enabled in the place/file you are testing in for this to work.

Expected Behavior

The CatalogPages should return results for items which match the AssetTypes provided into the CatalogSearchParams (in this case, only Shirt, TShirt and Pants)

Actual Behavior

When the CatalogSearchParam’s SearchKeyword is left to its default value, these are the asset types returned (as expected):

Normal Results

But when the SearchKeyword is set to some specific values (e.g. “Dress”, “Shorts”, “Shoe” or “Sweater”), the results are a mixture of other asset types, which were not specified in the CatalogSearchParams.AssetTypes property:

Inaccurate Results 2

Workaround

Setting CatalogSearchParams.MaxPrice to 10 will prevent this happening, but isn’t ideal as items over 10 Robux are no longer searchable.

Issue Area: Engine
Issue Type: Other
Impact: Moderate
Frequency: Constantly

5 Likes

Whoops, seems like this is a problem from the actual Website Avatar Shop - not just AvatarEditorService.

If you go to Avatar Shop > Clothing > Classic Shirts and search for “Dress” (Or click this link), you will get search results for items which are not Classic/2D clothing.


In this image you can see seasrch results for “Dress” in the “Classic Shirts” category, but we get no classic shirt results given to us at all.

2 Likes

Thanks for the report and sorry for the late response. We filed a ticket to our internal database and we’ll come back with updates when possible.

3 Likes

Thank you for your response!

I am not sure if it has been fixed just now, or prior to your reply, but the search results seem to be returning accurate results now :+1:

1 Like