copy-helper.sh script "No such file or directory" when profiling #7
Comments
|
I just tried to profile an app I have that uses this module and it worked fine. Maybe try |
|
I'm also getting I was getting other errors that I was able to fix by dragging the LaunchAtLogin.framework into the "Embedded Binaries" section in addition to the "Linked Frameworks and Libraries" section under Target > General |
|
Yeah it was weird, I think |
That's already covered by the Carthage guide:
|
|
@pjloury @jacobrosenthal I'm getting this error right now. while using Podfile. Did you use it with Podfile? Or any solution how to fix it? Edit: Solved it. Solution can be found here |
|
I still get this error, both on debug and release builds when using cocoapods. Xcode 9.4.1 I tried @deadcoder0904 proposed solution but that didn't help. The script itself runs for me so I wouldn't think there is any problem with the build phase step finding the path to the script. The real problem seems to be that when I build my workspace the LaunchAtLoginHelper.app isn't being created (like when I open the folder in Finder I see that the .app isn't there). Is it possible there is some other xcworkspace setting that I need to change to make sure the POD is building LaunchAtLoginHelper.app? Also, @sindresorhus do you happen to have a sample repo that consumes this via cocoapods as a reference? Thanks! |
|
@wes566 I happen to have made both examples with a simple project :) CocoaPods Example - https://github.com/deadcoder0904/LaunchAtLoginPod Carthage Example - https://github.com/deadcoder0904/LaunchAtLoginCart |
|
Thanks @deadcoder0904 - I tried your repo but the script failed to run after a fresh clone, so that's why I was asking @sindresorhus if there was another repo I could look at as a reference. |
|
@issuehuntfest has funded $80.00 to this issue. See it on IssueHunt |
|
|
issuehunt-oss
bot
added
the
💵 Funded on Issuehunt
|
I came across the same issue when building my app in Release mode. Not sure what consequences are going to be doing this though. |
|
@nodeful That removes the helper app and the copy script from the framework embedded in your app as you already have the helper app elsewhere in the bundle and the copy script is not useful inside your built app. |
|
@sindresorhus Have you had a chance to look at #34 as a solution to this issue? |
|
I will look at it soon. I’m on vacation at the moment. |
|
@sindresorhus have you had a chance to look at #34 ? |
|
@sweetleon I have already reviewed it. |
|
I did try @sweetleon #34 PR code and it does seem to fix the issue for me, not sure if the changes have other implications however, didn't see any so far. |
|
☝️ actually Archiving has stopped working after using code in #34 |
|
@nodeful make sure that you put the "Run Script" area all the way to the bottom. I had it at a higher position before which caused the problems for me. |
|
it was last already @frogg |
|
I can confirm the following behavior:
The project configuration is correct - the Run Script phase is after the Embed Frameworks phase. This behavior is always reproducible for me. |
|
I'd recommend switching to SPM for this, which should have fewer problems: https://github.com/sindresorhus/LaunchAtLogin/releases/tag/v4.0.0 |
|
I found that if your path(or your project name) contains spaces, "No such file or directory" problem will occur when archive. |
|
@caiwenshuo It's already wrapped in quotes in the readme: "${BUILT_PRODUCTS_DIR}/LaunchAtLogin_LaunchAtLogin.bundle/Contents/Resources/copy-helper-swiftpm.sh" |
|
i still get this issue, using SPM and yes the script is at the bottom of the build phases. |
Love the update and simplification, it pushed me to learn and reimplement my app in swift
Its has been working great, but when I try to profile the copy-helper.sh script cant be found.. any ideas?
IssueHunt Summary
Backers (Total: $80.00)
Submitted pull Requests
Become a backer now!
Or submit a pull request to get the deposits!
Tips
IssueHunt has been backed by the following sponsors. Become a sponsor
The text was updated successfully, but these errors were encountered: