We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
1.5.2
First of all, melos is a great package and it has already improved my workflow!
melos
Whenever I build my macOS Flutter app all melos commands in my workspace fail with the following error:
Unhandled exception: FileSystemException: Cannot resolve symbolic links, path = '/Users/johannes/dev/arro/packages/app/build/macos/Build/Products/Debug/PromisesObjC/FBLPromises.framework/PrivateHeaders/PrivateHeaders' (OS Error: No such file or directory, errno = 2) #0 FileSystemEntity.resolveSymbolicLinks.<anonymous closure> (dart:io/file_system_entity.dart:318:9) <asynchronous suspension> #1 DirectoryUtils.listConditionallyRecursive.recurse (package:melos/src/common/utils.dart:393:37) <asynchronous suspension>
When I run flutter clean that removes the flutter macOS build everything works fine again.
flutter clean
The melos command should run without having to clean the build.
No response
The text was updated successfully, but these errors were encountered:
fix: handle unresolvable symbolic links
ed37260
Fixes invertase#269
fix: handle unresolvable symbolic links (#280)
7009436
Fixes #269
blaugold
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Version
1.5.2
Description
First of all,
melos
is a great package and it has already improved my workflow!Whenever I build my macOS Flutter app all melos commands in my workspace fail with the following error:
When I run
flutter clean
that removes the flutter macOS build everything works fine again.Steps to reproduce
Expected behavior
The melos command should run without having to clean the build.
Screenshots
No response
Additional context and comments
No response
The text was updated successfully, but these errors were encountered: