parse-server icon indicating copy to clipboard operation
parse-server copied to clipboard

Dashboard data browser not loading _User if a user with Twitter authdata exists

Open ashish-naik opened this issue 1 month ago • 6 comments

Issue Description

_User doesnt show data if a row exists with twitter auth data. I have a very old row with twitter auth data. Data browser not loading with data after i upgraded from v7.3.0 t0 8.2.5. Resolves if i delete the row. No issues in queries from client code.

Server

  • Parse Server version: 8.2.5
  • Operating system: macOS/Linux Docker
  • Local and or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): Local and Digital ocean

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: 8.0.15
  • Local (Community edition) and Atlas

Client Not applicable for the issue

Logs

Common on local and Digital Ocean,MongoDB Atlas

at TwitterAuthAdapter.validateOptions (/parse/node_modules/parse-server/lib/Adapters/Auth/twitter.js:81:13)
at loadAuthAdapter (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:162:13)
at getValidatorForProvider (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:182:25)
at /parse/node_modules/parse-server/lib/Adapters/Auth/index.js:202:27
at Array.map (<anonymous>)
at Object.runAfterFind (/parse/node_modules/parse-server/lib/Adapters/Auth/index.js:201:32)
at /parse/node_modules/parse-server/lib/RestQuery.js:788:85
at Array.map (<anonymous>)
at _UnsafeRestQuery.handleAuthAdapters (/parse/node_modules/parse-server/lib/RestQuery.js:788:43)
at /parse/node_modules/parse-server/lib/RestQuery.js:259:17

Only on Digital ocean (Observed only once) error: bad regex: [object Object] {"code":107,"stack":"Error: bad regex: [object Object]\n at transformConstraint (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:787:17)\n at transformQueryKeyValue (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:351:33)\n at transformWhere (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoTransform.js:399:17)\n at MongoStorageAdapter.find (/parse/node_modules/parse-server/lib/Adapters/Storage/Mongo/MongoStorageAdapter.js:477:59)\n at /parse/node_modules/parse-server/lib/Controllers/DatabaseController.js:1050:33\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async _UnsafeRestQuery.runFind (/parse/node_modules/parse-server/lib/RestQuery.js:647:19)"}

package.json

{
	"name": "lendable",
	"version": "2.0.0",
	"main": "index.js",
	"repository": {
		"type": "git",
		"url": "https://github.com/ashish-naik/abc.git"
	},
	"license": "MIT",
	"dependencies": {
		"cors": "*",
		"cryptoutils": "*",
		"dotenv": "16.3.0",
		"form-data": "^4.0.0",
		"google-auth-library": "9.6.2",
		"jsonwebtoken": "*",
		"node-schedule": "latest",
		"parse-dashboard": "7.5.0",
		"parse-server": "8.2.5",
		"parse-server-api-mail-adapter": "4.1.0",
		"path": "*",
		"socket.io-client": "4.8.1",
		"underscore": "*",
		"zeptomail": "6.0.0"
	},
	"scripts": {
		"start": "node index.js"
	},
	"engines": {
		"node": "22.21.0",
		"npm": "11.6.2"
	}
}

ashish-naik avatar Oct 23 '25 07:10 ashish-naik

🚀 Thanks for opening this issue!

What is the auth data value? Please replace sensitive data with dummy data. Could it be related to the secure vs. insecure auth data? Please add a test that shows the issue, not based on Parse Dashboard but a Parse.Query or similar.

mtrezza avatar Oct 23 '25 23:10 mtrezza

_auth_data_twitter": { "auth_token": "token ", "id": "12345", "screen_name": "name", "auth_token_secret": "secret", "consumer_key": "key", "consumer_secret": "secret" },

ashish-naik avatar Oct 24 '25 04:10 ashish-naik

Please provide a Parse Query that replicates the issue.

mtrezza avatar Oct 24 '25 08:10 mtrezza

I noticed this in Dashboard data browser. Refresh doesnt load anything.

ashish-naik avatar Oct 24 '25 10:10 ashish-naik

This is the server repository, so if the issue is with Parse Server, it should be reproducible with a REST query or Parse.Query. If it cannot be reproduced then we may need to move this to the dashboard repository. The first step is to determine in which repository the bug lies. Given the logs you posted I assume on the server side.

mtrezza avatar Oct 24 '25 14:10 mtrezza