-
Notifications
You must be signed in to change notification settings - Fork 71
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
Unimplemented element #62
Comments
Thanks for the report! I just tried running However, we did just release a new version of the plist gem, so there is a possibility it broke something in a non-obvious way. Can you check the versions of Ruby, plist, and fastlane that are installed on each machine? I think this will do it:
|
Thanks for your help!
$ ruby -v
ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin22]
|
On the computer where it does not work
Actually now I see that the ruby version is way more updated on one machine than the other BUT the Thankss <3 |
OK, it looks like a different version of the plist gem is installed on the two machines. On the machine where it is not working, can you try the following:
Then see if you can still reproduce the error. If that doesn't change anything, then the next thing you could try is updating fastlane itself. I see that the machine that is working is using an older version of fastlane. Could you verify that it still works after updating to fastlane 2.212.1? Finally: after digging into how fastlane and On the machine where it is not working, do you have any environment variable set that could be causing Xcode tools to emit verbose logs? Try running this command:
And scan through the output to see if anything looks like it could be related to Xcode that is different between the two machines. |
Also, can you share the |
Hey @mattbrictson !
One thing I noticed - and seems to be the only difference between the output of both machines - is that on the machine that does not work, I get some log about
While on the other it's just a bunch of steps mixed up. I would say that this is nothing related to your project so, if you don't have clue or any hint, I would say to close this issue. Thanks once again! |
@Destrocamil thanks for the additional info. Based on your logs and my analysis of the fastlane source code, I think this is ultimately a fastlane problem and not something that can or should be dealt with in the plist gem. Here's what I found:
The problem (in my opinion) is that fastlane uses If altool prints debug messages, progress messages, or other text on stderr (e.g. "Unable to find transporter..."), this gets combined with the XML plist into a single string. That combination of log messages and plist data is not valid XML. When invalid XML is passed to I think you should open a bug report in the fastlane repository. Feel free to link to or copy the contents of this comment. As a workaround, you could continue troubleshooting why altool one machine is outputting different log messages. If you can somehow figure out how to suppress those messages, that may fix the XML parsing. This is my first encounter with fastlane and altool, so I probably can't offer much insight. |
Hello,
I um using Fastline with some Fastlane action, mainly Gym and Notarize to build and notarize some macOS applications.
Currently, I have 2 computer: both with same XCode versions, both with same macOS Ventura versions.
The installation of fastlane was made equally across the machines.
I have all the required env variables to perform notarization in place.
On one computer, it works like a charm.
On the other, notarization seems to finish with no errors (the notarization in its core) but then I got a
Unimplemented element
error.Here is part of the log
I am out of ideas.
Thanks a lot for your help
The text was updated successfully, but these errors were encountered: