Package name and folder paths are too long for usage with windows

[christian-hess-94]

Describe the bug
A clear and concise description of what the bug is.
The following path is too big to be handled by windows CMD or powershell:

reactnativekeyboardcontroller_autolinked_build/CMakeFiles/react_codegen_reactnativekeyboardcontroller.dir/C_/dev/truckup-pro/node_modules/react-native-keyboard-controller/android/build/generated/source/codegen/jni/react/renderer/components/reactnativekeyboardcontroller/reactnativekeyboardcontrollerJSI-generated.cpp.o

the app fails to build due to this problem. It is a windows limitation that cannot be fixed via regedit, because CMAKE and ninja are not up to date to match versions that take care of this limitation

Code snippet
It happens literally on app build, no code change needed

Repo for reproducing
I am currently unable to provide the code i am running to repro this. I can try to create a mock repo if really needed

To Reproduce
Steps to reproduce the behavior:

1. Install latest and try to run it with a windows device
   Expected behavior
   App runs and builds fine
   Screenshots

Smartphone (please complete the following information):

• Desktop OS: Windows 11
• Device: Android 15 emulator
• OS: Android 15
• RN version: 0.80.2
• RN architecture:Fabric
• JS engine: Hermes
• Library version: latest

Additional context
The main reason seems to be the fact that the entire package name is used multiple times in the paths. This artifically increases the path length by over 40 characters for no real benefit.

Would it be possible to refactor those names to simpler and smaller names to ensure compatibility?

In our sturcture we wishto allow for people to run the code in any platform and desktop OS, be it Linux, macOS or windows

[christian-hess-94]

Here is a more complete error msg:

BUILD FAILED in 38s
error Failed to install the app. Command failed with exit code 1: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
No modules to process in combine-js-to-schema-cli. If this is unexpected, please check if you set up your NativeComponent correctly. See combine-js-to-schema.js for how codegen finds modules. FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':app:buildCMakeDebug[armeabi-v7a]'. > com.android.ide.common.process.ProcessException: ninja: Entering directory `C:\dev\truckup-pro\android\app\.cxx\Debug\6i2vs141\armeabi-v7a' [0/2] Re-checking globbed directories... C++ build system [build] failed while executing: @echo off "C:\\Users\\chris\\AppData\\Local\\Android\\Sdk\\cmake\\3.22.1\\bin\\ninja.exe" ^ -C ^ "C:\\dev\\truckup-pro\\android\\app\\.cxx\\Debug\\6i2vs141\\armeabi-v7a" ^ appmodules ^ react_codegen_RNCSlider ^ react_codegen_reactnativekeyboardcontroller ^ react_codegen_rnpicker ^ react_codegen_rnscreens ^ react_codegen_rnsvg ^ react_codegen_safeareacontext from C:\dev\truckup-pro\android\app ninja: error: Stat(reactnativekeyboardcontroller_autolinked_build/CMakeFiles/react_codegen_reactnativekeyboardcontroller.dir/C_/dev/truckup-pro/node_modules/react-native-keyboard-controller/android/build/generated/source/codegen/jni/react/renderer/components/reactnativekeyboardcontroller/reactnativekeyboardcontrollerJSI-generated.cpp.o): Filename longer than 260 characters * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. > Get more help at https://help.gradle.org. BUILD FAILED in 38s.

[kirillzyusko]

Hey @christian-hess-94

Would it be possible to refactor those names to simpler and smaller names to ensure compatibility?

I already made it shorter in #1251 I removed reactnative prefix, but I don't think it will help you, because: reactnativekeyboardcontroller_autolinked_build/CMakeFiles/react_codegen_reactnativekeyboardcontroller.dir/C_/dev/truckup-pro/node_modules/react-native-keyboard-controller/android/build/generated/source/codegen/jni/react/renderer/components/reactnativekeyboardcontroller/reactnativekeyboardcontrollerJSI-generated.cpp.o -> 318, and new version keyboardcontroller_autolinked_build/CMakeFiles/react_codegen_keyboardcontroller.dir/C_/dev/truckup-pro/node_modules/react-native-keyboard-controller/android/build/generated/source/codegen/jni/react/renderer/components/keyboardcontroller/keyboardcontrollerJSI-generated.cpp.o -> 274 which is still higher than expected 260 symbols.

I would like to make it even shorter, like keyboardcontroller -> rnkc, but I don't really like to use abbreviations since I think it makes code more difficult for understanding and I need to have a good reasons to make this step 😓 I've tried to create a reproduction for the problem that you described in #1248, but I'm getting build failures due to react-native-worklets 🤷‍♂️

If you have a hand-on experience with windows runners/CI then I would be very grateful to you if you could create a CI job that could reproduce the problem. Then, when I have stable reproduction example I can think of which paths I need/can make shorter and I'd love to use this job in my CI to be sure, that I don't reintroduce the problem again and again. The only blocker now - is configuring this CI job 😓 Do you have any ideas how to reproduce this issue using GitHub runners?

I don't have a laptop with windows, so I can not test/reproduce this problem on my own. Even if I can borrow a laptop and ifx a problem, there is literally 0 guarantee that I accidentally will not re-introduce this problem. This is why I want to have a CI job for this type of issue...

[christian-hess-94]

hey there @kirillzyusko

Sure i can give a look when I have some down time.
I also don`t have much experience with windows runners. We actually use linux at my company to bundle the android variant of our app at the CI level (with GHA)

I am also happy to test any hotfixes you end up creating, i am down to trying to install them here on the app to see if it fixes the issue.

Do you think renaming it to RNKC for a test run might be a valid way to check if it actually fixes the issue? Kinda like a patch hotfix to see the viability of it?

Also Im not sure how CMake bundles and checks these things, but would there be a way to decrease the folder path size by changing any kind of config on it? Im not sure if some of those paths are generated by it when it`s compiling stuff for the package 🤷🏼

ALso final question, if I do go ahead and try to check some of that CI stuff, would you be ok with me using an AI agent to help me out? (again, no real experience on that regard)

[christian-hess-94]

also i think you can use rnkc as an abbreviation if you maybe start using it in the documentation as well (which is the first point for people trying to install the package). It will eventually makes it way to be the known acronym

or you could add it to the package name itself not sure 🤷🏼

also from my research, the main reason this happens is because CMAKE and ninja (which CMAKE uses) are not compliant to the 260 long path configuration, so even enabling it on your windows machine does not fix the issue. They would have to configure it at their level (which is something we cannot control) for it to work without a workaround 😢

[kirillzyusko]

Do you think renaming it to RNKC for a test run might be a valid way to check if it actually fixes the issue? Kinda like a patch hotfix to see the viability of it?

Yes, you can check what has been renamed here: #1251 and do similar changes (replace keyboardcontroller with rnkc).

ALso final question, if I do go ahead and try to check some of that CI stuff, would you be ok with me using an AI agent to help me out? (again, no real experience on that regard)

Yes, sure, I'm not against. As a starting point you can try to use changes from #1248

Feel free to experiment with renaming codegen name and CI and let me know the results 😊

[christian-hess-94]

awesome, i forked the repository here to give it a test. i can then send it to you so you can check or re-do my changes as a draft PR, thanks!

[kirillzyusko]

Sure! Will be happy to test/review 😊

[tanzeel152]

getting same issue on windows 11

[kirillzyusko]

@tanzeel152 I published 1.20.3 where I shortened name from reactnativekeyboardcontroller to keyboardcontroller. Not sure if it helps 🤷‍♂️ If not, then let me know and send the error from console here, please 🙏

[marcellov7]

@tanzeel152 I published 1.20.3 where I shortened name from reactnativekeyboardcontroller to keyboardcontroller. Not sure if it helps 🤷‍♂️ If not, then let me know and send the error from console here, please 🙏

Now it works for me! Thanks

[bondarenkod]

1. enable long path support for windows
2. override the cmake version in the win env vars: CMAKE_VERSION = 3.31.0
3. set the cmake version to 3.31.0 in the android project: mobile\DemoApp2\android\build.gradle

subprojects { p ->
  p.afterEvaluate {
    def androidExt = p.extensions.findByName("android")
    if (androidExt?.hasProperty("externalNativeBuild") &&
        androidExt.externalNativeBuild.hasProperty("cmake")) {
      androidExt.externalNativeBuild.cmake.version = "3.31.0"
    }
  }
}

Should help.