FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':dr.pogodin_react-native-fs:compileReleaseKotlin'.

[imranAfzal43A]

Eas build failed and local build failed. Here's the logs:

FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':dr.pogodin_react-native-fs:compileReleaseKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$Gradn
Compilation error. See log for more details

I am using react native expo 52

[birdofpreyru]

I don't support Expo (although, I guess, it should work) 🤷‍♂
Also the support of old react architecture has been dropped in the last release. If you are trying to use it with the old arch then it is the problem.

[imranAfzal43A]

It works with expo in development build. I have been using it for the last few months without any issue. But now suddenly, it stops bundling. I have enabled the new architecture, but still, it's not bundling. Here's the more logs;
Task :dr.pogodin_react-native-fs:compileReleaseKotlin FAILED
e: file:///Users/imranjutt/Desktop/githubrepo/hapos/node_modules/@dr.pogodin/react-native-fs/android/src/main/java/com/drpogodin/reactnativefs/ReactNativeFsPackage.kt:22:47 None of the following functions can be called with the arguments supplied:
public constructor ReactModuleInfo(_name: String, _className: String, _canOverrideExistingModule: Boolean, _needsEagerInit: Boolean, isCxxModule: Boolean, isTurboModule: Boolean) defined in com.facebook.react.module.model.ReactModuleInfo
public constructor ReactModuleInfo(name: String, className: String, canOverrideExistingModule: Boolean, needsEagerInit: Boolean, hasConstants: Boolean, isCxxModule: Boolean, isTurboModule: Boolean) defined in com.facebook.react.module.model.ReactModuleInfo

[MrXyfir]

npm install --save @dr.pogodin/react-native-fs@v2.30.3

It'd probably be better if a new (old) build was released as 2.32.0 and then 2.31 gets released as 3 so that people don't unexpectedly hit this issue.

[birdofpreyru]

¯\_(ツ)_/¯

It'd probably be better if Meta, or Expo place me on their payroll with a nice compensation, or every user actively donate me, so that I actually had a capacity to bother myself with what is convenient for every user of this and other RN libraries I work on 🤣 As of now, I have to spend 40h/week working for commercial projects that have nothing to do with React Native / this library; and even my pet projects I do in my free time, for which I need this library, and which are the reason I forked and maintain it, also require a bunch of efforts not related to this lib.

You may guess, what do I think when ppl do not read release notes carefully, do not put efforts into investigating themselves the issues with this library, and insist on better support, more careful version management, etc. :)

[imranAfzal43A]

npm install --save @dr.pogodin/react-native-fs@v2.30.3

It'd probably be better if a new (old) build was released as 2.32.0 and then 2.31 gets released as 3 so that people don't unexpectedly hit this issue.

I used this version with and without the new architecture enabled. But the build failed again.

[MrXyfir]

@imranAfzal43A Are you sure it's the same issue? After I fixed this I got another issue from the root expo package with some Kotlin versioning issue or something like that. I had to downgrade Expo as well to 52.0.18. If that's not the issue, try clearing out your gradle and expo cache or something...

[imranAfzal43A]

Actually, I have removed this package and am using the Expo file system.

…

On Sun, Feb 16, 2025 at 4:00 AM xyfir ***@***.***> wrote: @imranAfzal43A <https://github.com/imranAfzal43A> Are you sure it's the same issue? After I fixed this I got another issue from the root expo package with some Kotlin versioning issue or something like that. I had to downgrade Expo as well to 52.0.18. If that's not the issue, try clearing out your gradle and expo cache or something... — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2QL4DSDEGZKSCJUGJQDY3T2P7BHPAVCNFSM6AAAAABXE5KCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGEZTQNJRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***> [image: MrXyfir]*MrXyfir* left a comment (birdofpreyru/react-native-fs#106) <#106 (comment)> @imranAfzal43A <https://github.com/imranAfzal43A> Are you sure it's the same issue? After I fixed this I got another issue from the root expo package with some Kotlin versioning issue or something like that. I had to downgrade Expo as well to 52.0.18. If that's not the issue, try clearing out your gradle and expo cache or something... — Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2QL4DSDEGZKSCJUGJQDY3T2P7BHPAVCNFSM6AAAAABXE5KCMKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRRGEZTQNJRG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Tchaikovsky1114]

First of all, thank you for your hard work.

I am a user of RN version 76.5 and am unable to migrate to version 77.. due to core libraries not supporting new-architecture.

I am currently experiencing the same error as this issue.
As @MrXyfir said, it happened while doing a fresh build, and it's been unresolved for quite some time.

If you can handle this, I would appreciate it if you could fix this once

[birdofpreyru]

thank you for your hard work.

Thanks! 🤗

due to core libraries not supporting new-architecture

So... owners of other libraries fail to put in necessary efforts to keep up with the current RN developments, and you ask the owner of a library who already puts in that, non compensated effort to keep up with the current RN developments, to walk an extra mile to also make it compatible with legacy stuff 🤔

If you can handle this

I sure can, theoretically...

I would appreciate it if you could fix this once

... but practically, I would appreciate users actively sponsoring my work, otherwise I better invest my time into anything that generate return value to me... thus, no to free support of legacy, long deprecated stuff; no free support for Expo (for-profit business) eco-system 🤷‍♂

[Tchaikovsky1114]

i completely understand the sentiment.
you're the heir to a really good react-native-fs library. i'd appreciate it if you'd take a look at it once in a while, when you're free.
i'll be sure to sponsor you someday.

with gratitude.

[MrXyfir]

@Tchaikovsky1114 you'll just have to downgrade to the previous version and make sure to pin the version number in your package.json because otherwise npm will think it's a safe upgrade with no breaking changes and automatically upgrade it on you

[mukul-sharma085]

what kotlin version does this package- "@dr.pogodin/react-native-fs": "^2.32.1", supports? and what version is of package "@dr.pogodin/react-native-fs" is compatible with RN - "0.76.5" - and build.gradle -------

buildscript {
   ext {
       buildToolsVersion = "35.0.0"
       minSdkVersion = 24
       compileSdkVersion = 35
       targetSdkVersion = 34
       ndkVersion = "26.1.10909125"
       kotlinVersion = "1.9.24"
      
   }
   repositories {
       google()
       mavenCentral()
   }
   dependencies {
       classpath("com.android.tools.build:gradle")
       classpath("com.facebook.react:react-native-gradle-plugin")
       classpath("org.jetbrains.kotlin:kotlin-gradle-plugin")
      
   }
}

apply plugin: "com.facebook.react.rootproject"