Project search throws "cannot read properties" error after upgrade to v2032.2 (Build 12046)

[ShannonN]

Recently we upgraded to v2023.2.12046 and worked with support teams to address some unexpected data issues. Today we’re receiving reports that searches on the ‘Projects’ screen are generating a ‘TypeError: Cannot read properties of null (reading ‘toLowerCase’)’ error. Not sure if its related to yesterday’s fixes; however searching for Projects is broken.

[clare.martin]

Hey @ShannonN,

Thank you for contacting Octopus Support and sorry to see you are running into this issue, luckily we are aware of it and you can find more details on it including a workaround and a GitHub issue you can subscribe to in this forum post:

Project filter exception after v2023.2 upgrade

Hello! after upgrading our Octopus instance from v2023.1 to v2023.2 we are facing issues with the project filter. As soon as we type the second letter in the project filter box, without any project group selected, we get this exception as seen in the screenshots (same procedure lasts in an different error message between Firefox and Edge), also happens in private tabs. [edge] [ff] logs triggered with Firefox: 2023-06-15 10:14:16.2273 13052 147 ERROR TypeError: e is null 2023-06-15 1…

Hopefully that helps but reach out if you need anything further as we are always on hand to help.

Kind Regards,
Clare

[ShannonN]

Thanks Clare. We’ve deployed the build to our Dev instance and everything appears to be fine. I’ll reply on the thread if we find anything after our Production install.