-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When Entry control get focus app crash #21051
Comments
Just adding an Entry in any Layout?, are not using a different parent?. Can see UITableView (ListView, TabletView) in the logs. |
Confirmed this is happening but I also see this happening in a .NET for iOS project without .NET MAUI. Going to try Xcode now. Update: Xcode directly with Obj-C seems to work so based off this I would think its something on the .NET for iOS level. Asking that team to have a look at this issue! |
I have the same issue |
Hello. I'm trying to understand what the fix is for the IOS simulator crashing when the entry control is focused. |
The fix is to use a simulator that's iOS 17.2 or below. you can install different version of the simulator from Xcode. |
@JoacimWall I installed iOS 17.0 and the issue still persists. |
Hi |
Same issue here, crashes just in iOS everytime an Entry is focused |
@JoacimWall Using iOS 17.2 actually solved the crashing of the simulators. Thanks alot man! @leonedev Try this solution. |
@IngenieroInformatico28 Yes I forgot to reply, it works as usual with 17.2 simulator, thanks! |
Since I don't have a physical iPhone with iOS 17 right now, Does anyone have an idea if this issue is happening on physical devices with iOS 17.4 too? |
@FabriBertani for me in phisical device with 17.4 works fine. Only crash in simulator |
As a workaround, using iPhoneSimulator with iOS 17.0 works as well. |
I don't understand why there is still no fix for this problem. |
@ovoelke yes it is absurd |
I have the latest version of XCode and was able to install both the 17.2 and 17.4 emulators simultaneously. The 17.2 emulator works for testing. The app does crash with 17.4 emulator but does not crash on 17.4 devices. The tooling just hasn't caught up yet. I can still move forward with development though. My set up is Visual Studio 2022 17.9.1 Community on a Windows box linked to XCode on a Mac Mini. I choose the 17.2 iPhone simulators in the VS debugging menu. |
This is still a very real and painful issue. Installed the latest VS preview 2022 and added all the latest nugets (8.021 I think?) today but the problem REMAINS. The whole process with iOS development with a paired mac has, frankly, been TOTALLY dreadful. Deleting bin & obj catalogues, restarting VS and deleting the app before you can run again - just to see if the "padding is done right" is totally DREADFUL. Why isn't Microsoft investing more in this? You can't compete with competent frameworks like Flutter with this!!!!! So dishearthening. |
|
I haven't dug into the details here too closely but it looks like I was hitting this issue as well. The workaround worked for me, but the EDIT: Oops, I guess I meant the workaround mentioned in runtime/#98941 as I haven't setup the older simulators yet (though that might be preferable to modifying my linker settings) |
App crashes when using Editor, Entry, and Picker |
I recently updated to dotnet version 8.0.300. I then created another new project (I'm currently using Rider as an IDE) and added an entry control. The app no longer crashes under iOS 17.5. Can anyone confirm this? |
Description
After install of IOS 17.4 in simulator and new maui project with a Entry control crash when you tapp inside the entry control .
Steps to Reproduce
Link to public reproduction project repository
Not needed just a new stadard project nedded
Version with bug
8.0.7 SR2
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
iOS
Affected platform versions
Xamarin.iOS Version: 16.4.0.23, Simulator version 17.4
Did you find any workaround?
no
Relevant log output
The text was updated successfully, but these errors were encountered: