file uri scheme

Following up here. This is of course infernally annoying to test and debug: there is no response from Apple on this issue or documentation about VPP vs App Store differences. Furthermore we can only test our attempted changes by submitting a new build to the app store, waiting for approval, and then trying to deploy to our devices with VPP. What we can confirm is: – This is happening with other watch companion apps installed through VPP. HOWEVER a couple of watch companion apps I tested DID work. I would be happy to provide a list for comparison to Apple if it's helpful. – We tried adjusting a bunch of project settings related to optimization, dead code stripping, symbol stripping, etc. following a mix of online and AI-based guidance about potential objective-c metadata issues flagged from the crash logs. Our app is primarily based on Swift 5 but it does target some objective-c pods and frameworks which haven't changed in years. This didn't help. – Our app used the old WatchKit architecture with both an app t

Thank you, I asked, but unfortunately from Gurobi they confirmed their APIs do not support mmap. I am curious about your last suggestion regarding the boot parameter vm_compression_limit. The default is zero, but I cannot find any documentation about the other possible values, nor what is the corresponding behaviour. Is there any official documentation on it? Is there a command that supports modifying this parameter? On my mac it seems encrypted since on the kernels folder (I actually do not know which kernel is in use, there are multiple ones) all the files display a bunch of random symbols, so it is not as easy as to edit as the Linux kernel boot parameters. I assume there is a command to do it.

Answering my own question: I was able to do this by downloading LM Studio and installing a Devstral model from Mistral. Just start the server for that model and then set up a local model in Xcode. It's a local model, and works even with wifi turned off. I found the model didn't work nearly as well at understanding even medium-sized codebases and making changes. It was better suited for writing small snippets of code or maybe analyzing a single file.

Works great, Thanks! I updated the project file to a working state that others can use.

Sure, I can explain that a bit further. You added a Swift file to your project named LaunchViewController. That code will never run during the app launch process, because after all, your app is busy launching, not already running, so it doesn't yet have the ability to run that code. Thus, launch screens need to be static files — either just the contents of the Launch Storyboard, or just the contents of the Info.plist alternative which I recommend as the best choice these days. The system uses those static files to display your launch screen for you as the system gets your app ready to run your code. There is one other issue with your Xcode project configuration, in that it's not configured to support all orientations in the General tab. That's also set by default for brand new targets, and not one that should be changed. Older apps that don't have all orientations selected need to migrate to supporting all orientations, if your launch screen question here is part of making updates t

are there any other marker types which are capable of showing vertical position / altitude data on the map in 3D mode? There isn't API to do so for annotations, which is what I presume you mean by marker. For overlays, there also isn't API for you to create overlays with data for a third dimension, with one exception — if you ask MapKit for a route between locations using the MKDirections family of API, the route returned to you may display with elevation info, such as placing the route polyline on a bridge. The following screenshot is taken from a sample code project, though I adjusted the position of the map slightly to illustrate my point. At the top of the screen, you can see the route line going across a bridge, and then down through a tunnel, and finally passing underneath a highway overpass. As I said before, if you'd like us to consider more APIs including elevation, please file enhancement requests using Feedback Assistant and let us know how you'd use such APIs! — Ed Ford,  DTS Engineer

As an aside, macOS should probably automatically add an entry to the Print Panel when the app includes PDF as a document type in Xcode; it would save a lot of hassle and avoid having to go outside of the sandbox. However, I cannot wait for that. Hopefully, someone can help. So, I took a look at your sample and found two different problems: (1) As originally configured, your project had User Selected File to Read, which caused UIDocumentPickerViewController to always cancel. Changing that to Read/Write got it working. (2) You're checking for the correct folder by comparing the value the user selected to the value returned by: guard var libraryURL = FileManager.default.urls(for: .libraryDirectory, in: .userDomainMask).first else { The problem is that, in a sandboxed app, that API returns the app container path, NOT the user’s actual directories. So your check ends up comparing this: ~/Library/Containers//Data/Library/ To the user’s true selection: ~/Library/ ...inadvertently failing the correct path. A

Thank you for reporting here @Claude31 - always recommend filing a FB so we're all sure to see it and so we can track it as well.

Apologies for the delayed update. Yesterday, we completed the rollout of your workaround solution, and our metrics indicate its effectiveness. The issue count has decreased significantly during the implementation, dropping from 6000 per day to 1000 per day as of today. Fabulous, that's great to hear and thank you for sharing concrete numbers. I was fairly confident it would work, but it's good to get independent confirmation. We would like to express our gratitude for the workaround solution you provided. You're very welcome. Currently, we have implemented the workaround only for incoming calls, as these were the primary source of issues observed in our app. We plan to extend the implementation to outbound calls as well. I don't know this for certain, but my guess is that the difference between the incoming/outgoing rate is mostly due to usage patterns and the details of your existing implementation. In particular, these two factors: I suspect most calls originate from the foreground (the user opening your ap