Update the Affine Pro app to the latest version

Oct 13, 2025 by windailys.com 55 views

[Bug]: Export to md does not work, only pnd

As a user of Affine Pro, you may have encountered an issue where exporting to Markdown (md) format does not work, while exporting to Pandoc (pnd) format does. This article aims to provide a detailed explanation of the issue, its causes, and potential solutions.

What happened?

When attempting to export a document to Markdown format, users encounter an error that prevents the export from succeeding. The error message indicates that the export process fails to convert the document to a snapshot, resulting in an invalid time value error.

Distribution version

The issue was encountered on the web version of Affine Pro, which can be accessed at https://app.affine.pro.

App Version

The Affine Pro app version at the time of the issue was 20.4.

Browsers

The issue was observed on Chrome browser.

Self-hosting

The user is not self-hosting Affine Pro.

Relevant log output

The log output provides valuable information about the error, including the following:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/". Either the 'unsafe-inline' keyword, a hash ('sha256-zpXBZ2B6ifkDXVZ+lEbqsSd2GPVzFoy9wbxAuk5xHIk='), or a nonce ('nonce-...') is required to enable inline execution.

(anonymous) @ chrome-extension://o…timezoneChange.js:1
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Unchecked runtime.lastError: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
console.js:36 Cannot convert doc to snapshot
(anonymous) @ console.js:36
console.js:36 RangeError: Invalid time value
    at E (format.js:350:11)
    at Object.cellToString (define.ts:12:32)
    at utils.ts:97:33
    at Array.forEach (<anonymous>)
    at utils.ts:81:13
    at Array.forEach (<anonymous>)
    at a (utils.ts:66:12)
    at Object.enter (markdown.ts:33:23)
    at ASTWalker._enter (markdown.ts:138:48)
    at ASTWalker._visit (base.ts:227:18)
    at ASTWalker._visit (base.ts:254:26)
    at async ASTWalker._visit (base.ts:254:15)
    at async ASTWalker.walk (base.ts:299:5)
    at async MarkdownAdapter._traverseSnapshot (markdown.ts:164:13)
    at async MarkdownAdapter.fromBlockSnapshot (markdown.ts:222:32)
    at async MarkdownAdapter.fromDocSnapshot (markdown.ts:238:33)
    at async MarkdownAdapter.fromDoc (base.ts:100:14)
    at async eY (use-export-page.ts:79:19)
    at async e1 (use-export-page.ts:126:5)
    at async e0 (use-export-page.ts:149:7)
    at async use-export-page.ts:189:9
(anonymous) @ console.js:36
console.js:36 Cannot convert doc to snapshot
(anonymous) @ console.js:36
console.js:36 RangeError: Invalid time value
    at E (format.js:350:11)
    at Object.cellToString (define.ts:12:32)
    at utils.ts:97:33
    at Array.forEach (<anonymous>)
    at utils.ts:81:13
    at Array.forEach (<anonymous>)
    at a (utils.ts:66:12)
    at Object.enter (html.ts:26:21)
    at ASTWalker._enter (html.ts:142:48)
    at ASTWalker._visit (base.ts:227:18)
    at ASTWalker._visit (base.ts:254:26)
    at async ASTWalker._visit (base.ts:254:15)
    at async ASTWalker.walk (base.ts:299:5)
    at async HtmlAdapter._traverseSnapshot (html.ts:168:13)
    at async HtmlAdapter.fromBlockSnapshot (html.ts:215:32)
    at async HtmlAdapter.fromDocSnapshot (html.ts:229:33)
    at async HtmlAdapter.fromDoc (base.ts:100:14)
    at async eY (use-export-page.ts:79:19)
    at async eJ (use-export-page.ts:112:5)
    at async e0 (use-export-page.ts:146:7)
    at async use-export-page.ts:189:9
(anonymous) @ console.js:36
console.js:36 Cannot convert doc to snapshot
(anonymous) @ console.js:36
console.js:36 RangeError: Invalid time value
    at E (format.js:350:11)
    at Object.cellToString (define.ts:12:32)
    at utils.ts:97:33
    at Array.forEach (<anonymous>)
    at utils.ts:81:13
    at Array.forEach (<anonymous>)
    at a (utils.ts:66:12)
    at Object.enter (markdown.ts:33:23)
    at ASTWalker._enter (markdown.ts:138:48)
    at ASTWalker._visit (base.ts:227:18)
    at ASTWalker._visit (base.ts:254:26)
    at async ASTWalker._visit (base.ts:254:15)
    at async ASTWalker.walk (base.ts:299:5)
    at async MarkdownAdapter._traverseSnapshot (markdown.ts:164:13)
    at async MarkdownAdapter.fromBlockSnapshot (markdown.ts:222:32)
    at async MarkdownAdapter.fromDocSnapshot (markdown.ts:238:33)
    at async MarkdownAdapter.fromDoc (base.ts:100:14)
    at async eY (use-export-page.ts:79:19)
    at async e1 (use-export-page.ts:126:5)
    at async e0 (use-export-page.ts:149:7)
    at async use-export-page.ts:189:9
