[Bug] Smart App Control blocks unsigned plugin DLL on Windows 11 (0.9.1)

Open
#9,148 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter

Research direction

The issue concerns the unsigned super_native_extensions_plugin.dll shipped in the Windows release ZIP, so the relevant places are the Windows build and release packaging steps, not Dart code. Start by finding where that DLL is produced and bundled, and check whether a signing step exists in the release workflow. Done would mean a signed DLL in the Windows artifact, which needs a code-signing certificate that only maintainers can provide, so confirm with them before starting.

Written by the indexing model from the issue text.

Description

Bug Description

AppFlowy 0.9.1 is blocked by Windows Smart App Control (SAC) on Windows 11. Launching fails with a Bad Image error (0xc0e90002) involving super_native_extensions_plugin.dll. Windows Code Integrity logs Event ID 3077 for this block (policy ID 0283ac0f-fff1-49ae-ada1-8a933130cad6).

The DLL is unsigned. I compared the installed 0.9.1 DLL with the DLL in the official 0.9.1 ZIP; both are NotSigned and have the same SHA-256: A825B509FF5F188604C6C4121980AE55A13857BF2479556E76785B65B91191DF. Disabling Smart App Control allowed 0.9.1 to launch successfully.

This appears related to issue #8925, which reported the same Windows error code on 0.13.0. My report is specifically about SAC blocking this unsigned component on 0.9.1 and the signing status of the distributed DLL.

How to Reproduce
  1. On Windows 11 with Smart App Control enabled, install and launch AppFlowy 0.9.1.
  2. AppFlowy fails to launch and Windows reports Bad Image error 0xc0e90002 for super_native_extensions_plugin.dll.
  3. Check Windows Code Integrity events; Event ID 3077 records the block with policy ID 0283ac0f-fff1-49ae-ada1-8a933130cad6.
  4. Compare the installed DLL with the one in the official 0.9.1 ZIP: both are unsigned and have SHA-256 A825B509FF5F188604C6C4121980AE55A13857BF2479556E76785B65B91191DF.
  5. With Smart App Control disabled, AppFlowy 0.9.1 launches successfully.
Expected Behavior

AppFlowy 0.9.1 should launch on Windows 11 with Smart App Control enabled, without requiring users to weaken Windows security protections.

Operating System

Windows 11 (Smart App Control enabled)

AppFlowy Version(s)

0.9.1

Screenshots

No response

Additional Context

The official AppFlowy 0.15.1 Windows ZIP also contains an unsigned super_native_extensions_plugin.dll (SHA-256 B8EE5AF43D6A47FA1B7ACF2439BD6F70E18DB5C0393D27623A59B893C0C2D4AD). I have not tested whether 0.15.1 launches with Smart App Control enabled, so I cannot confirm whether it is affected.

Please sign all distributed Windows components with a trusted code-signing certificate, and if possible provide a fix compatible with AppFlowy 0.9.1. The 0.15.1 signing status may also merit review.

Dominant language
Dart
Stars
79.1k
Forks
6.3k
Avg merge
17h 29m
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AppFlowy-IO/AppFlowy

All issues in AppFlowy-IO/AppFlowy

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.