Chrome Uncaught TypeError: Cannot read properties of undefined (reading '1')

[adamtheapiguy]

Hey guys,

I get the below error in chrome sometime when I click on an item in the drop-down list of autoComplete , any ideas?

Error Text:

autoComplete.js:333 Uncaught TypeError: Cannot read properties of undefined (reading '1')
at feedback (autoComplete.js:333:28)
at select (autoComplete.js:413:5)
at click (autoComplete.js:422:7)
at HTMLUListElement.click$1 (autoComplete.js:508:11)

[HeavenlyEntity]

Getting the same type of error. I even type cast the number to make sure its an integer but it still getting the same error.

[AdamAliAu]

In my case I found out that the response was not as expected. Was getting 429 errors. After fixing that all went well. You need to make sure in that call, the response was returned as expected.

[sanjay-tiwari-tfs]

Even I am also facing same issue, can anyone have any idea ?

[adamtheapiguy]

My issue was that json response structure was different than what I defined as it was error response. If you check your response you might see it is not what you defined in the config and that's why you get this error.

[sanjay-tiwari-tfs]

Hi @adamtheapiguy , as per our requirement we have modified json response to show some different design, can you please suggest how to fix this issue.

[adamtheapiguy]

I think The response need to match plugin config. Response cannot be dynamic for success and fail. So for example if you configured $.result for plugin to pick up the data, all responses (success or fail) must have $.result. If fail response has no $.result then you would get that error.

In my case I was getting the error when the response was 429 (too many requests) as this response has no data and the json path $.result was not in the response.

To fix it, I just increased the rate limit on the api to avoid 429 errors and configured plugin to slow down the speed of api call.

At least that was my experience. You might have a different issue.