smb big sur

Doesn't audio background guarantee that app is not suspended by system? Strictly speaking, no. The audio background category allows your app to remain awake while your audio session is active, which isn't quite the same as guaranteeing it will not be suspended. Next a quick note here: The problem is that my app sometimes gets suspended few hours after getting into background. I cannot find the exact reason for it. How are you finding out about this problem? Is it: You're able to directly reproduce it. Users are complaining about it. You have log data showing that it's occurring. The last kind of data (#3) is the case you need to be very careful about. I've seen many cases where a developer identified a problem based on log data then spent a great deal of time and worry investigating it, only to eventually discover that... nothing was actually going wrong. Logging only shows your apps side of an issue, which means you can't really tell the difference between cases like the system stopped playing me and the use

I second _nox, am testing against IOS 18, but this seems to have broken for my app a few weeks ago. I had hoped the big upgrade would have fixed this. I have verified that the token I have in my db matches what my app gets in didRegisterForRemoteNotificationsWithDeviceToken at startup, and whether I build my app in production or development I get the same token, which seems peculiar. If I build and push from apple web site console to production I see The specified device token is invalid. Verify that the request contains a valid token and that the token matches the environment. with APS Env set to production, but if I build to development and send to development, from their web console thingy, I get discarded as device was offline from my server sending the production works always giving me sendToToken com.eatthepath.pushy.apns.util.concurrent.PushNotificationFuture@5770671b[Not completed, 1 dependents] but sending with the development cert I get io.netty.channel.ConnectTimeoutException: connection t

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