(anonymous) @ console.js:36

Potential solutions

Based on the log output, the issue appears to be related to the Content Security Policy (CSP) directive, which prevents the execution of inline scripts. To resolve this issue, the following solutions can be attempted:

Add the 'unsafe-inline' keyword to the CSP directive: This can be done by adding the following line to the CSP directive:

script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'unsafe-inline';


2.  **Use a hash or nonce to enable inline execution**: Instead of using the 'unsafe-inline' keyword, a hash or nonce can be used to enable inline execution. This can be done by adding the following line to the CSP directive:

    ```javascript
script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'sha256-zpXBZ2B6ifkDXVZ+lEbqsSd2GPVzFoy9wbxAuk5xHIk=';

or

```javascript

script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'nonce-...';


3.  **Update the Affine Pro app to the latest version**: It is possible that the issue is resolved in a later version of the Affine Pro app. Updating the app to the latest version may resolve the issue.

**Conclusion**
----------

The issue of exporting to Markdown format not working in Affine Pro appears to be related to the Content Security Policy (CSP) directive. By adding the 'unsafe-inline' keyword, using a hash or nonce, or updating the app to the latest version, the issue can be resolved.<br/>
**[Bug]: Export to md does not work, only pnd - Q&A**

**Introduction**
===============

As a user of Affine Pro, you may have encountered an issue where exporting to Markdown (md) format does not work, while exporting to Pandoc (pnd) format does. This article aims to provide a detailed explanation of the issue, its causes, and potential solutions. In this Q&A section, we will address some of the most frequently asked questions related to this issue.

**Q: What is the cause of the issue?**
--------------------------------------

A: The issue is caused by the Content Security Policy (CSP) directive, which prevents the execution of inline scripts. This directive is used to prevent cross-site scripting (XSS) attacks and ensure the security of the application.

**Q: How can I resolve the issue?**
--------------------------------------

A: There are several ways to resolve the issue:

1.  **Add the 'unsafe-inline' keyword to the CSP directive**: This can be done by adding the following line to the CSP directive:

    ```javascript
script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'unsafe-inline';

Use a hash or nonce to enable inline execution: Instead of using the 'unsafe-inline' keyword, a hash or nonce can be used to enable inline execution. This can be done by adding the following line to the CSP directive:

script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'sha256-zpXBZ2B6ifkDXVZ+lEbqsSd2GPVzFoy9wbxAuk5xHIk=';


    or

    ```javascript
script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' chrome-extension://9b441a33-cd06-48d5-a013-184ee238bb44/' 'nonce-...';

Update the Affine Pro app to the latest version: It is possible that the issue is resolved in a later version of the Affine Pro app. Updating the app to the latest version may resolve the issue.

Q: Why is the issue only occurring when exporting to Markdown format?

A: The issue is only occurring when exporting to Markdown format because the Markdown adapter is using inline scripts to render the document. The CSP directive is preventing the execution of these inline scripts, resulting in the error.

Q: Can I disable the CSP directive to resolve the issue?

A: While it is possible to disable the CSP directive, it is not recommended as it can make the application vulnerable to XSS attacks. Instead, it is recommended to use one of the solutions mentioned above to resolve the issue.

Q: How can I prevent this issue from occurring in the future?

A: To prevent this issue from occurring in the future, it is recommended to:

Regularly update the Affine Pro app to the latest version: This will ensure that any security patches or updates are applied, reducing the risk of security vulnerabilities.
Use a secure Content Security Policy (CSP) directive: This will help to prevent XSS attacks and ensure the security of the application.
Use a secure rendering engine: This will help to prevent the execution of inline scripts and reduce the risk of security vulnerabilities.

Conclusion

The issue of exporting to Markdown format not working in Affine Pro is a complex one, but by understanding the causes and potential solutions, users can resolve the issue and continue to use the application securely. By following the recommendations outlined in this article, users can prevent this issue from occurring in the future and ensure the security of their application.