[$50] Type Error 'Cannot read property 'version' of null'

[vikasrohit]

Observing following error in console for few projects:

TypeError: Cannot read property 'version' of null at ? (/main.cff9bc43004fa36c3860.js:134:91314) at s(/main.cff9bc43004fa36c3860.js:21:54731) at r.render(/main.cff9bc43004fa36c3860.js:67:36796) at d._renderValidatedComponentWithoutOwnerOrContext(/main.cff9bc43004fa36c3860.js:67:43229) at d._renderValidatedComponent(/main.cff9bc43004fa36c3860.js:67:43441) at d._updateRenderedComponent(/main.cff9bc43004fa36c3860.js:67:42660) at d._performComponentUpdate(/main.cff9bc43004fa36c3860.js:67:42461) at d.updateComponent(/main.cff9bc43004fa36c3860.js:67:41739) at d.receiveComponent(/main.cff9bc43004fa36c3860.js:67:40856) at Object.receiveComponent(/main.cff9bc43004fa36c3860.js:21:137806) at d._updateRenderedComponent(/main.cff9bc43004fa36c3860.js:67:42704) at d._performComponentUpdate(/main.cff9bc43004fa36c3860.js:67:42461) at d.updateComponent(/main.cff9bc43004fa36c3860.js:67:41739) at d.receiveComponent(/main.cff9bc43004fa36c3860.js:67:40856) at Object.receiveComponent(/main.cff9bc43004fa36c3860.js:21:137806) at d._updateRenderedComponent(/main.cff9bc43004fa36c3860.js:67:42704) at d._performComponentUpdate(/main.cff9bc43004fa36c3860.js:67:42461) at d.updateComponent(/main.cff9bc43004fa36c3860.js:67:41739) at d.performUpdateIfNecessary(/main.cff9bc43004fa36c3860.js:67:41072) at Object.performUpdateIfNecessary(/main.cff9bc43004fa36c3860.js:21:137988) at s(/main.cff9bc43004fa36c3860.js:21:24049) at r.perform(/main.cff9bc43004fa36c3860.js:21:199894) at o.perform(/main.cff9bc43004fa36c3860.js:21:199894) at o.perform(/main.cff9bc43004fa36c3860.js:21:25208) at Object.P [as flushBatchedUpdates](/main.cff9bc43004fa36c3860.js:21:25377) at r.closeAll(/main.cff9bc43004fa36c3860.js:21:200482) at r.perform(/main.cff9bc43004fa36c3860.js:21:199977) at Object.batchedUpdates(/main.cff9bc43004fa36c3860.js:67:49583) at Object.l [as enqueueUpdate](/main.cff9bc43004fa36c3860.js:21:24262) at r(/main.cff9bc43004fa36c3860.js:40:4763) at Object.enqueueSetState(/main.cff9bc43004fa36c3860.js:40:5895) at s.r.setState(/main.cff9bc43004fa36c3860.js:40:136947) at s.handleChange(/main.cff9bc43004fa36c3860.js:67:78833) at u(/main.cff9bc43004fa36c3860.js:40:167171) at u(/main.cff9bc43004fa36c3860.js:21:215253) at ? (/main.cff9bc43004fa36c3860.js:21:214092) at ? (/main.cff9bc43004fa36c3860.js:72:54531) at ? (/main.cff9bc43004fa36c3860.js:67:119675) at ? (/main.cff9bc43004fa36c3860.js:72:49213) at dispatch(/main.cff9bc43004fa36c3860.js:67:84933) at ? (/main.cff9bc43004fa36c3860.js:21:177046) at ? (/main.cff9bc43004fa36c3860.js:67:119666) at ? (/main.cff9bc43004fa36c3860.js:72:49213) at Object.getNotifications(/main.cff9bc43004fa36c3860.js:67:84251) at ? (/main.cff9bc43004fa36c3860.js:46:362848) at d(/3.17.0/raven.min.js:2:6417)

Exact line where error is raised
{snip} &&e.error.type===k.LOAD_PROJECT_FAILURE||("v3"!==e.project.version||e.projectTemplate)&&e.productTemplates.length>0)}),U=function(e){var t=e {snip}

https://sentry.io/topcoder/connect-app/issues/860833969/

[maxceem]

@vikasrohit This issue looks like have the same root as #2828 because I think the error happens at the same place.

As we don't have certain steps to reproduce the error in this issue, I guess we can fix another one and check if this issue still happens in some other conditions.

[vikasrohit]

@maxceem it seems the error is at this line and it is raised when project is null in props which can be there when there was an error in loading the project via api.

This error is still appearing in Sentry logs and recent event was logged a day ago.

[maxceem]

@vikasrohit we can try to play with it and simulate an error in project loading trying to reproduce it. By code, if an error happens during project loading, that line should not be called.

[maxceem]

@vikasrohit This issue might have been fixed by this PR #2871. Are there any new instances of this error after the previous release 2.4.10?

[vikasrohit]

@maxceem Yes, we have seen the issue in sentry after 2.4.10 release. However, it has been 14 days now since last occurrence of this issue. If it does not seems to workable for now, please exclude it from the CF, we can take it back in later.