how to remove schema rule

[ahdat81]

so i was messing with schemas between the rule.json file and setting it programmatically. I'm trying to 'clear' it and start over. Right now my rules file is:

{
    "rules": {
        ".read": "auth !== null",
        ".write": "auth !== null"
    }
}

and programmically, im either not setting anything, or trying to set the node in quesiton to something empty

    await db.schema.set('scanner',{
      '*': '*'
     })
    await db.schema.set('scanner/$scannerid',{
     '*': '*'
    })

but when im trying to connect, im getting this error

scannerMgr() CRITICAL! init failed AceBaseRequestError: Access denied to path "scanner" by set rule
    at IncomingMessage.<anonymous> (C:\Websites\naked-charts-trading\node_modules\acebase-client\src\request\index.js:72:35)
    at IncomingMessage.emit (node:events:532:35)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: 'rule',
  request: {
    method: 'GET',
    protocol: 'http:',
    host: '0.0.0.0',
    port: '3005',
    path: '/data/naked_charts_trading_db/scanner',
    headers: { 'AceBase-Context': 'null' },
    body: ''
  },
  response: {
    statusCode: 403,
    statusMessage: 'Unauthorized',
    headers: {
      'x-powered-by': 'Express',
      'access-control-allow-origin': '*',
      'access-control-allow-methods': 'GET,PUT,POST,DELETE,OPTIONS',
      'access-control-allow-headers': 'Content-Type, Authorization, Content-Length, Accept, Origin, X-Requested-With, AceBase-Context',
      'access-control-expose-headers': 'Date, AceBase-Context',
      'cache-control': 'no-cache',
      'content-type': 'application/json; charset=utf-8',
      'content-length': '73',
      etag: 'W/"49-LkatVqaKhfd1LQQEPKe+cjkS0tw"',
      date: 'Sat, 30 Jul 2022 12:36:00 GMT',
      connection: 'close'
    },
    body: '{"code":"rule","message":"Access denied to path \\"scanner\\" by set rule"}'
  }
}

thoughts?

[appy-one]

Is your client signed in?

[ahdat81]

oof you're right, db was checked for connection but not sign in. my mistake