openharmony 鸿蒙 changelogs-arkcompiler

2026-08-25 浏览 (1)

ArkCompiler Changelog

cl.arkcompiler.1 JIT Is Disabled by Default and Requires Permission Certificate and Approval to Enable

Access Level

Public API

Reason for Change

The Just In Time (JIT) compilation feature, which compiles code on-the-fly during execution, can pose risks of arbitrary code injection. To safeguard application security and uphold the integrity of the OpenHarmony ecosystem, the system now defaults to disabling the JIT functionality in the JSVM. Instead, it executes JS code through interpretation.

Impact of the Change

This change requires application adaptation.

Before the change: JIT is enabled by default.

After the change: JIT is disabled by default and can only be enabled after obtaining a permission certificate. Without JIT, wasm interfaces that rely on JIT fail to execute, and there may be performance differences between JIT and interpretation in specific scenarios.

Start API Level

API 11

Change Since

OpenHarmony SDK 5.1.0.51

Key API/Component Changes

APIImpact
OH_JSVM_CompileWasmModuleIf the JIT permission is not granted, the JIT_MODE_EXPECTED status code is returned, and a log is printed for notification.
OH_JSVM_CompileWasmFunctionIf the JIT permission is not granted, the JIT_MODE_EXPECTED status code is returned, and a log is printed for notification.
OH_JSVM_CreateWasmCacheIf the JIT permission is not granted, the JIT_MODE_EXPECTED status code is returned, and a log is printed for notification.
OH_JSVM_RunScriptIf the JIT permission is not granted, the script containing wasm will fail to be executed. The performance varies in specific scenarios, and a log is printed for notification.

Adaptation Guide

For new applications that wish to use JIT, you must submit an application for the ohos.permission.kernel.ALLOW_EXECUTABLE_FORT_MEMORY restricted ACL permission to the AppGallery Connect (AGC). In your application materials, specify the exact scenarios in which the JIT functionality of the JSVM engine will be used. Once the permission is approved, you can update your profile certificate from the AGC website and repackage your application for release. For details, see Requesting Restricted Permissions.

Precautions

  1. If restricted permissions are only declared in the configuration file without a permission profile, the application installation will fail.
  2. If the error "The ohos.permission.kernel.ALLOW_EXECUTABLE_FORT_MEMORY permission under requestPermissions must be a value that is predefined within the SDK or a custom one that you have included under definePermissions." is displayed during the compilation process, update the OpenHarmony SDK to the latest version (5.0.2.125 or later).

你可能感兴趣的鸿蒙文章

openharmony 鸿蒙 i18n-ui-design

openharmony 鸿蒙 i18n-sorting-local

openharmony 鸿蒙 i18n-numbers-weights-measures

openharmony 鸿蒙 i18n-l10n

openharmony 鸿蒙 i18n-preferred-language

openharmony 鸿蒙 Readme-EN

openharmony 鸿蒙 i18n-language-region-display

openharmony 鸿蒙 pseudo-i18n-testing-translation

openharmony 鸿蒙 i18n-calendar

openharmony 鸿蒙 i18n-dst-transition

  • 所属分类: 后端技术
  • 本文标签: 软件 鸿蒙
  • 版权声明: 本文链接 https://seaxiang.com/blog/Xv2dR7ZQ