smb big sur

Thanks for the answer! Could you elaborate more on shipping the helper daemon as an installer package? Is it shipping it with the main app's bundle somehow? How would it look technically? Sandbox is a great concept, but in many cases, it just limits basic functionality, which otherwise is available in many apps shipped outside of the Mac App Store. Those apps have a big competitive advantage, better developer experience, and no app review. Over time I become only more frustrated with the restrictions Apple imposes.

Grant Bennet-Alder User level:Level 10 131,983 points Feb 19, 2024 7:42 AM in response to johnkl Some additional searching around this error yielded additional insights. It appears the default confguration of the WD Server does not support everything Apple devices need to be successful. you may have to modify the configuration of the NAS server software. According to https://krypted.com/lists/comprehensive-list-of-mac-os-x-error-codes/ , 100093 is kPOSIXErrorENOATTR (Attribute not found). It looks like there's special support for Apple SMB clients in Samba. from: https://www.reddit.com/r/ios/comments/q02ss3/files_app_osstatus_error_100093/?rdt=55815 https://discussions.apple.com/thread/255480414?sortBy=oldest_first

I have found that the release notes of Sequoia actually state that any app group format should work, when the app is distributed through the app store or includes it in the provisioning profile (highlights by me): Specifically, the app must use FileManager to get the app group container path and meet one of the following requirements: the app is deployed through Mac App Store; the app group identifier is prefixed with the app’s Team ID; or the app group identifier is authorised by a provisioning profile embedded within the app. Also, I have discovered in the release notes of macOS 15.1 beta 4 sate that it fixes the following issue: Fixed: Users might be incorrectly prompted when an app that is distributed through TestFlight attempts to access an application group container. (131606564) (FB14288230) I understand, that the security alert should actually not be shown and is currently only shown for XCode and TestFlight builds. I can verify, that no such alert is shown when I run the App Store version of my app.

[quote='803922022, StefanoHeartP, /thread/763754?answerId=803922022#803922022, /profile/StefanoHeartP'] I'm not sure about dates. [/quote] OK. But my point is that the difference of a day isn’t a big deal. If you’re renewing a certificate, you wouldn’t do that on the last day that the certificate is valid, you’d do it well in advance. So the difference between 9 Oct and 10 Oct isn’t something you really care about. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

FB15139430 It seems it's not just macOS 10.15, it's also Big Sur. In fact, it's not about the macOS version - it's crashing on Intel Macs. We've just received a crash report from Big Sur with the same issue: Code Type: X86-64 (Native) Parent Process: ??? [1] User ID: 501 Date/Time: 2024-09-18 12:48:44.261 +0700 OS Version: macOS 11.7.10 (20G1427) Report Version: 12 Anonymous UUID: FCCC50AB-71DC-4908-AD86-EE79F2A7EDFF Sleep/Wake UUID: FA9BC3F4-1F95-41BC-9153-EA509922FCFB Time Awake Since Boot: 44000 seconds Time Since Wake: 18000 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD, [0x1] Library missing Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: dyld: Using shared cache: 3694F5E4-3E85-3CD5-A2B0-534E2DFC1355 Library not loaded: /System/Library/Frameworks/QuickLookU

I’m still experiencing the same issue with Spotlight on my Mac Mini M2 with macOS Sequoia 15.0. It only returns search results for applications, not files, settings, or emails. Setup Mac Mini M2 Mobile account authenticated against SAMBA-AD-DC (Active Directory-like) Workaround I found a temporary workaround that seems to help: I created a local account (no admin privileges required). Then, I attempted to SSH to localhost using that local account. The SSH connection was rejected for reasons I haven’t yet investigated, but interestingly, after this, Spotlight started functioning normally again. It seems that a local account needs to log in at least once after every reboot for Spotlight to work correctly. This workaround isn’t ideal, but it might help if you are facing the same issue.

[quote='763751021, HanochM, /thread/763751, /profile/HanochM'] is there any update about the ability of getting the Network details such as RSSI , PHY in iOS 18? [/quote] No. I’m in the process of updating TN3111 for iOS 18, but the only big change on that front is the introduction of AccessorySetupKit (which is super cool though). ps If you haven’t already seen it, have a read of iOS Network Signal Strength. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

First off, I need do comment on a pet concern of mine: let fileAttributes = try FileManager.default.attributesOfItem(atPath: url.path) String based paths are a long standing problem in our entire API. Their are valid file system configuration that system should be able to work with, but that fail catastrophically because of how string based paths manipulate unicode normalization. I don't know if we will ever be able to fully resolve those issue, but doing so is going to require using NSURL for ALL file references. In terms of selfish reasons, you should be aware that the path and URL variants of the same API can have WILDLY different performance characteristics. For example, enumeratorAtPath is ~3x SLOWER than enumeratorAtURL, due to a combination of different API semantics (it's design forces a additional stat call for attributes you may never look at) and because it's not the primary API. Moving on to the issue itself: When users share a file with my app I am having trouble 5-10% of the time obtaining the f

Not sure if this solution works for everyone, but I found in my case that xcodebuild was reaching out because I had an account defined in Xcode > Settings > Accounts. Once I deleted my account from Xcode, xcodebuild sped up to the same speed as when I unplug my network cable. But the caveat is that my team's build system doesn't have the Automatically manage signing checkbox checked for our projects and is setup to separately manage our certs / provisioning profiles / team identifiers, so removing my account from Xcode isn't a big deal.

Big thanks @DTS Engineer. after 2 days of additional research, i've mark next points. need to sign bundle, and execution file to, one without entitlements, second with. First of all we signing Sysex , than main app. Commands looks like next: codesign -f --timestamp --options runtime --sign ${certificate_name} ${app_bundle.app} codesign -f --timestamp --options runtime --entitlements ${app_entitlements} --sign ${certificate_name} ${app_bundle.app}/Contents/MacOS/${app_name} Also i have to removed keychain access group compatibility, cause when i've trying to run. It can't be run cause saying that signing is wrong. But after removing it solved. In console, i've see the error. Entitlement com.apple.security.application-groups=( group.com.ex.company.appname ) is ignored because of invalid application signature or incorrect provisioning profile its super strange message, and possibly can affect something, but not sure. (Maybe there is must be prefixed with TeamId?) Could you please add comments for it? an

I'll be honest, this has me completely baffled. I have a few comment below, but here's what I'd like you to do: File a code support incident using the button at the bottom of this page. In that request, make sure you mention that I asked you to and include the link to that forum post. I want to get my hands on the actual files involved, so lets move this off the forums. I'd like to get my hands on all the data you've got and it may be to big to send as an attachment. If you can include a link I can download it all from, that would be helpful. If you're in contact with any of your users how are able to reproduce the issue, then what would be most helpful is for them to reproduce the issue (install them app, wait a moment, launch the app and watch it fail), then collect a sysdiagnose. A few notes on that: It's helpful to reboot the machine before testing and to avoid running anything that isn't part of the test. It doesn't matter if the log is collected a few minutes after the issue and, in fact, it ma

It's okay to run multiple ARKitSession's in a single app. Further, they will share the coordinate system of the running app. There is a bit of a cost for additional running DataProvider's, as they all have their own connections to receive data. But in most cases that shouldn't have a big impact on your app's performance.

I would really like an answer to this last question. If the idea is that our API server gets a refresh + access token, then passes the access token to the (user side) app client, which they then use as a bearer token to access resources on the API server (at least, I think this is what is implied by the rather not-too-great docs), then you want to be able to either verify the access token on every request to your API server, which includes checking its validity. If it's nearing expiry, you should use the refresh token to request a new access token. If you have access token validity at 1h, and throttling on token endpoint calls at 1 per day, that's a big fail. Anyhow, I'd really like to know apple's preferred way of doing this, without us either (1) rolling our own token issuing on our servers; or (2) relying on a service such as Cognito in the middle to handle token issuing.

[quote='803106022, Gandolf, /thread/763453?answerId=803106022#803106022, /profile/Gandolf'] I'm working on a screen sharing app [/quote] Thanks for that. This is a well-trodden path, one that I’ve helped numerous developers navigate. Two things up front: I presume you’ve seen the PreLoginAgents sample code. Its read me document mentions a bug (r. 5636091). If you haven’t already done so, please open a DTS code-level support request so I can discuss that bug with your privately. IMPORTANT The submission form asks you whether someone asked you to contact DTS. Make sure to answer “Yes” and point to this DevForums thread. macOS 15 (currently a release candidate) has changes such that screen sharing apps need an additional capability. See Persistent Content Capture. [quote='803106022, Gandolf, /thread/763453?answerId=803106022#803106022, /profile/Gandolf'] does it get its own GUI Session ID? [/quote] You have to define what you mean by “GUI Session ID”. What API are you using that works in terms of session IDs. [q