getsentry
TypeError: Cannot read properties of undefined (reading 'id')
Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
Steps to Reproduce
Go to User Feedback page. But actually it happens only with my user.
Expected Result
It loads
Actual Result
Product Area
User Feedback
Link
No response
DSN
No response
Version
24.3.0
![getsantry[bot] avatar](https://avatars.githubusercontent.com/in/66573?v=4 "Published by a pub.dev verified publisher"){kind=small}
The url in the screen shot is funny, it's got a subdomain and also /organizations/:orgSlug, but they don't match.
But more generally it looks like we're not checking for invalid responses from the issues & events endpoints.
I'm having the same issue, but the error on the frontend is slightly different:
TypeError: Cannot read properties of undefined (reading 'feedback')
The 400 (Bad Request) response is:
{"detail":"Invalid statsPeriod: ''"}
I'm not sure how else I can help, but please let me know if I can provide any more info
@MattPurland Are you on self hosted or saas? Can you paste the URL path + params? (omitting any project/org id/slugs)
@MattPurland Are you on self hosted or saas? Can you paste the URL path + params? (omitting any project/org id/slugs)
I'm on self-hosted, here's the URL:
http://sentry.domain.com/api/0/organizations/star/issues-count/?end=&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aunresolved%20&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aresolved%20&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aignored%20&queryReferrer=feedback_list_page&start=&statsPeriod=&utc=
end:
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aunresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aignored%20
queryReferrer: feedback_list_page
start:
statsPeriod:
utc:
Comparing this to saas I'm not sure what to make of it, but it also has the same problem initially - but manages to continue to make multiple requests to the same API endpoint and works as intended:
The first one fails, just like the self-hosted:
end:
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aunresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aignored%20
queryReferrer: feedback_list_page
start:
statsPeriod:
utc:
But continues with the following, which seems to work fine:
end:
project: 4505958713786368
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aunresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aresolved%20
query: issue.category%3Afeedback%20is%3Aunassigned%20is%3Aignored%20
queryReferrer: feedback_list_page
start:
statsPeriod: 14d
utc:
Followed by variations of the above, which all return successfully
This is way beyond me, but hopefully can help
The url in the screen shot is funny, it's got a subdomain and also
/organizations/:orgSlug, but they don't match.But more generally it looks like we're not checking for invalid responses from the issues & events endpoints.
Is it the lack of statsPeriod the problem @ryan953 ?
Hello I think we have a related issue.
TypeError: Cannot read properties of undefined (reading 'find')
console.js:36 TypeError: Cannot read properties of undefined (reading 'find')
at At (feedbackItem.tsx:31:26)
at oa (react-dom.production.min.js:167:137)
at Re (react-dom.production.min.js:290:337)
at a (react-dom.production.min.js:280:389)
at i (react-dom.production.min.js:280:320)
at n (react-dom.production.min.js:280:180)
at pi (react-dom.production.min.js:271:88)
at va (react-dom.production.min.js:273:300)
at Kr (react-dom.production.min.js:127:105)
at react-dom.production.min.js:267:273
And a 400 on this url:
/api/0/organizations/sentry/issues-count/?end=&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aunresolved%20&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aresolved%20&query=issue.category%3Afeedback%20is%3Aunassigned%20is%3Aignored%20&queryReferrer=feedback_list_page&start=&statsPeriod=&utc=
Response is:
{"detail":"Invalid statsPeriod: ''"}
Initially thought this PR would resolve the issue but it's unrelated: https://github.com/getsentry/sentry/pull/71278
Version: Sentry self-hosted v24.5.1
