FIRESTORE (7.14.3) 内部断言失败:值必须未定义或 Uint8Array
Posted
技术标签:
【中文标题】FIRESTORE (7.14.3) 内部断言失败:值必须未定义或 Uint8Array【英文标题】:FIRESTORE (7.14.3) INTERNAL ASSERTION FAILED: value must be undefined or Uint8Array 【发布时间】:2020-09-06 21:45:00 【问题描述】:我的脚本不断引发此错误。我编写的代码用于测试 Firestore 安全规则。 我基本上想在向其添加 javascript 函数的同时测试我的 Firestore 安全性。可以在 firestore 控制台中编写规则并在那里保存它们,但我想使用 IDE - VS 代码。
我想知道如何修复“FIRESTORE (7.14.3) INTERNAL ASSERTION FAILED: value must be undefined or Uint8Array”。我已经更新了我的 npm 并尝试了我在 Github 上找到的答案,该答案说我要先安装“npm i jest-environment-uint8array”。它不起作用。我也尝试过使用“TextEncoder” 比如: var uint8array = new TextEncoder("utf-8").encode("Posts"); var string = new TextDecoder("utf-8").decode(uint8array); 它也没有奏效。如果你们能彻底回答我,我将非常感激,因为我只是一个新手。
我的测试代码是
const setup, teardown = require("./helpers");
describe("General Safety Rules", () =>
afterEach(async () =>
await teardown();
);
test("should deny a read to the posts collection", async () =>
const db = await setup();
const postsRef = db.collection("Posts");
await expect(postsRef.get()).toDeny();
);
);
我的助手 js 基本上完成了我的代码完成后的设置和拆卸。
const firebase = require("@firebase/testing");
const fs = require("fs");
module.exports.setup = async (auth, data) =>
const projectId = `rules-spec-$Date.now()`;
const app = firebase.initializeTestApp(
projectId,
auth
);
const db = app.firestore();
// Apply the test rules so we can write documents
await firebase.loadFirestoreRules(
projectId,
rules: fs.readFileSync("firestore-test.rules", "utf8")
);
// write mock documents if any
if (data)
for (const key in data)
const ref = db.doc(key); // This means the key should point directly to a document
await ref.set(data[key]);
// Apply the actual rules for the project
await firebase.loadFirestoreRules(
projectId,
rules: fs.readFileSync("firestore.rules", "utf8")
);
return db;
;
module.exports.teardown = async () =>
// Delete all apps currently running in the firebase simulated environment
Promise.all(firebase.apps().map(app => app.delete()));
;
错误是:
开玩笑./spec
(node:8200) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
FAIL spec/collections.spec.js (10.284 s)
General Safety Rules
× should deny a read to the posts collection (4598 ms)
× should deny a write to users even when logged in (131 ms)
● General Safety Rules › should deny a read to the posts collection
FIRESTORE (7.14.3) INTERNAL ASSERTION FAILED: value must be undefined or Uint8Array
at fail (node_modules/@firebase/firestore/src/util/assert.ts:39:9)
at hardAssert (node_modules/@firebase/firestore/src/util/assert.ts:53:5)
at JsonProtoSerializer.fromBytes (node_modules/@firebase/firestore/src/remote/serializer.ts:250:7)
at JsonProtoSerializer.fromWatchChange (node_modules/@firebase/firestore/src/remote/serializer.ts:431:32)
at PersistentListenStream.onMessage (node_modules/@firebase/firestore/src/remote/persistent_stream.ts:568:41)
at node_modules/@firebase/firestore/src/remote/persistent_stream.ts:448:21
at node_modules/@firebase/firestore/src/remote/persistent_stream.ts:501:18
at node_modules/@firebase/firestore/src/util/async_queue.ts:358:14
● General Safety Rules › should deny a write to users even when logged in
FIRESTORE (7.14.3) INTERNAL ASSERTION FAILED: value must be undefined or Uint8Array
at fail (node_modules/@firebase/firestore/src/util/assert.ts:39:9)
at hardAssert (node_modules/@firebase/firestore/src/util/assert.ts:53:5)
at JsonProtoSerializer.fromBytes (node_modules/@firebase/firestore/src/remote/serializer.ts:250:7)
at JsonProtoSerializer.fromWatchChange (node_modules/@firebase/firestore/src/remote/serializer.ts:431:32)
at PersistentListenStream.onMessage (node_modules/@firebase/firestore/src/remote/persistent_stream.ts:568:41)
at node_modules/@firebase/firestore/src/remote/persistent_stream.ts:448:21
at node_modules/@firebase/firestore/src/remote/persistent_stream.ts:501:18
at node_modules/@firebase/firestore/src/util/async_queue.ts:358:14
console.error
[2020-05-20T13:13:11.851Z] @firebase/firestore: Firestore (7.14.3): FIRESTORE (7.14.3) INTERNAL ASSERTION FAILED: value must be undefined or Uint8Array
at Logger.defaultLogHandler [as _logHandler] (node_modules/@firebase/logger/src/logger.ts:115:57)
at logError (node_modules/@firebase/firestore/src/util/log.ts:45:20)
at fail (node_modules/@firebase/firestore/src/util/assert.ts:34:3)
at hardAssert (node_modules/@firebase/firestore/src/util/assert.ts:53:5)
at JsonProtoSerializer.fromBytes (node_modules/@firebase/firestore/src/remote/serializer.ts:250:7)
at JsonProtoSerializer.fromWatchChange (node_modules/@firebase/firestore/src/remote/serializer.ts:431:32)
Test Suites: 1 failed, 1 total
Tests: 2 failed, 2 total
Snapshots: 0 total
Time: 18.711 s
Ran all test suites matching /.\\spec/i.
(node:8200) UnhandledPromiseRejectionWarning: FirebaseError: Caught error after test environment was torn down
The client has already been terminated.
(node:8200) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:8200) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with `--detectOpenHandles` to troubleshoot this issue.
【问题讨论】:
【参考方案1】:这似乎是最新的@firebase/testing@0.19.4
版本和内部使用的firebase@7.14.4
版本之间的兼容性问题。我遇到了同样的错误,并使用了一个临时解决方法。
尝试将您的@firebase/testing
版本降级为^0.15.0
。经过快速npm i
它对我有用。只要它们修复了当前的兼容性问题,您仍然可以稍后升级到最新版本。
一旦发生这种情况,我会更新我的答案。
更新: 这是我在 firebase-js-sdk GitHub 页面 https://github.com/firebase/firebase-js-sdk/issues/3096 上创建的问题。
似乎与测试框架 Jest 中的一个错误有关。该问题描述了一种不需要降级的解决方法。
一旦不再需要解决方法,我将更新我的答案。
【讨论】:
是的,降级有效,不知道如何,但有效 请注意 - 现在通过安装 'jest-environment-node' 并将 testEnvironment: "node" 添加到 jest.config.js 已正确修复(至少我认为这是他们的预期修复) 【参考方案2】:这是 Firebase 问题:
https://github.com/firebase/firebase-js-sdk/issues/3096显然这是由 Jest 中的错误引起的......
https://github.com/facebook/jest/issues/7780...包括此解决方法:
https://github.com/facebook/jest/issues/7780#issuecomment-615890410重现和修复的步骤...
https://github.com/dconeybe/FirebaseJsBug3096【讨论】:
【参考方案3】:您只需在测试文件的顶部添加以下 JSDOC 注释即可解决此问题,这会阻止 Jest 使用 JSDOM 运行测试。
在spec/collections.spec.js
:
/**
* @jest-environment node
*/
describe("my rules", () =>
// ...
);
根本问题是jsdom
与firebase
库使用的内部断言不兼容,此处记录:https://github.com/nodejs/node/issues/20978
Tony O'Hagan (here) 指出的解决方法允许测试在 JSDOM 环境中运行,但解决方案相当复杂。如果您只是测试 Firestore 安全规则,则不需要 JSDOM。
更新:Jest 27(2021 年 5 月)将 Jest 的默认行为更改为在 Node 环境而不是 JSDOM 中运行
【讨论】:
我认为这个答案涵盖了基于节点的应用程序,而不是基于 Angular 的应用程序。我的理解是你需要 Angular 中的 JSDOM @code 问题是关于使用 Jest 测试 Firestore 安全规则,它不需要 UI 框架 - Angular 或其他。在测试 Angular 应用程序的 Jest 文件中,不要将注释添加到顶部。以上是关于FIRESTORE (7.14.3) 内部断言失败:值必须未定义或 Uint8Array的主要内容,如果未能解决你的问题,请参考以下文章
FIRESTORE (4.10.1) 内部断言失败:AsyncQueue 已经失败:请求的版本 (1) 小于现有版本 (2)
Flutter 错误 - 断言失败:第 213 行 pos 15:'data != null':在从 firestore 获取数据时不正确
云功能失败并出现异常:内部,Flutter 应用程序中没有代码
构建失败并出现异常 - 任务“:cloud_firestore:parseDebugLocalResources”执行失败