Parse-server: TypeError: Cannot read property 'type' of undefined at dbTypeMatchesObjectType

Created on 4 Feb 2017  路  15Comments  路  Source: parse-community/parse-server

I was getting below error when i try to add a new column to my class in dashboard with [email protected]

2017-02-04T01:57:00.321Z - Uncaught internal server error. TypeError: Cannot read property 'type' of undefined
    at dbTypeMatchesObjectType (D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:309:13)
    at D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:691:16
    at process._tickDomainCallback (internal/process/next_tick.js:129:7) TypeError: Cannot read property 'type' of undefined
    at dbTypeMatchesObjectType (D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:309:13)
    at D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:691:16
    at process._tickDomainCallback (internal/process/next_tick.js:129:7)

Most helpful comment

@swar-it @adambarghouthi I will check with Azure documentdb team and update

All 15 comments

Can you provide the server logs when running with VERBOSE=1?

I'm experiencing this too

error: Uncaught internal server error. [TypeError: Cannot read property 'type' of undefined] TypeError: Cannot read property 'type' of undefined
at dbTypeMatchesObjectType (D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:307:13)
at D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:687:16
at process._tickDomainCallback (node.js:412:9)

TypeError: Cannot read property 'type' of undefined
at dbTypeMatchesObjectType (D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:307:13)
at D:\home\site\wwwroot\node_modules\parse-server\lib\Controllers\SchemaController.js:687:16
at process._tickDomainCallback (node.js:412:9)

@prashanthmadi are you on Azure also or no?

@adambarghouthi Yes. I will work on this issue today and update.

@prashanthmadi that'd be great. I'm also in contact with Azure since this issue started happening only after they fixed another issue I was having. So it could be on their end. We'll update this thread if anything

@adambarghouthi issue looks to be related with documentdb. Try with mlab mongodb and it would work...
I'm working with documentdb team and would update you soon.

FYI, I'm part of Azure Support.

@prashanthmadi Awesome!!! We're twisting the arms of documentDB it seems! If you have suggestions to improve our interface to make it easier to move forward (reducing the amount of forward breaking changes)

@prashanthmadi thank you! Will be waiting for the update

issue is identified and the Azure DocumentDB team will be deploying a new build starting tomorrow.

@prashanthmadi awesome thanks man!

I am still having this issue. Does anyone know if this has already been resolved by the Azure DocumentDB team or not?

@swar-it They were deploying the fix yesterday but I'm also still facing this issue

@swar-it @adambarghouthi I will check with Azure documentdb team and update

Hi @prashanthmadi did you get any update back?

DocumentDB Team has started deploying fix and it will complete all azure regions by Tuesday

A workaround would be to update the _SCHEMA document manually and add a new property using DocumentDB Studio (which directly talks to our backend).

If you have any queries, Feel Free to reach out [email protected]

Was this page helpful?
0 / 5 - 0 ratings

Related issues

kilabyte picture kilabyte  路  4Comments

jaydeep82 picture jaydeep82  路  4Comments

carjo422 picture carjo422  路  3Comments

darkprgrmmr picture darkprgrmmr  路  4Comments

dovewi picture dovewi  路  3Comments