## Steps to reproduce:
Update System to Xamarin.iOS cycle9 build mtouch 10.4.0.96 (cycle9: 4e31137).
Build Linkall-tvOS.csproj with fastdev enabled.
## Actual Behaviour:
App faisl to build with native linking error.
## Build Log with fastdev enabled:
## Supplemental Info:
It builds successfully when fastdev is disabled.
This issue seems to be introduced with https://github.com/xamarin/xamarin-macios/commit/e3f2685b8e2cdb163ffd0518d108f1e687491841
I can reproduce, but reverting the test-only changes from https://github.com/xamarin/xamarin-macios/commit/e3f2685b8e2cdb163ffd0518d108f1e687491841 makes the build succeed (https://gist.github.com/rolfbjarne/f3a2f393b6c92b6634d697df1d2095ba), which proves that this isn't a regression in any bits we ship.
This is the tvOS-version (and probably watchOS as well) of bug #51548 (the fix for bug #51548 was to pass '-u _symbolX' to the linker, but '-u' is not allowed for bitcode).
@Sebastien, my suggestion here would be to bump this to C10, because tvOS (and watchOS) is much less used than iOS, so the impact should be lower (and the workaround is trivial). Once fixed, we can evaluate if we want it in a C9 service release or not.
I'm fine with adding a "known issue" to C9 release notes to cover this (until fixed).
For C9: automatically disable fastdev when we find binding projects in tvOS and watchOS.
I've implemented a temporary workaround for this:
@Rolf was that to be fixed with PR 1680 ? or did we wait for it to merge to fix it ?
@Sebastien, no, this was not fixed with PR #1680.
PR with fix: https://github.com/xamarin/xamarin-macios/pull/2162
Please provide Fix Versions and Fix Details
Do NOT reopen a bug unless you can reproduce it
This issue is resolved. Verified with latest d15-3 build
## Test Log:
## Test Env :
So, what... fastdev will never be supported if you have more than one binding project enabled? Two flagship features are incompatible and disabling one is the solution?
@Jahmai, disabling fastdev was a temporary workaround; the bug has already been fixed properly and the workaround has been deleted (see comment #11).
Compilation was failing with an error that lead me here as of the latest Xamarin.iOS on the date I made that comment. So when exactly was that pull request released?
Sorry, not failing, just stating it was disabled.
@Jahmai, sorry, I was confused, this bug refers to a somewhat different issue than what you're running into, and we ended up talking about different things.
You're running into the workaround for bug #52727, which has not been fixed properly (the workaround is still in place). I've filed a new issue (https://github.com/xamarin/xamarin-macios/issues/3174) for us to look into fixing this somehow.