You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Running npx react-native-rename@latest returns the error Directory should be created using "react-native init".
To Reproduce
Steps to reproduce the behavior:
run react-native init
delete the android directory
run react-native-rename
Expected behavior
I would expect it to ignore android renames if the android directory is missing, same with iOS. At the very least it should ignore android if I use --iosBundleID instead of -b
The text was updated successfully, but these errors were encountered:
I can confirm that the inverse of this problem is also true:
I have an Android-only app in React Native. Running the npx react-native-rename command fails with Directory should be created using "react-native init".
As a temporary workaround, I initialized a new project with react-native init and copy/pasted the auto-generated ios folder into my existing project. After doing this, npx react-native-rename works!
...This isn't ideal, since I now have a useless ios folder (and @iotashan, you would have a useless android folder if you did this for your project), but this temp-fix did unblock me for local development with this package.
Describe the bug
Running npx react-native-rename@latest returns the error
Directory should be created using "react-native init".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect it to ignore android renames if the android directory is missing, same with iOS. At the very least it should ignore android if I use --iosBundleID instead of -b
The text was updated successfully, but these errors were encountered: