PHImageManager.h Xamarin IOS Build error

#1

Bitrise Build Issue Report template

Description of the issue

There is apparently a known issue with the xcode beta with the PhotoUI headers. And this seems to be the error we are getting on our builds starting the other day.

Environment:

Where did the issue happen?

Xamarin iOS
Visual Studio for Mac, Beta channel

Which build Step causes the issue and which version of the step?

10 nunit runner

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : NO
  • Does the issue happen sporadically, or every time? : Everytime
  • Does upgrading the build Step to the latest version help? : step is running on latest version
  • When did the issue start? : Over the weekend

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

No in the sense that the build works fine because I am not running xcode beta

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

No in the sense that the build works fine because I am not running xcode beta

Build log

0 Likes

#2

Hi @MajinFro,

Sorry to hear about this and thanks for reporting, I’m not sure how much we can do if this is truly a problem with Xcode itself though :frowning:

0 Likes

closed #3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

0 Likes