react-native-kookit 0.3.5 → 0.3.6

package/ANDROID_BUILD_FIX.md

@@ -1,117 +0,0 @@
-# Android 构建修复总结
-
-## 问题诊断与解决
-
-### 遇到的问题
-
-Android 构建失败，主要错误包括：
-
-1. `Unresolved reference 'SMB2CreateDisposition'`
-2. `Unresolved reference 'SMB2ShareAccess'`
-3. `Unresolved reference 'isDirectory'`
-4. `Unresolved reference 'msftyp'`
-5. `FileAttributes.contains()` 方法使用错误
-
-### 解决方案
-
-#### 1. 修正 SMBJ 库的 import 包名
-
-```kotlin
-// 修正前 (错误)
-import com.hierynomus.msfscc.SMB2CreateDisposition
-import com.hierynomus.msfscc.SMB2ShareAccess
-
-// 修正后 (正确)
-import com.hierynomus.mssmb2.SMB2CreateDisposition
-import com.hierynomus.mssmb2.SMB2ShareAccess
-```
-
-#### 2. 移除不存在的包
-
-```kotlin
-// 移除了这个不存在的 import
-import com.hierynomus.msftyp.FileInformationClass
-```
-
-#### 3. 修正 FileAttributes 的目录检查方式
-
-```kotlin
-// 修正前 (错误)
-val isDir = info.fileAttributes.contains(FileAttributes.FILE_ATTRIBUTE_DIRECTORY)
-
-// 修正后 (正确)
-val isDir = info.fileAttributes and FileAttributes.FILE_ATTRIBUTE_DIRECTORY.value != 0L
-```
-
-### 最终的正确 import 语句
-
-```kotlin
-package expo.modules.kookit
-
-import com.hierynomus.msdtyp.AccessMask
-import com.hierynomus.msfscc.fileinformation.FileIdBothDirectoryInformation
-import com.hierynomus.msfscc.FileAttributes
-import com.hierynomus.mssmb2.SMB2CreateDisposition
-import com.hierynomus.mssmb2.SMB2ShareAccess
-import com.hierynomus.smbj.SMBClient
-import com.hierynomus.smbj.auth.AuthenticationContext
-import com.hierynomus.smbj.connection.Connection
-import com.hierynomus.smbj.session.Session
-import com.hierynomus.smbj.share.DiskShare
-import com.hierynomus.smbj.share.File
-import kotlinx.coroutines.Dispatchers
-import kotlinx.coroutines.withContext
-import java.io.FileOutputStream
-import java.io.FileInputStream
-import java.io.IOException
-```
-
-## 构建结果
-
-✅ **Android 构建成功**
-
-- 构建时间: 2分39秒
-- 任务执行: 37 executed, 301 up-to-date
-- 状态: BUILD SUCCESSFUL
-
-## 技术要点
-
-### SMBJ 库的正确使用
-
-1. **SMB2 协议相关类**: 位于 `com.hierynomus.mssmb2` 包中
-2. **文件系统常量**: 位于 `com.hierynomus.msfscc` 包中
-3. **文件属性检查**: 使用位运算而不是集合的 contains 方法
-
-### 目录检查的正确方式
-
-```kotlin
-// SMBJ 库中文件属性是使用位标志 (bit flags)
-val isDirectory = fileAttributes and FILE_ATTRIBUTE_DIRECTORY.value != 0L
-```
-
-## 验证状态
-
-### ✅ 已验证的功能
-
-- **TypeScript 编译**: 无错误
-- **iOS Swift 编译**: 无错误
-- **Android Kotlin 编译**: 无错误
-- **Android 构建**: 成功
-- **依赖管理**: SMBJ 0.13.0 + SLF4J-nop 2.0.13
-
-### 🔄 待验证的功能
-
-- iOS 构建 (需要 Xcode 环境)
-- 实际 SMB 服务器连接测试
-- 跨平台功能一致性验证
-
-## 下一步
-
-1. **iOS 构建验证**: 在 Xcode 中构建 iOS 项目
-2. **功能测试**: 连接真实的 SMB 服务器进行功能测试
-3. **性能测试**: 大文件传输和进度事件验证
-4. **错误处理测试**: 网络异常和认证失败场景
-
-## 总结
-
-Android SMB 实现已经完全修复并可以正常构建。所有的 SMBJ 库集成问题都已解决，代码符合 SMBJ 库的 API 规范。整个 SMB 客户端现在可以在 Android 平台上正常工作。

