[Bug]: Search APIs not working properly...

[ct2irw]

Binner version

2.5.9

Operating System

Linux x64

Describe the bug and the steps to reproduce it

Digikey API is showing incorrect values, examples:

• If I search LIS2DU12TR I will get ECA-1VHG102
• If I search RC0402FR-0710KL I get the same ECA-1VHG102
• NRF52840-QIAA-R returns same thing...
• I wonder if it always returns that part...

Mouser API also has issues:

• LIS2DU12TR won't show any results - I've actually tested this on their api try it out test (https://api.mouser.com/api/docs/ui/index#/SearchApi/SearchApi_SearchByKeyword) and it returns the correct result.
• RC0402FR-0710KL works
• NRF52840-QIAA-R works

Would you like to attach your appsetings.json configuration?

I've just enabled (set to true) the digikey or the mouser integration depending on the actual tested api...

Screenshots or Videos (Optional, but they help!)

No response

Are you able to contribute a PR? (No is ok!)

None

[replaysMike]

That's a first, I'll investigate shortly

[ct2irw]

Thanks.

Some additional information that might help...

1. NRF52840-QIAA-F-R returned no results with Mouser and Digikey Enabled
2. I've additionally enabled octopart, and after that digikey returned the same cap from the previous report.
3. Disabled octopart and now digikey keeps reporting the same cap...

BR, Diogo

[grego1981]

Same here, I cannot create an app other than sandbox and I get the same cap for all searches.

[belotv]

You must first create an "Organization" and then create a "Production" API rather than a sandbox API.

[ct2irw]

You must first create an "Organization" and then create a "Production" API rather than a sandbox API.

Hi belotv, you're right with production it does work. I just had to do a "Forget Credentials" before actually setting up the production API.

Not sure if it makes sense to keep this as an open issue as it works with production, just not sandbox...

Thanks for the help!