-
Notifications
You must be signed in to change notification settings - Fork 303
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
Problems with .sh script permissions #1840
Comments
Hi! Thanks for opening your first issue here! 😄 |
Hmm, IIRC you do need to select a provisioning profile when developing ios flutter. Does it work if we just follow what Flutter says and select a provisioning profile? |
I don't have a mac, but theoretically with --no-signcode there should be no need for a provisioning profile. Without using flutter_rust_bridge, it's true that building ipa can be done without it. Or with using this https://github.com/project-violet/violet to run action, it's also build ipa successfully without provisioning profile. I've confirmed this by forking it and run it mannuly. |
https://github.com/canxin121/violet This is my fork from https://github.com/project-violet/violet, and it runs well. action result: https://github.com/canxin121/violet/actions/runs/8451208039 |
Hmm, what about |
I found something very strange. https://github.com/canxin121/myapp But now there is a very strange situation, the same GitHub action workflow builds flutter's ios ipa in the second repo, but the first repo gives me the following error: Then I tried to use --mirror to duplicate the second repo exactly, and it builds the ios ipa fine. I will try to use --verbose right now. |
This is the action for a failed build and --verbose: https://github.com/canxin121/myapp/actions/runs/8453774701/job/23157246140; this is the action for a successful build and --verbose: https://github.com/canxin122/myapp/actions/runs/8453759931/job/23157195246 |
The failed one says:
So it looks like your |
It's really a file permissions issue, when my project is created under windows, the permissions on This can indeed be fixed by adding the line |
Origin issue: fzyzcjy/flutter_rust_bridge#1840 Origin pr: fzyzcjy/flutter_rust_bridge#1842 Simple problem description: if you create a new flutter_rust project in windows, the sh script is automatically created, but the executable permissions cannot be set. When moving this project to macOS and executing `flutter build ios` to build ipa files the process crashes due to insufficient sh script permissions. This permission problem can be circumvented by `sh script.sh` rather than `script.sh` As verified by Github Action's macOS Runner, the modified cargokit works fine for building ipa apps using the flutter_rust project created on windows. [Action Link](https://github.com/canxin121/new_app_test/actions/runs/8466294309)
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new issue. |
Describe the bug
If the project is created under windows, then the sh script permissions cannot be changed to
0o755
, and when these under-privileged sh scripts are uploaded to github and executed when runningflutter build ios
in the MacOs Runner using Github Actions, the build process crashes due to the sh script permission issue and crashes.(Ps. There seems to be a big problem with Flutter's logging system, when
flutter build ios
crashes due to sh permissions issues, Flutter incorrectly reportsBuilding a deployable iOS app requires a selected Development Team with a Please ensure that a Development Team is selected by.
)Steps to reproduce
flutter_rust_bridge_codegen create new_app
to create a new demo project.The workflow file used above: https://github.com/canxin121/new_app/blob/main/.github/workflows/build.yml
Logs
with --verbose
without --verbose:
Expected behavior
sh scripts should be secured with executable permissions before they are used.
OS
Windows and MacOS
The text was updated successfully, but these errors were encountered: