Closed heitorfr closed 3 years ago
Hy @heitorfr
Thanks for the heads up, I created a task for the tooling team to check out the issue and make the appropriate changes.
We are also facing the same problem. Is there an ETA of when this problem will be fixed?
Hi there @gholias!
We can't give you an ETA yet, but we are currently looking into the problem and will notify you as soon as we have something! 🙂
I'm also experiencing the same issue. @gholias @Roland-Bak Have you found a workaround?
My fix was hardcode the app name to match the scheme name
Hello there, I'm a bot. On behalf of the community I thank you for opening this issue.
To help our human contributors focus on the most relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 90 days, so I marked it as stale.
The community would appreciate if you could check if the issue still persists. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me".
If no comment left within 21 days, this issue will be closed.
I'll close this issue as it doesn't seem to be relevant anymore. We believe an old issue probably has a bunch of context that's no longer relevant, therefore, if the problem still persists, please open a new issue.
In v0.10.0. When searching for app paths to copy to deploy dir, the step based the app name on the target name i.e. if Target is MyTarget, it will search for MyTarget.app.
It should instead observe the PRODUCT_NAME xcode setting.