After I updated my ios to ios26.1 Icons are bigger in homepage and alarm is alarming literally since it is way much bigger it occupies the whole screen of my phone. Also, accessibility menu like lock screen, home, screenshot needs to double tap before it functions properly. Its annoying
Search results for
Visual Studio Maui IOS
105,617 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hmm, the app works as expected on my iPhone with iOS 26.0.1. The iPhone simulator is on iOS 26.0
Topic:
Machine Learning & AI
SubTopic:
Core ML
Tags:
The crash reports (__TPRO_CONST, specifically,) indicates that dyld was trying to write the read-only memory address, which I believe is a known bug that happens on iOS 18.1, and has been fixed in the iOS 18.4 and later. Hecne the best solution is to update the system version. Best, —— Ziqiao Chen Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
General
Tags:
When scanning multiple rooms (10+) in a single structure using ARWorldMap for coordinate space consistency, RoomCaptureSession throws CaptureError.exceedSceneSizeLimit. The instructions here (https://developer.apple.com/documentation/roomplan/scanning-the-rooms-of-a-single-structure) provide exactly what I am doing to keep the underlying ARSession alive (by calling captureSession.stop(pause: false)) and save the results before a user moves to the next room. Scanning 11 or so rooms will cause the user to hit the exceedSceneSizeLimit error. The ARWorldMap is about 58 MB and always is around this size when hitting this issue. No anchors are present and all the data seems to be from tracking data. On iPad devices (where I do not see this issue) the ARWorldMap grows as a significantly slower rate in size. I save the ARWorldMap after each room is scanned and confirmed by the user. If I use the ARMap to initialize the ARSession (as described in the docs) the session will immediately error with exceedSceneSizeLimit o
You can add your own model with MLX. I've used MLX_LM.lora to 'upgrade' Mistral-7B-Instruct-v0.3-4bit with my own content. The 'adapter' folder that is created can be added to the original model with mlx_lm.fuse and tested with mlx_lm.generate in the Terminal. I then added the resulting Models folder into my macOS/iOS Swift app. The app works on my Mac as expected. It worked on my iPhone a few days ago but now crashes in the simulator. I don't want to try it my phone until it works (again) on the simulator. The models folder contains the files created by the fuse command. I'm not sure that I changed anything in the last few days but it seems to be crashing in the loadmodel function with a lot of 'strange' output that I don't understand. My loadModel func `func loadModel() async throws -> Void { // return // one test for model not loaded alert // Avoid reloading if the model is already loaded let isLoaded = await MainActor.run { self.model != nil } if isLoaded { return } let modelFactory = LLMModel
Topic:
Machine Learning & AI
SubTopic:
Core ML
Tags:
Thanks for reporting the issue. Do you have a feedback report yet? If not, would you mind to file a feedback report and share your report ID here? Be sure to mention that the issue only happens on iOS 26.x. Thanks! Best, —— Ziqiao Chen Worldwide Developer Relations.
Topic:
App & System Services
SubTopic:
Health & Fitness
Tags:
One bit of follow-up on the bug fix side of this: FB19429215 (CallKit does not activate audio session with higher probability after upgrading to iOS 18.4.1) Having looked into the issue in more depth, there are technical issues that are likely to delay a fix coming from our side. The CallKit team is still committed to resolving this, but you should not expect the issue to be resolved in the short term. I'll also say that, based on my own analysis, I do NOT think this is in fact a new issue. That is, going back to the original report on this thread: We've noticed that this issue occurs more frequently after upgrading to iOS 18.4.1 The focus here was on the increased rate; however, it's very likely that this was simply a shift in the rate an existing bug occurred, NOT a new/different issue. Because of that, my recommendation is that all CallKit apps send a setConfiguration immediately before they report a new call. It's the best way I can see to prevent the problem from occurring and is alread
Topic:
App & System Services
SubTopic:
General
Tags:
If you're able to reproduce this issue, could you please file a but report, using the steps here: https://developer.apple.com/services-account/download?path=/iOS/iOS_Logs/CoreMedia_Logging_Instructions.pdf
Topic:
Media Technologies
SubTopic:
Streaming
Tags:
Hello, This is most likely due to the analytics self-correcting after terminations were previously under-reported due to a bug. Please see the Xcode section in the iOS 26 release notes: https://developer.apple.com/documentation/ios-ipados-release-notes/ios-ipados-26-release-notes Thanks!
Topic:
App & System Services
SubTopic:
General
Tags:
Thanks for the post. Do you get the same results with just the relevant code in a small test project? If so, please share a link to your test project. That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. If you could provide me with the sample, I can test it myself. However, if this is a bug, are you testing it with different versions of iOS? Let’s get to the bottom of the issue! Albert Pascual
Worldwide Developer Relations.
Topic:
UI Frameworks
SubTopic:
UIKit
I experienced this problem in XCode 26.0.1. My app has a single target configured with iOS and macOS destinations. For macOS, my app requires the sandbox entitlement for calendar data access. I fixed the error by: Removing the com.apple.application-identifier, com.apple.security.app-sandbox, and com.apple.security.personal-information.calendars entries from the app's AppName.entitlements file. Adding the sandbox and calendar entitlements back by adding the corresponding capabilities in the app target Signing & Capabilities settings. Toggling off and back on Automatically manage signing. I believe this worked because sandbox capability entitlements are only injected for macOS, while entitlement file entitlements were injected for all destinations. Hopefully this helps others with similar dual-destination setups.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags:
15.8 isn't available as a platform in xCode, but 15.5 is. Yes, the iPhone 7/15.5 simulator works, but that doesn't resolve the issue with connecting a physical iPhone 7 with iOS 15.8 repeatedly fails.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Up until some point relatively recently, I have been able to use Safari's web inspector to connect to the iOS simulator in order to debug our web application in development at http://localhost:8088. Now, the web inspector still OPENS, but it opens in a broken state. The context is available to select from Safari's Develop menu: Develop > iPhone 16 Pro (Simulator) > localhost - login. It appears under the Safari heading if I have navigated to the web app in the browser, or under the Expo heading if I am accessing it through the webview in our React Native wrapper app. When I select it, the web inspector window does appear. However, once it opens, the Elements pane is empty, the Console pane is empty, expressions entered into the console are not evaluated, there's no content in Sources, Network, Storage, etc. Important notes: This broken state happens at http://localhost:8088 as well as http://127.0.0.1:8088, and it seems that the insecure context is the issue. The web inspector DOES work for HTT
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
iOS
Web Inspector
Safari Developer Tools
Simulator
Is it not possible to change the background color of popovers in iOS 26? The backgroundColor property of UIPopoverPresentationController seems to just get ignored when Liquid Glass is enabled. Here’s a minimal repro: let presentedVC = UIViewController() presentedVC.modalPresentationStyle = .popover presentedVC.view.backgroundColor = .clear let popover = presentedVC.popoverPresentationController popover?.sourceItem = button popover?.backgroundColor = .red present(presentedVC, animated: true) If the UIDesignRequiresCompatibility key is set to YES, then the popover background color works as expected.
Topic:
UI Frameworks
SubTopic:
UIKit
This is still a problem in iOS 26.0.1. The behavior is significantly different than on iOS 18 and below. Using the new iOS 26 method - (BOOL)textField:(UITextField *)textField shouldChangeCharactersInRanges:(NSArray *)ranges replacementString:(NSString *)string API_AVAILABLE(ios(26.0), tvos(26.0), visionos(26.0), watchos(26.0)); Does NOT resolve the issue as it reports the same WRONG values.
Topic:
UI Frameworks
SubTopic:
UIKit