Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

不支持鸿蒙API9 #1325

Closed
ant074 opened this issue Jun 17, 2024 · 1 comment
Closed

不支持鸿蒙API9 #1325

ant074 opened this issue Jun 17, 2024 · 1 comment

Comments

@ant074
Copy link

ant074 commented Jun 17, 2024

Note:

hvigor Finished :module_base:default@CompileJS... after 5 ms
"@kit.PerformanceAnalysisKit" is imported by "oh_modules/.ohpm/@Tencent[email protected]/oh_modules/@tencent/mmkv/src/main/ets/utils/MMKV.ets", but could not be resolved – treating it as an external dependency.
hvigor ERROR: Failed :module_base:default@CompileArkTS...
hvigor ERROR: ArkTs Compiler Error
ERROR: ArkTS:ERROR File: G:/huawei/ws/qbtmj_hm/oh_modules/.ohpm/@Tencent[email protected]/oh_modules/@tencent/mmkv/src/main/ets/utils/MMKV.ets:22:23
Cannot find module '@kit.PerformanceAnalysisKit' or its corresponding type declarations.

ERROR: ArkTS:ERROR File: G:/huawei/ws/qbtmj_hm/oh_modules/.ohpm/@Tencent[email protected]/oh_modules/@tencent/mmkv/src/main/ets/utils/MMKV.ets:683:31
Property 'getAllSync' does not exist on type 'Preferences'.

WARN: ArkTS:WARN File: G:/huawei/ws/qbtmj_hm/oh_modules/.ohpm/@Tencent[email protected]/oh_modules/@tencent/mmkv/src/main/ets/utils/MMKV.ets:21:20
Currently module for 'libmmkv.so' is not verified. If you're importing napi, its verification will be enabled in later SDK version. Please make sure the corresponding .d.ts file is provided and the napis are correctly declared.

COMPILE RESULT:FAIL {ERROR:3 WARN:1}

hvigor ERROR: BUILD FAILED in 4 s 15 ms

The language of MMKV

arkTS

The version of MMKV

1.3.6-beta2

@lingol
Copy link
Collaborator

lingol commented Jun 17, 2024

MMKV requires API 12.

We started from API 12 targeting HarmonyOS NEXT, which will be released at least from 12.
So no, API 11 is not in our plan.

Originally posted by @lingol in #1298 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants