-
Notifications
You must be signed in to change notification settings - Fork 7
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
Nanaimo parse error #26
Comments
Brief update: I have tried removing the aforementioned comment line in a separate branch and this error stopped coming up. This is not ideal for the current setup, and does further suggest that it is a problem with nanaimo. |
Yes, the issue is with the trailing |
Yes, I believe so. |
Damn. I'll look into fixing this. |
Looks like this is only an issue when the trailing comma is followed directly by a comment, we already support trailing commas in every other scenario |
#27 should fix the issue, thanks for the excellent bug report! |
Oh sweet! No problem, thanks for fixing! Just need it to cascade through to fastlane, woo! |
Curious, was this a generated project file or not? seems like this should have come up before now since that seems like a fairly standard pattern of placing comments. |
Hello!
I'm getting a parse error when building an app using fastlane. Seems to be nanaimo complaining about a parse error. Not seeing anything myself that should really be causing a parse error and the project opens fine in xcode, so not sure where else to look.
Here's the error:
Seems to be referring to this block within the pbxproj file:
Note I have deliberately "censored" things here out of paranoia, but the format is maintained...
I would suspect it has something to do with the
//tag
comment at the bottom of the children block. Xcode doesn't seem to bat an eyelid about this comment line.We did not seem to have this problem with nanaimo 0.2.3, but fastlane refuses to start if I downgrade nanaimo. I cannot share the full pbxproj.
I appreciate that maybe this ought to be a question on stackoverflow but to me it does look like maybe there is a bug with nanaimo's parsing. That closing bracket does not look out of place here.
Thanks!
The text was updated successfully, but these errors were encountered: