uni_module [tuikit-atomic-x] FAILURE: Build failed with an exception. t ':app' without an existing directory is not allowed. The configured projectDirectory

10:56:19.983 uni_module [tuikit-atomic-x]
10:56:19.983 FAILURE: Build failed with an exception.
10:56:19.983 * What went wrong:
10:56:19.983 Configuring project ':app' without an existing directory is not allowed. The configured projectDirectory '/Users/hello/Library/Application Support/HBuilder X/.uts-development-android/gradle/tuikit-atomic-x_1777604175164/app' does not exist, can't be written to or is not a directory.
10:56:19.983 * Try:
10:56:19.984 > Make sure the project directory exists and is writable.
10:56:19.984 > Run with --scan to generate a Build Scan (powered by Develocity).
10:56:19.984 BUILD FAILED in 3s
10:56:34.025 uts插件[tuikit-atomic-x]编译失败
10:56:34.045 ‌error: 找不到名称“opensource”。参考: https://doc.dcloud.net.cn/uni-app-x/uts/compiler-known-issues.html#error18‌
10:56:34.045 at uni_modules/tuikit-atomic-x/utssdk/app-android/svgaplayer.vue.ts:7:27
10:56:34.046 5 | import Log from "android.util.Log"
10:56:34.046 6 | import SVGAAnimationView from "uts.sdk.modules.atomicx.kotlin.SVGAAnimationView";
10:56:34.046 7 | import SVGACallback from "com.opensource.svgaplayer.SVGACallback"
10:56:34.046 | ^
10:56:34.046 8 |
10:56:34.046 9 | const SVGA_TAG = "SvgaPlayer"⁠
10:56:34.046 ‌error: 找不到名称“trtc”。参考: https://doc.dcloud.net.cn/uni-app-x/uts/compiler-known-issues.html#error18‌
10:56:34.046 at uni_modules/tuikit-atomic-x/utssdk/app-android/index.uts:14:62
10:56:34.046 12 | // HybridBridge
10:56:34.046 13 | import { HybridBridge } from 'io.trtc.tuikit.atomicxcore.hybridapi.bridge';
10:56:34.046 14 | import { DataReport, InteractionMetrics, AtomicMetrics } from 'io.trtc.tuikit.atomicxcore.impl.common';
10:56:34.046 | ^
10:56:34.046 15 | DataReport.reportUIPlatform(52);
10:56:34.046 16 | ⁠
10:56:34.046 ‌error: 找不到名称“trtc”。参考: https://doc.dcloud.net.cn/uni-app-x/uts/compiler-known-issues.html#error18‌
10:56:34.046 at uni_modules/tuikit-atomic-x/utssdk/app-android/index.uts:14:62
10:56:34.046 12 | // HybridBridge
10:56:34.046 13 | import { HybridBridge } from 'io.trtc.tuikit.atomicxcore.hybridapi.bridge';
10:56:34.046 14 | import { DataReport, InteractionMetrics, AtomicMetrics } from 'io.trtc.tuikit.atomicxcore.impl.common';
10:56:34.047 | ^
10:56:34.047 15 | DataReport.reportUIPlatform(52);
10:56:34.047 16 | ⁠
10:56:34.047 ‌error: 找不到名称“trtc”。参考: https://doc.dcloud.net.cn/uni-app-x/uts/compiler-known-issues.html#error18‌
10:56:34.047 at uni_modules/tuikit-atomic-x/utssdk/app-android/index.uts:14:62
10:56:34.047 12 | // HybridBridge
10:56:34.047 13 | import { HybridBridge } from 'io.trtc.tuikit.atomicxcore.hybridapi.bridge';
10:56:34.047 14 | import { DataReport, InteractionMetrics, AtomicMetrics } from 'io.trtc.tuikit.atomicxcore.impl.common';
10:56:34.047 | ^
10:56:34.047 15 | DataReport.reportUIPlatform(52);
10:56:34.047 16 | ⁠
10:56:34.047 ‌error: 找不到名称“trtc”。参考: https://doc.dcloud.net.cn/uni-app-x/uts/compiler-known-issues.html#error18‌
10:56:34.047 at uni_modules/tuikit-atomic-x/utssdk/app-android/index.uts:13:29
10:56:34.047 11 |
10:56:34.047 12 | // HybridBridge
10:56:34.047 13 | import { HybridBridge } from 'io.trtc.tuikit.atomicxcore.hybridapi.bridge';
10:56:34.047 | ^
10:56:34.047 14 | import { DataReport, InteractionMetrics, AtomicMetrics } from 'io.trtc.tuikit.atomicxcore.impl.common';
10:56:34.047 15 | DataReport.reportUIPlatform(52);⁠
10:56:42.001 项目 sssssss 编译成功。
10:56:42.061 ready in 55049ms.
10:56:43.373 正在安装HBuilder调试基座...
10:57:34.762 安装HBuilder调试基座成功
10:57:37.464 正在建立手机连接...
10:57:42.916 正在同步手机端程序文件...
10:58:02.914 同步手机端程序文件成功
10:58:05.071 正在启动HBuilder调试基座...
10:58:06.368 应用【ssssss】已启动
10:58:06.469 注意编译阶段有报错，可能部分模块无法使用

Start with uni_modules/tuikit-atomic-x/utssdk/app-android/svgaplayer.vue.ts and uni_modules/tuikit-atomic-x/utssdk/app-android/index.uts, then review the Gradle project-directory failure in the build log. Check why the SVGACallback and io.trtc.tuikit.atomicxcore imports are unresolved; done means the Android compilation completes without these errors and the affected modules remain usable.