harmony 鸿蒙SDK Subsystem Changelog

2025-06-12
浏览 (27)

SDK Subsystem Changelog

cl.sdk.1 Severity Increased for an Alarm Generated When an API Available Only for the FA Model Is Used in a Stage Model Application or Vice Versa

Change Reason

An API available only for the FA model should not be used in an application developed in the stage model, and an API available only for the stage model should be used in an application developed in the FA model. The build process should be interrupted if this requirement is not met.

Change Impact

The application build behavior is affected.

Before change:

When an FA model application uses an API available only in the stage model, a WARN alarm is generated, with the message content as follows:

“This API is used only in Stage Mode, but the current Mode is FA.”

When a stage model application uses an API available only in the FA model, a WARN alarm is generated, with the message content as follows:

“This API is used only in FA Mode, but the current Mode is Stage.”

After change:

When an FA model application uses an API available only in the stage model, an ERROR alarm is generated, with the message content as follows:

“This API is used only in Stage Mode, but the current Mode is FA.”

When a stage model application uses an API available only in the FA model, an ERROR alarm is generated, with the message content as follows:

“This API is used only in FA Mode, but the current Mode is Stage.”

Start API Level

Change Since

OpenHarmony SDK 5.0.0.24

Key API/Component Changes

This change affects only the build. For details about the involved APIs and their substitutes, see API Model Conversion List.

Adaptation Guide

If such an alarm is generated during application build, search for the corresponding API in API Model Conversion List based on the alarm information and find its substitute in the stage model. Then proceed as follows by scenario.

Scenario 1: A substitute exists.

Replace the API with the substitute in your code.

Negative example:

// The current project is in the stage model.
import featureAbility from '@ohos.ability.featureAbility';

let context: featureAbility.Context = featureAbility.getContext().getApplicationContext();

Positive example:

// The current project is in the stage model.
import UIAbility from '@ohos.app.ability.UIAbility';
import common from '@ohos.app.ability.common';

export default class EntryAbility extends UIAbility {
  onCreate() {
    console.log('MyAbility onCreate');
    let applicationContext: common.Context;
    try {
      applicationContext = this.context.getApplicationContext();
    } catch (error) {
      console.error(`getApplicationContext failed, error.code: ${error.code}, error.message: ${error.message}`);
    }
  }
}

Scenario 2: No substitute is available.

Delete the code of the incorrect API call.