“Visual Studio Maui IOS”

https://imgur.com/SwinOxzI too have this problem. Using Visual Studio, added all the icons to the asset thing. It says I don't have 76x76 icon (plus a couple others) yet I do. Trying to get a build up on ITunes Connect (I think that is the name). So much work! Have been working on this for three days, hopefully getting close.

[quote='868011022, chrismuench, /thread/769472?answerId=868011022#868011022, /profile/chrismuench'] it is clearly still a bug in Xcode 26 [/quote] Absolutely. There’s no argument about that. [quote='868011022, chrismuench, /thread/769472?answerId=868011022#868011022, /profile/chrismuench'] which leads to deployment failure from my Visual Studio on my PC. [/quote] With Xcode, you don’t need to explicitly install the profile because the system picks it up from the embedded.mobileprovision file embedded within the built app. I don’t know enough about how Visual Studio builds and installs apps to offer any insight into why that’s not working for it. My advice is that you escalate this via the support channel for that tooling. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello Albert2018,Templates in C++ are an advanced topic. You would have to post the source for anyone to be able to make any recommendations. When using templates, C++ can get very strange. What you describe could very well be correct interpretation of your code. Perhaps Visual Studio is using an older C++ standard by default. There is no way to tell without said code. If it is crashing, then there is likely a bug somewhere.

Hello everyone, I'm experiencing the same issue mentioned, but it occurs only with .NET MAUI builds. My older Xamarin builds, which I compile using Xcode 15.2 on macOS 13, work perfectly, while the .NET MAUI builds—compiled with Xcode 16.1 on macOS 14—start encountering problems yesterday in the TestFlight app. Moreover, since yesterday, even the old builds that were working fine until then have stopped functioning. I had to mark all the MAUI builds as invalid so that only the Xamarin builds remained, and once I did that, TestFlight started working again. I'm curious if anyone else has noticed similar issues when using .NET MAUI on the latest Xcode and macOS versions. Could this be due to changes in the new build environment or potential incompatibilities specific to .NET MAUI? Additionally, what debugging steps or workarounds have you tried so far?

Same here, but as AirborneMarik mentioned above they have a workaround posted on the Visual Studio developer community in this thread: https://developercommunity.visualstudio.com/t/Cannot-add-Apple-Account-VS-2002-Enter/10773193 I believe the primary workaround is that you can still manually specify your provisioning profile and signing certificate even though Visual Studio doesn't let you sign in to your Apple developer account. This workaround came too late for me, but I was able to build, debug and deploy on the mac using a combination of the dotnet CLI, VSCode, and Xcode. I still used Windows to do Android development and deployment, and just used the mac for iOS. I did run into a problem where the publish was failing on Windows because it wasn't able to do the iOS build, so I ended up setting up my .csproject file so that it only targets iOS if running on a mac, and only targets Android if running on Windows. Oh, and there seems to be an issu

#include using namespace std; int main() { cout << welcome to C++!; return 0; } There's nothing wrong with that. (Well, except for the lack of n in your string.) The error must be with how you are compiling it, i.e. something in the Visual Studio configuration or usage. As MobileTen writes, this forum is not the best place for that discussion; we are mostly Xcode users.

Just to link back from here that this maybe also affects dotnet MAUI still: https://github.com/dotnet/maui/issues/26650 And that also the separator reappears when the window is moved - even if it has been set to hidden: https://feedbackassistant.apple.com/feedback/18161892

Just to add to the pile-on, no real extra information, I'm having the exact same thing happening to me (stack trace looks identical), all simulators running iOS 15.4. With the 13 series simulators it can sometimes go away with a clean code rebuild but that doesn't seem to work when using the 12 series simulators. Building using Xamarin and Visual Studio for Mac rather than XCode, if that makes a difference. Running the exact same code on an iPhone 11 simulator running iOS 13.7 seems to work fine. Not sure if this is useful information but hopefully Apple can address this soon as it appears to be an issue with the simulators.