Closed juwens closed 2 years ago
gasblack
commented
2 years ago The workaround didn't work for me. I was able to build the app downgrading xcode to v12.4 and xamarin.ios to v14.10.0.4. This will be a problem once Apple updates the version of xcode required to build the app. Is anyone working to fix this?
@Raystorm7 did you try the workaround I found? This could help you in the short term.
MattePozzy
commented
2 years ago Thank you @gasblack but I need to compile for iOS 15.x and those versions don't allow it :(
jaybiedev
commented
2 years ago This has helped my build, it might help others: using macOS-11, XCode 13.2, SDK 6_12_12 In .csproj under PropertyGroup Condition=AppleStore I added
<MtouchInterpreter>-all</MtouchInterpreter>
dais-set
commented
2 years ago Adding the -all argument didn't help us :(
pranavtiw
commented
2 years ago any update on this issue?
rolfbjarne
commented
2 years ago We need a way to reproduce the problem in order to figure out what's going on.
If anybody can provide a project we can use for this purpose (it doesn't have to be a minimal project, it can be your real project), we're eager to investigate.
Matti-Koopa
commented
2 years ago @rolfbjarne You can use mine. Remove line 97-105 (the workaround described in this thread) of "Sags Wien Neu.iOS.csproj" in order to reproduce it.
rolfbjarne
commented
2 years ago @Matti-Koopa that builds fine for me locally (I assume you're building Release for device?)
Can you execute this from a terminal:
msbuild /bl:msbuild.binlog "Sags Wien Neu.sln" /r /p:Platform=iPhone /p:Configuration=Releaseand then attach the resulting msbuild.binlog file here? That should provide me with all the version information and build output to figure out where our builds differ.
filipnavara
commented
2 years ago that builds fine for me locally (I assume you're building Release for device?)
Same here, builds fine (after changing signing certs and removing the aforementioned lines).
Matti-Koopa
commented
2 years ago Workaround seems to be: Restart VS and THEN reconnect to Mac, clean all and rebuild.
ghost
commented
2 years ago Hi @juwens. Due to inactivity, we will be closing this issue. Please feel free to re-open this issue if the issue persists. For enhanced visibility, if over 7 days have passed, please open a new issue and link this issue there. Thank you.
juwens
commented
2 years ago Wait one year without fixing the problem. Close ticket. Done.
LOL
MattePozzy
commented
2 years ago This means that Xamarin Forms is dead?
dalexsoto
commented
2 years ago Hello Folks
Wait one year without fixing the problem. Close ticket. Done. LOL
We implemented a cleanup bot to help us better maintain our issues list, we requested info (need-info) because we were not able to reproduce this ourselves but got no response yet.
This means that Xamarin Forms is dead?
Definitely no, it is still being maintained but the main focus is now MAUI.
Please if you are able to provide a test case / project that we can use to repro feel free to re-open this issue or create a new one and we will have a look at it.
dpozimski
commented
2 years ago any update on this issue? the problem still exists
dpozimski
commented
2 years ago Hello Folks
Wait one year without fixing the problem. Close ticket. Done. LOL
We implemented a cleanup bot to help us better maintain our issues list, we requested info (need-info) because we were not able to reproduce this ourselves but got no response yet.
This means that Xamarin Forms is dead?
Definitely no, it is still being maintained but the main focus is now MAUI.
Please if you are able to provide a test case / project that we can use to repro feel free to re-open this issue or create a new one and we will have a look at it.
appcenter anonimized build log with this issue: https://docs.google.com/document/d/1AQ63tMXf0bjpWR-HAUjxC_2YC6jT5Zv4bSPTI0VpnLM/edit?usp=sharing
rolfbjarne
commented
2 years ago any update on this issue? the problem still exists
ℹ️ We need a way to reproduce the problem in order to figure out what's going on. ℹ️
If anybody can provide a project we can use for this purpose (it doesn't have to be a minimal project, it can be your real project), we're eager to investigate.
I'm going to lock this issue so that this is the last comment (and thus more visible).
If you can provide a project we can use to reproduce the problem, please open a new issue and link back to this one.
I repeat: we're happy to investigate, but we need a way to reproduce it ourselves.
rolfbjarne
commented
1 year ago For the following scenario:
See #17387 for potential workarounds/solutions.
Update: might be related to this change in 14.14 #10182
pretty similar to #10855 we just recently have a problem building only our Release|arm64 build with Xamarin.ios 14.14
Might be a bad Nuget package as well.
Steps to Reproduce
Expected Behavior
Release|ARM64 doesn't fail with linking errors on _CompileToNative If it fails, there should be some hint, on which Nuget package to look at.
Actual Behavior
Release|ARM64 fails with errors/warnings
Environment
Build Logs
whole verbose log
Logging from error to end
Example Project (If Possible)