Skip to content

folder structure reversal - app not booting up #2630

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
a-dominiak opened this issue Mar 19, 2025 · 1 comment
Open

folder structure reversal - app not booting up #2630

a-dominiak opened this issue Mar 19, 2025 · 1 comment
Labels
question Further information is requested

Comments

@a-dominiak
Copy link

Ask your Question

Hi!
Our client we have a case where we need to reverse folders' structure in RN project (client's demand - also a brownfield app to be).
So that RN wouldn't wrap android and ios folder, but react-native would be a folder inside android project's folder.
I've created a boilerplate RN app (no expo) with cli and reversed the structure of file, app stopped running but that was expected, I've run npx react-native doctor and it showed it had problem with gradlew and android SDK. I've fixed gradlew, but right now I'm still facing android SDK problem and app won't boot up.

for npx react-native doctor part it shows:

✖ Android SDK - Required for building and installing your app on Android
   - Versions found: N/A
   - Version supported: Not Found

for npm run android part it shows:

error Failed to install the app. Command failed with exit code 1: ./gradlew app:installDebug -PreactNativeDevServerPort=8081
ERROR: autolinkLibrariesFromCommand: process npx @react-native-community/cli config exited with error code: 1 FAILURE: Build failed with an exception. * Where:
Settings file '/Users/adamdominiak/rnpoc/android/settings.gradle' line: 3 * What went wrong:
A problem occurred evaluating settings 'android'.
> ERROR: autolinkLibrariesFromCommand: process npx @react-native-community/cli config exited with error code: 1 * Try:

I've seen same case here: #2490 (comment), but it doesn't solve the issue - probably due to the fact that still there's some path mismatch.

@a-dominiak a-dominiak added the question Further information is requested label Mar 19, 2025
@gowtham207
Copy link

Hi,
I have removed the "file:" using the npm unlink command it works for mee

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants