smb big sur

Hello, I think that all the EFB Admins dealing with iPad devices are struggling with the same issue. Apple will never tell you this information. I've tried to request it several times since 2015. Some years ago, Jeppesen said that as far as you have an accurate gps signal, you will have the location on FDProX. If the signal strength is not enough, then it will dissappear and will not be displayed. At the end, we have the AMM and we cannot use it because we cannot prove that the iPad's built-in GPS receiver has 12 channels. Apple should provide this information. They are fully aware that airlines are big users of this product. C'mon guys, the only thing you have to do is to write a statement in the specifications saying that! We don't want to know the manufacturer name of that antenna! Only how many channels there are!

Hello @Mike@ThatSoft, Yes, maximumImageDimension gives you some control over the input resolution. You can learn about more of the contour request properties in this WWDC video (timestamped link to the relevant portion): https://developer.apple.com/videos/play/wwdc2020/10673/?time=694 If you are unable to achieve the accuracy you desire, please file an enhancement request using Feedback Assistant. Other big critical problem/issue I have been struggling with, is over laying the contour. Can we discuss here, or you prefer a new question with that subject? Please open a new thread to address this. -- Greg

hello @Greg, I do see and experimented with: private var epsilon: Float = 0.001 I see this: let req = VNDetectContoursRequest() I see no resolution of the request. Can you please advise or a sample of this resolution setting? as you saw I really desire straight line detection and the corners. Sorry I'm not a real programmer at all, trying though. 60 yr old man :) thank you. feel free to email. thx. Greg, I tried this: (did i do it right?) private lazy var request: VNDetectContoursRequest = { let req = VNDetectContoursRequest() req.maximumImageDimension = 2000 return req }() see no real difference in the contour shape though. Note those pics were very cropped = zoomed in. Other big critical problem/issue I have been struggling with, is over laying the contour. Can we discuss here, or you prefer a new question with that subject? thx. I'd prefer email please :).

Especially big problem for Apple Vision Pro game development

It's not in App Store Connect. It's in right where you said: Account > Membership details The big blue iOS-style switch control

Bah, I’m still dealing with a big backlog, so I don’t have time to respond fully, but I can at least answer this. [quote='772363021, harshal_goyal, /thread/772363, /profile/harshal_goyal'] It seems like I can't create an NWInterface object because it doesn't have any initializers. [/quote] Indeed. You can use an Ethernet channel path monitor for this. For the details, see this thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='772362021, ManoharaRP, /thread/772362, /profile/ManoharaRP'] customers use our [instrumentation] product they don't have to add any code from there end to monitor this system. [/quote] There isn’t a good way to achieve this goal. I’ve seen folks attempt to do this in a variety of ways, and none of them end well. Specifically: Swizzling — DTS doesn’t support folks swizzling methods on Apple classes because it’s not a sustainable path. Eventually something comes along and breaks you. It sounds like you’ve hit that case with these Swift async methods. URLProtocol — Implementing a recursive URLProtocol is super hard to do correctly [1], and it comes with a bunch of feature limitations and compatibility risk. Moreover, if code within the process is using a custom URLSession, then it has to opt in anyway, and if you require an opt in then you might as well require a nice opt in (see below). As to what you should do right now, it kinda depends on the context. If you only need to help folks at development tim

Sorry, this Xcode16 just sucks. I've lost another half a days fiddling around with no luck, I just don't know what to do, and where. The project is big and in order to recreate the functionality, and the lldb bug, I have to build a whole new project, which will end up resembling the original one, minus some functionalities, so I dropped this route. The issue appears in one of the projects's internal static library. Now, I pause the execution at some breakpoint, run the po command and promptly get the Couldn't realize Swift AST type of self. Then I run swift-healthcheck, check the health log file, find the error below and conclude that the issue is in the static lib XXX. SwiftASTContextForExpressions(module: XXX, cu: AllParts.swift)::LoadOneModule() -- Missing Swift module or Clang module found for XXX, imported via SwiftDWARFImporterDelegate. Hint: Register Swift modules with the linker using -add_ast_path. Then I added -add_ast_path on the Other Linker Flags of the final executable, and now I get an

In my case, stat struct is provided by Endpoint Security message. Ahh, that makes sense then. One note here: Looks like, the best solution is to use DiskArbitration framework. I have to confess, I'm a bit of a fan boy™ when it comes to the DiskArb framework, having had the (dubious) pleasure of using it's original (and AWFUL) private API before the public API was introduced in 10.4. The API is looks a bit dated by modern standards, but it's very good at what it does. DiskArbitration can be used to find relationship between mount point (DAVolumePath) and physical device (DADiskGetBSDName). The main thing to be aware of (and take advantage of) is that the DiskArbitration can find out (and block) actions before they happen, meaning before the EndpointSecurity framework actually happens. For example, if you wanted to control/prevent mounts, the best way (IMHO) would be to: Use DARegisterDiskMountApprovalCallback() to block the DiskArb mount. Use the ES auth callback as the backstop if #1 is bypassed (for example,

Thanks for the big picture info. That was super helpful. Unfortunately I don’t see any way to do this. Regardless of the SecureToken stuff, the data protection keychain is becoming increasingly important and I’m not aware of any way to change its password. Lemme think about this some more and then get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi, Ziqiao, Thank you for your reply. 1.We just enabled iCloud sync in our app by following the guidance(https://www.hackingwithswift.com/quick-start/swiftdata/how-to-sync-swiftdata-with-icloud). 2.The app is similar with apple calendar. The app sync events data across the devices. 3.We have talked with some potential users. Their habits are to edit their agenda on iPad or Macbook because the screen is big enough. And then they will carry their iPhone to go outside and depend on the notifications from their iPhone to remind them. We can remind them to launch the app on their iPhone to sync the data from iCloud but sometimes they will forget it. That's why we want to design some codes to sync the events data from iCloud in the midnight without launching the app on iPhone.We have designed codes to reschedule the notifications in the midnight via backgroundtask. It works well. But we can't find the method to manually sync iCloud data via backgroundtask. Look forward to good solutions from Apple for it.

Quick Look does not seem to require an exclusive lock on a file for reading purposes. Given these observations, it seems likely that the exclusive lock behavior in the Quick Look Extension Preview, when accessing files over SMB, in unintentional. The term unintentional here is tricky. It's certainly true in the sense that extension is not specifically acquiring the lock on it's own, but there are enough API layers in the system that it's not unusual for a component to acquire behavior it didn't specifically intend/need. Case in point... If this is not an oversight, could you kindly explain why an exclusive lock is necessary in the Quick Look Extension Preview? This insight would help us better understand the situation and explore alternative solutions. The underlying cause here is that, across multiple implementation layers, QuickLookUIService ends up holding a CGImageSource reference and that reference is mmap'ing a file, which is in turn causing the lock. None of that implementation is actually new