![]() ![]() NET 6+ this is a different story NuGet packages. For the old Xamarin SDKs this was not much of a problem since all of it shipped in a single package iOS and macOS support but for. In a nutshell Xcode 14 is shipping iOS and tvOS 16.0 and MacCat 15.4 and macOS 12.4 SDKs if you see this from the MAUI standpoint is kind of complicated since it means some code needs 16.0 but MacCat SDK is not there. Sorry folks we are still ironing out all the details that Xcode 14.0 brought to the table, it broke some assumptions that we had regarding our CI infrastructure and how we build the SDKs. My gut says that the workload system is an overall liability, otherwise you would cut a preview nuget and let people continue on their way with the prerelease-bits. We aren't live yet with the app so its not "showstopping" bad right now, but what is ios 17 going to look like? What is the issue here, and what can we do to remedy it in the future when we know we will come up against this issue again? ![]() Now we are stuck in a very tough position of Maui definitely not being GA, and legacy being unsupported. SIDENOTE: Because of the signaling that Xamarin Forms was EOL basically as soon as Maui hit GA, we did our greenfield app in Maui. ![]() It also leaves me looking extremely incompetent as the team lead when my only answer is for when its going to come out is "I dont know, I hope sometime soon". It is very hard to continue to advocate for Maui as a solution when these sorts of things are left to linger and my only recourse is to hope its fixed the next day I come into the office. I understand the lack of resources on the team, and the workload the team is under, but the lack of communication for such a high priority / high impact issue is extremely concerning for me and my company. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |