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

Fix iOS Fastlane build when using Unity Cloud Diagnostics #383

Merged
merged 1 commit into from
Apr 11, 2022

Conversation

gnomesley
Copy link
Contributor

Fixes error described here: https://forum.unity.com/threads/ios-build-is-failing-seems-like-a-fastlane-problem-not-sure-how-to-proceed.682201/

Changes

  • Add username and password to mac build.sh

Checklist

  • Read the contribution guide and accept the code of conduct
  • Readme (updated or not needed)
  • Tests (added, updated or not needed)

@github-actions
Copy link

Cat Gif

Copy link
Member

@webbertakken webbertakken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about these changes.

Comment on lines +133 to +134
-username "$UNITY_EMAIL" \
-password "$UNITY_PASSWORD" \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are already passed during the activate step. Any reason why we'd need to pass them here too?

@webbertakken
Copy link
Member

The description is not clear enough as to what exactly it fixes under which circumstances.

We currently have successful builds in iOS.

What would be interesting to know is how Unity Cloud Diagnostics is different and which exact post you're referring to in that long thread that is seemingly about a bug in Unity and little related to the code changes. I could be mistaken and would love to be educated.

@gnomesley
Copy link
Contributor Author

The post I'm referring to is the first post in the thread.
I get this error during the build_app step in Fastlane:

6842: ▸ Running script 'Process symbols'
6843: ▸ ** ARCHIVE FAILED **
6844: ▸ The following build commands failed:
6845: ▸ PhaseScriptExecution Process\ symbols /BUILD_PATH/Library/Developer/Xcode/DerivedData/Unity-iPhone-gjomesfkojewdbcqkxboenqtbzba/Build/Intermediates.noindex/ArchiveIntermediates/Unity-iPhone/IntermediateBuildFilesPath/Unity-iPhone.build/Release-iphoneos/Unity-iPhone.build/Script-F6E34F12805380276D47C8E3.sh
6846: ▸ (1 failure)

The solution from the thread is to add the username and password arguments when calling Unity through batchmode.

Copy link
Member

@webbertakken webbertakken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional context.

Since for MacOS the UNITY_EMAIL and UNITY_PASSWORD are always passed we don't need conditionals for whether or not to pass them to the CLI.

Therefor I think we're safe to merge this.

@webbertakken
Copy link
Member

By the way can you confirm this solution works for you?

You can try by using

  uses: game-ci/unity-builder@b081e3320cb00d466b3c95c649a31e7da227cf29
  with:
    your: vars

@gnomesley
Copy link
Contributor Author

Sure thing, I'll let you know when the build is done.

@gnomesley
Copy link
Contributor Author

Looks like it worked. 🙂

@webbertakken webbertakken merged commit 4be5d2d into game-ci:main Apr 11, 2022
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

Successfully merging this pull request may close these issues.

2 participants