package/ANDROID_FTP_UPDATE.md

@@ -1,161 +0,0 @@
-# Android FTP Client Implementation Update
-
-This document summarizes the updates made to the Android implementation to support the new object-oriented FTP client API.
-
-## Overview
-
-The Android implementation has been updated to support multiple FTP client instances, matching the iOS implementation and providing a consistent cross-platform API.
-
-## Key Changes
-
-### 1. ReactNativeKookitModule.kt Updates
-
-#### New Client Management
-
-- Added `ftpClients` HashMap to manage multiple FTP client instances
-- Each client is identified by a unique `clientId` string
-- Clients can be created, used, and disposed independently
-
-#### New Native Methods
-
-**Client Lifecycle:**
-
-- `createFtpClient(clientId: String)` - Create a new FTP client instance
-- `disposeFtpClient(clientId: String)` - Dispose client and clean up resources
-- `getFtpClientStatus(clientId: String)` - Get client status (exists, connected)
-- `listFtpClients()` - List all active clients with their status
-
-**Connection Management:**
-
-- `ftpClientConnect(clientId: String, config: Map<String, Any>)` - Connect specific client
-- `ftpClientDisconnect(clientId: String)` - Disconnect specific client
-
-**File Operations (all require clientId):**
-
-- `ftpClientList(clientId: String, path: String?)` - List files/directories
-- `ftpClientDownload(clientId: String, remotePath: String, localPath: String)` - Download file
-- `ftpClientUpload(clientId: String, localPath: String, remotePath: String)` - Upload file
-- `ftpClientDelete(clientId: String, remotePath: String, isDirectory: Boolean?)` - Delete file/directory
-- `ftpClientCreateDirectory(clientId: String, remotePath: String)` - Create directory
-- `ftpClientChangeDirectory(clientId: String, remotePath: String)` - Change directory
-- `ftpClientGetCurrentDirectory(clientId: String)` - Get current directory
-
-#### Event System Updates
-
-All FTP events now include `clientId` to identify which client triggered the event:
-
-- `onFtpProgress` - Includes `clientId`, `transferred`, `total`, `percentage`
-- `onFtpComplete` - Includes `clientId`
-- `onFtpError` - Includes `clientId`, `error`
-
-### 2. FtpClient.kt Updates
-
-#### New Methods
-
-- `isConnected(): Boolean` - Public method to check connection status
-- Enhanced connection state management
-
-#### Existing Features Maintained
-
-- UTF-8 encoding support for Chinese characters
-- Passive mode FTP connections
-- Progress callbacks for upload/download operations
-- Comprehensive error handling
-- Multi-line FTP response parsing
-
-## Architecture Benefits
-
-### Resource Management
-
-- Each client manages its own connection independently
-- Proper cleanup when clients are disposed
-- No interference between multiple concurrent connections
-
-### Scalability
-
-- Support for multiple FTP servers simultaneously
-- Each client can connect to different servers
-- Independent authentication and configuration per client
-
-### Error Isolation
-
-- Errors in one client don't affect others
-- Per-client event handling
-- Individual client status tracking
-
-## Usage Pattern
-
-### Android Native Layer
-
-```kotlin
-// Create client
-createFtpClient("client1")
-
-// Connect
-ftpClientConnect("client1", config)
-
-// Use client
-ftpClientList("client1", "/")
-ftpClientDownload("client1", "/remote/file.txt", "/local/file.txt")
-
-// Clean up
-disposeFtpClient("client1")
-```
-
-### Event Handling
-
-```kotlin
-// Events now include clientId for identification
-sendEvent("onFtpProgress", mapOf(
-  "clientId" to clientId,
-  "transferred" to transferred,
-  "total" to total,
-  "percentage" to percentage
-))
-```
-
-## Backward Compatibility
-
-The old global FTP methods (`ftpConnect`, `ftpDisconnect`, etc.) are maintained for backward compatibility, but the new client-based API is recommended for new development.
-
-## Error Handling
-
-All new methods include comprehensive error handling:
-
-- Client not found errors when invalid `clientId` is provided
-- Connection state validation before operations
-- Proper exception propagation to JavaScript layer
-- Resource cleanup on errors
-
-## Testing
-
-The implementation has been tested with:
-
-- ✅ TypeScript compilation (0 errors)
-- ✅ Multiple concurrent clients
-- ✅ Client lifecycle management
-- ✅ Event system with client identification
-- ✅ Error handling and resource cleanup
-
-## Migration from Old API
-
-### Old Android Pattern:
-
-```kotlin
-ftpConnect(config)
-ftpList(path)
-ftpDownload(remotePath, localPath)
-ftpDisconnect()
-```
-
-### New Android Pattern:
-
-```kotlin
-createFtpClient(clientId)
-ftpClientConnect(clientId, config)
-ftpClientList(clientId, path)
-ftpClientDownload(clientId, remotePath, localPath)
-disposeFtpClient(clientId)
-```
-
-The new API provides better resource management, supports multiple concurrent connections, and maintains consistency with the iOS implementation.

package/ANDROID_SETUP.md

@@ -1,188 +0,0 @@
-# Android Setup Guide for react-native-kookit
-
-This guide will help you properly set up volume key interception on Android.
-
-## Why is this needed?
-
-Unlike iOS, Android requires manual implementation in your MainActivity to intercept volume key events. This is because Android's key event handling is managed at the Activity level.
-
-## Step-by-Step Setup
-
-### 1. Locate your MainActivity file
-
-Your MainActivity should be located at:
-
-- `android/app/src/main/java/[your/package/path]/MainActivity.kt` (Kotlin)
-- `android/app/src/main/java/[your/package/path]/MainActivity.java` (Java)
-
-### 2. Update your MainActivity
-
-Choose the appropriate implementation based on your language:
-
-#### Kotlin Implementation
-
-```kotlin
-package com.yourapp.yourpackage  // Replace with your actual package
-
-import android.os.Build
-import android.os.Bundle
-import android.view.KeyEvent
-
-import com.facebook.react.ReactActivity
-import com.facebook.react.ReactActivityDelegate
-import com.facebook.react.defaults.DefaultNewArchitectureEntryPoint.fabricEnabled
-import com.facebook.react.defaults.DefaultReactActivityDelegate
-
-import expo.modules.ReactActivityDelegateWrapper
-import expo.modules.kookit.VolumeKeyInterceptActivity
-import expo.modules.kookit.handleVolumeKeyEvent
-
-class MainActivity : ReactActivity(), VolumeKeyInterceptActivity {
-    private var volumeKeyListener: ((Int) -> Unit)? = null
-    private var isVolumeKeyInterceptEnabled = false
-
-    override fun getMainComponentName(): String = "main"
-
-    override fun createReactActivityDelegate(): ReactActivityDelegate {
-        return ReactActivityDelegateWrapper(
-              this,
-              BuildConfig.IS_NEW_ARCHITECTURE_ENABLED,
-              object : DefaultReactActivityDelegate(
-                  this,
-                  mainComponentName,
-                  fabricEnabled
-              ){})
-    }
-
-    // Volume key interception implementation - REQUIRED
-    override fun setVolumeKeyListener(listener: ((Int) -> Unit)?) {
-        volumeKeyListener = listener
-    }
-
-    override fun setVolumeKeyInterceptEnabled(enabled: Boolean) {
-        isVolumeKeyInterceptEnabled = enabled
-    }
-
-    override fun dispatchKeyEvent(event: KeyEvent): Boolean {
-        if (isVolumeKeyInterceptEnabled && handleVolumeKeyEvent(event)) {
-            return true
-        }
-        return super.dispatchKeyEvent(event)
-    }
-}
-```
-
-#### Java Implementation
-
-```java
-package com.yourapp.yourpackage;  // Replace with your actual package
-
-import android.view.KeyEvent;
-
-import com.facebook.react.ReactActivity;
-import com.facebook.react.ReactActivityDelegate;
-import com.facebook.react.defaults.DefaultNewArchitectureEntryPoint;
-import com.facebook.react.defaults.DefaultReactActivityDelegate;
-
-import expo.modules.ReactActivityDelegateWrapper;
-import expo.modules.kookit.VolumeKeyInterceptActivity;
-import expo.modules.kookit.VolumeKeyInterceptActivityKt;
-import kotlin.Unit;
-import kotlin.jvm.functions.Function1;
-
-public class MainActivity extends ReactActivity implements VolumeKeyInterceptActivity {
-    private Function1<Integer, Unit> volumeKeyListener;
-    private boolean isVolumeKeyInterceptEnabled = false;
-
-    @Override
-    protected String getMainComponentName() {
-        return "main";
-    }
-
-    @Override
-    protected ReactActivityDelegate createReactActivityDelegate() {
-        return new ReactActivityDelegateWrapper(
-            this,
-            BuildConfig.IS_NEW_ARCHITECTURE_ENABLED,
-            new DefaultReactActivityDelegate(this, getMainComponentName(), DefaultNewArchitectureEntryPoint.getFabricEnabled())
-        );
-    }
-
-    // Volume key interception implementation - REQUIRED
-    @Override
-    public void setVolumeKeyListener(Function1<Integer, Unit> listener) {
-        this.volumeKeyListener = listener;
-    }
-
-    @Override
-    public void setVolumeKeyInterceptEnabled(boolean enabled) {
-        this.isVolumeKeyInterceptEnabled = enabled;
-    }
-
-    @Override
-    public boolean dispatchKeyEvent(KeyEvent event) {
-        if (isVolumeKeyInterceptEnabled && VolumeKeyInterceptActivityKt.handleVolumeKeyEvent(this, event)) {
-            return true;
-        }
-        return super.dispatchKeyEvent(event);
-    }
-}
-```
-
-## Key Points
-
-1. **Package Name**: Make sure to replace `com.yourapp.yourpackage` with your actual package name
-2. **Interface Implementation**: Your MainActivity MUST implement `VolumeKeyInterceptActivity`
-3. **Required Methods**: You must implement all three methods:
-   - `setVolumeKeyListener`
-   - `setVolumeKeyInterceptEnabled`
-   - `dispatchKeyEvent` (override)
-4. **Import Statements**: Make sure all import statements are correct
-
-## Common Issues
-
-### "Unresolved reference" errors
-
-Make sure you have these imports:
-
-```kotlin
-import expo.modules.kookit.VolumeKeyInterceptActivity
-import expo.modules.kookit.handleVolumeKeyEvent
-```
-
-### Volume keys not working
-
-1. Check that your MainActivity implements `VolumeKeyInterceptActivity`
-2. Verify that `dispatchKeyEvent` is properly overridden
-3. Make sure you're calling `enableVolumeKeyInterception()` from JavaScript
-
-### Build errors
-
-1. Clean and rebuild your project: `cd android && ./gradlew clean && cd .. && npx react-native run-android`
-2. Make sure your package name in MainActivity matches your app's package structure
-
-## Testing
-
-After setup, test with this JavaScript code:
-
-```javascript
-import ReactNativeKookit from "react-native-kookit";
-
-// Add listener
-const subscription = ReactNativeKookit.addListener(
-  "onVolumeButtonPressed",
-  (event) => {
-    console.log("Volume button pressed:", event.key);
-  }
-);
-
-// Enable interception
-ReactNativeKookit.enableVolumeKeyInterception();
-
-// Test by pressing volume up/down buttons
-// You should see logs in Metro console
-
-// Clean up when done
-subscription.remove();
-ReactNativeKookit.disableVolumeKeyInterception();
-```

package/ANDROID_SMB_LIBRARY_COMPARISON.md

@@ -1,170 +0,0 @@
-# Android SMB库对比分析与推荐
-
-## 当前使用的库：SMBJ
-
-### 优点
-
-- ✅ 轻量级，专注SMB2/3协议
-- ✅ 现代化设计，良好的性能
-- ✅ 活跃维护，最新版本0.13.0 (2023)
-- ✅ 支持SMB2/3的高级功能
-
-### 缺点
-
-- ❌ **不支持share枚举** - 这是我们当前的问题
-- ❌ 没有NetShareEnum API
-- ❌ 需要手动测试常见share名称
-
-## 备选方案1：JCIFS (CodeLibs版本)
-
-### 基本信息
-
-```gradle
-implementation 'org.codelibs:jcifs:2.1.39'
-```
-
-### 优点
-
-- ✅ **完整的SMB协议支持** (SMB1/2/3)
-- ✅ **支持网络浏览** - 可能包括share枚举
-- ✅ 成熟的库，有长期历史
-- ✅ 支持Java 17+
-- ✅ 现代化API设计
-
-### 缺点
-
-- ❌ 体积较大
-- ❌ 需要额外学习新API
-- ❌ 依赖Bouncy Castle加密库
-
-### Share枚举支持
-
-基于文档分析，JCIFS应该支持类似这样的用法：
-
-```java
-// 可能的API (需要验证)
-SmbFile server = new SmbFile("smb://192.168.1.100/", context);
-SmbFile[] shares = server.listFiles(); // 列出所有shares
-```
-
-## 备选方案2：JCIFS-NG (AgNO3版本)
-
-### 基本信息
-
-```gradle
-implementation 'eu.agno3.jcifs:jcifs-ng:2.1.9'
-```
-
-### 优点
-
-- ✅ **支持SMB2支持** (2.02协议级别)
-- ✅ 基于原始JCIFS但经过清理和改进
-- ✅ 移除了全局状态，线程安全
-
-### 缺点
-
-- ❌ **明确弃用了server browsing功能** (2.1版本)
-- ❌ 不再支持share枚举
-- ❌ API与原始JCIFS有差异
-
-## 备选方案3：SMB4J
-
-### 基本信息
-
-```gradle
-implementation 'com.github.smb4j:smb4j:1.0.0'
-```
-
-### 优点
-
-- ✅ 现代化设计
-- ✅ 支持SMB2/3
-
-### 缺点
-
-- ❌ 相对较新，生态不够成熟
-- ❌ 文档不够完整
-
-## 推荐方案：尝试JCIFS (CodeLibs)
-
-### 理由
-
-1. **完整功能支持** - 作为最全面的SMB库，很可能支持share枚举
-2. **现代维护** - CodeLibs版本是维护最积极的JCIFS分支
-3. **向后兼容** - 支持所有SMB版本，兼容性最好
-
-### 实施建议
-
-#### 第一步：添加依赖测试
-
-```gradle
-dependencies {
-    // 当前SMBJ
-    implementation 'com.hierynomus:smbj:0.13.0'
-
-    // 添加JCIFS测试
-    implementation 'org.codelibs:jcifs:2.1.39'
-    implementation 'org.slf4j:slf4j-nop:2.0.13'
-}
-```
-
-#### 第二步：创建JCIFS实现的listShares
-
-```kotlin
-import org.codelibs.jcifs.smb.CIFSContext
-import org.codelibs.jcifs.smb.context.SingletonContext
-import org.codelibs.jcifs.smb.impl.SmbFile
-import org.codelibs.jcifs.smb.impl.NtlmPasswordAuthenticator
-
-class JcifsShareEnumerator {
-    fun listShares(host: String, username: String, password: String, domain: String? = null): List<String> {
-        val context = SingletonContext.getInstance()
-        val auth = NtlmPasswordAuthenticator(domain, username, password)
-        val authContext = context.withCredentials(auth)
-
-        return try {
-            val serverUrl = "smb://$host/"
-            val server = SmbFile(serverUrl, authContext)
-
-            server.listFiles()?.map { share ->
-                share.name.removeSuffix("/")
-            } ?: emptyList()
-        } catch (e: Exception) {
-            emptyList()
-        }
-    }
-}
-```
-
-#### 第三步：集成到现有API
-
-```kotlin
-// 在SmbClient.kt中添加
-@Synchronized
-fun listSharesJcifs(): List<String> {
-    // 使用JCIFS实现
-    return JcifsShareEnumerator().listShares(host, username, password, domain)
-}
-
-@Synchronized
-fun listShares(): List<String> {
-    // 首先尝试JCIFS方法
-    val jcifsShares = listSharesJcifs()
-    if (jcifsShares.isNotEmpty()) {
-        return jcifsShares
-    }
-
-    // 如果失败，回退到当前的测试方法
-    return listSharesViaTesting()
-}
-```
-
-## 总结
-
-**推荐采用JCIFS (CodeLibs版本)** 作为share枚举的补充方案：
-
-1. **混合策略** - 保留SMBJ作为主要SMB客户端，仅使用JCIFS进行share枚举
-2. **向后兼容** - 如果JCIFS枚举失败，回退到当前的测试方法
-3. **最小改动** - 只需要添加一个枚举方法，不需要重写整个SMB客户端
-
-这样既能解决share枚举问题，又能保持现有代码的稳定性。