-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add extra check when resolving INFOPLIST_FILE and fail with a meaningful error message #24
Conversation
This is partly a continuation of my quest with #13. Looks like it's failing because of a very old fastlane. Can we upgrade it to something higher? |
@ianbytchek Thanks for excellent improvement! |
This isn't outdated Fastlane… Before I dig further can you help me out a little? Here you have: path = plist.gsub('$(SRCROOT)', project.path.parent.to_path)
path = path.gsub('${SRCROOT}', project.path.parent.to_path) This is what failing current tests – when variables are resolved it simply returns Do you know anything about this? Why? Doesn't Xcodeproj know that path? P. S. I can simply |
🚦 @SiarheiFedartsou green light! I went ahead with |
…ful error message
…ng INFOPLIST_FILE resolution `common_resolved_build_setting` and `common_resolved_build_setting` don't explicitly check against available xcconfig files, though they use `resolved_build_setting`, which allows to request for that, so we should use that to ensure things don't get missed from the final resolved value. Also requires fresher and updates dependencies! 🎉
@SiarheiFedartsou 👋 Can we merge this? Rebased everything onto the latest version. Looks good from my end. |
@ianbytchek Yes, of course, we can. And maybe you want to be a maintainer of this repo? :) Unfortunately, for now I don't have enough time to support this plugin... |
Feel free to add me to the maintainers list. I know my way a around the project a little, will contribute with what I can! 👍 |
@ianbytchek Thanks for accepting this proposition :) Added you as collaborator for now. As I understood it is the only thing that I can do without moving this repo to another account/organization. But it will be enough to support it. |
This takes care when INFOPLIST_FILE setting fails to resolve, which can happen here and here without an actual error raised.