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
Originally posted by msarkrish August 28, 2024
I'm using rps for running scripts which is defined in pubspec.yaml file.
I'm using a mac system and i haven't added the flutter path to zshrc file.
Inside Android Studio settings, I have mentioned the specific flutter version. I use fvm use command to specify specific version for each project and using fvm flutter command to run the application from command prompt.
Everything is working fine, till i started to use rps. After defined the scripts in pubspec yaml file, i try to run it using rps command but it is not working and it saying that
/Users/username/.pub-cache/bin/rps: line 8: dart: command not found
If I add the flutter path to zshrc file then rps command is working. But If i add specific flutter version to zshrc file then if i run another flutter project then also it will take the same version.
Is there any way to resolve this?
The text was updated successfully, but these errors were encountered:
Discussed in #770
Originally posted by msarkrish August 28, 2024
I'm using rps for running scripts which is defined in pubspec.yaml file.
I'm using a mac system and i haven't added the flutter path to zshrc file.
Inside Android Studio settings, I have mentioned the specific flutter version. I use fvm use command to specify specific version for each project and using fvm flutter command to run the application from command prompt.
Everything is working fine, till i started to use rps. After defined the scripts in pubspec yaml file, i try to run it using rps command but it is not working and it saying that
If I add the flutter path to zshrc file then rps command is working. But If i add specific flutter version to zshrc file then if i run another flutter project then also it will take the same version.
Is there any way to resolve this?
The text was updated successfully, but these errors were encountered: