Skip to content
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

Very hard to figure out errors in Xib2Nib output #2924

Open
marczellm opened this issue Mar 3, 2019 · 2 comments
Open

Very hard to figure out errors in Xib2Nib output #2924

marczellm opened this issue Mar 3, 2019 · 2 comments

Comments

@marczellm
Copy link

Xib2Nib errors out on one of our xib files. I started commenting out parts of the file and calling Xib2Nib from the command line until I seemed to find the offending part and left it commented out. Now I can call xib2nib from the command line and it successfully makes a nib.

However if I run the VS build, at the end the xib compilation still fails with the same error.

Another problem is that the error message is more than 100 lines long therefore impossible to interpret.
I cannot post the xib file because of company policy.

@DHowett-MSFT
Copy link

Hi @marczellm,
Thanks for reporting this! If you'd feel more comfortable e-mailing about this issue, I'm at [email protected].

If not, I'd love to work with you to find a minimal repro case. Can you share the error message?

@marczellm
Copy link
Author

Okay I misinterpreted the build output. Turns out that during the Visual Studio build, xib2nib dumps all its output in the console but without ever specifying which xib file it errored out on. (The console listed all the xib files first, and then listed all the errors.)

So this becomes a feature request:

@marczellm marczellm changed the title Xib2Nib seems to change its behaviour based on call circumstances Very hard to figure out errors in Xib2Nib output Mar 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants