react-native-image-marker does not support the react native version 0.77.0

[codewithsujeet]

please update the package as soon as possible

Filename is MarkTextOptions.kt

package com.jimmydaddy.imagemarker.base

import com.facebook.react.bridge.Promise
import com.facebook.react.bridge.ReadableMap
import com.facebook.react.bridge.ReadableArray

class MarkTextOptions(options: ReadableMap) : Options(options) {
val watermarkTexts: List

init {
    // Safely get the "watermarkTexts" array
    val waterMarkTextsMap = options.getArray("watermarkTexts")
    if (waterMarkTextsMap != null && waterMarkTextsMap.size() > 0) {
        watermarkTexts = List(waterMarkTextsMap.size()) { index ->
            val textMap = waterMarkTextsMap.getMap(index)
                ?: throw IllegalArgumentException("Invalid TextOptions in watermarkTexts at index $index")
            TextOptions(textMap) // Pass only non-null ReadableMap
        }
    } else {
        // Initialize with an empty list if "watermarkTexts" is not provided
        watermarkTexts = emptyList()
    }
}

companion object {
    @JvmStatic
    fun checkParams(opts: ReadableMap, promise: Promise): MarkTextOptions? {
        return try {
            MarkTextOptions(opts)
        } catch (e: MarkerError) {
            promise.reject(e.getErrorCode(), e.getErrMsg())
            null
        } catch (e: IllegalArgumentException) {
            promise.reject("INVALID_OPTIONS", e.message)
            null
        }
    }
}

}

when i change in this file with above code and it is working in android but i m not sure this code is works on ios or not

[NourMoftah]

I tested this on Android with React Native 0.77.x, and replacing MarkTextOptions.kt with the following implementation fixed the issue for me.

The main change is that it safely handles a nullable watermarkTexts array instead of assuming it's always present.

// your code here



However, I haven't been able to verify the behavior on iOS yet, since this change only affects the Android Kotlin implementation.

Could one of the maintainers or someone using iOS confirm whether any corresponding changes are needed on the iOS side, or if this Android-only fix is sufficient?