smb big sur

Alright, thanks! So I can’t move the Developer folder to an external SSD, right? To be honest, I've never tried doing anything like replacing the Developer folder with a symbolic link. In many cases, when there is something special about a folder, like special system protections, or it's being managed by a system daemon, you can't do that. But I don't know about the Developer folder. I had forgotten about the Locations setting. In my case, I could use that to move 17 GB on this machine. But the iOSRuntime is the big problem. At one point during the summer, this folder went crazy and completely filled my SSD with 300 GB of data. I had to hack it via SIP. A later build fixed that. This is just one of those problems that can be easily solved with money. A problem solvable with money isn't a real problem.

So this is the actual purpose of my app. But the access you are attempting to obtain would also give you unrestricted ability to read and modify bookmarks, browsing history, image caches, cookies, extension data, etc. That's very valuable information. And having that access would, in turn, make your app valuable. Even if you only checked for invalid links, you could sell your app, and its Full Disk Access, to some other, less-scrupulous company. do you still think this would be considered too risky or difficult to get approved? I'm sorry, but wasn't clear enough before. I don't work for Apple or for App Review. My opinions have no part in their review. I've already described Full Disk Access as a suspicious Big Red Flag and a horrible user experience. You asked for advice and experiences. I've provided both.

Full Disk Access is a user privacy setting. App Review can't give that to your app. Only your users can give your app Full Disk Access. Furthermore, Mac App Store apps are sandboxed. That's a separate layer of privacy protection. You have to ask the user to give your app access to a given folder (or root) and then the user would also have to give your app Full Disk Access. Technically, it is possible. A few years ago, I had an app that did all that in the Mac App Store. I don't remember the relevant App Review communications at the time, but I remember thinking that I was not allowed to ask for Full Disk Access or direct users to it. I had an option in app settings to provide it, but users had to find that on their own. I could give them instructions on the web site, but not inside the app itself. I can't say what App Review's current policies are. All I can do is relate my own experience. I would also suggest that you're entering into a dangerous area. What kind of data from third party web browsers are you

It has been more than a year now, and this still has not been resolved. My US LLC Apple Developer account is still stuck in limbo. Apple has not given me any response. They just don't care. During this time, I used a friend's developer account to sign my Mac app and distribute it on my own website. I was not trying to ship on the App Store anyway. Later, I enrolled as an individual and published an iOS app under that account. After that, my personal account could also sign and notarize my Mac app normally. But I still want my US LLC developer account back. I do not want to publish Mac or iOS apps under my personal developer account. These are commercial products, and I think it is better to ship them under a company entity. My original hope was that after the membership expired for a year, I could re-enroll and the account would return to a normal state. But that did not happen. Even though the membership has expired, Apple still will not let me enroll again. The page still says: Sorry, you can't enroll at th

Thanks a lot for responding. Thanks for the post, it’s hard not seeing the code and how you're setting constrains in code. Would you be so kind to provide your code where you setting the constraints so developers here can see it? [..] it is generally not a good idea (and will lead to crashes) to directly modify the frame or bounds of a view that is managed by Auto Layout in my opinion. Initially I did not involve Autolayout at all explicitly. What I had was a small container view controller with something like this (no explicit constraints): @implementation SmallInfoWrapperViewController -(void)viewDidLayout { [super viewDidLayout]; NSRect bounds = self.view.bounds; CGFloat lineHeight = 1.0; self.separator.frame = NSMakeRect(0.0,bounds.size.height-lineHeight,bounds.size.width,lineHeight); BOOL separatorVisible = !self.separator.isHidden; CGFloat wrappedViewHeight = bounds.size.height; if (separatorVisible) { wrappedViewHeight -= lineHeight; } self.wrappedView.frame = NSMakeRect(0.0,0.0,bounds.size.width, wrap

@bryan1anderson I don't think you can. If your dataset is large enough (like my example), you'll always get hangs. It looks to me like Query/Predicate is the issue here, they seem to run everything on the Swift side rather than being transformed into SQL queries that run directly on the underlying SQL database. On the example that I posted and that @DTS Engineer confirmed, the SQL part runs really fast, but the overall fetch is slow. I'd love for Apple to give this more attention, because if having a big dataset is a deal breaker, nobody -unless you're 100% sure your data will always be very small- should use Swift Data. Imagine if you build a very complex app using Swift Data and your dataset keeps growing, you'll hit a point where you need to re-write the model layer using Core Data, kinda insane if you ask me.

I'm dealing with encyclopedic articles, and quite often the model will request the Introduction section, even though no such string appears in the sections array. Sometimes it also hallucinates sections that it thinks ought to exist based on the prompt. While I was debugging this, I constructed a simpler toy example. It might be easier if we talk about that instead. Here's a playground I made to demonstrate the issue: import Playgrounds import FoundationModels #Playground { struct CityInfo: Tool { let validCities: [String] let name: String = getCityInfo let description: String = Get information about a city. var parameters: GenerationSchema { GenerationSchema( type: GeneratedContent.self, properties: [ GenerationSchema.Property( name: city, description: The city to get information about., type: String.self, guides: [.anyOf(validCities)] ) ] ) } func call(arguments: GeneratedContent) throws -> String { print(arguments.generatedContent) let cityName = try arguments.value(String.self, forProperty: city) let c

In general, I recommend that you escalate questions like this via the support channel for the third-party tools you’re using. In this case, however, I have some suggestion before you do that, all related to this: [quote='812438021, lucksp, /thread/812438, /profile/lucksp'] For this new project, however, I am not the owner. [/quote] First, check that this team is an Organization team. If it’s an Individual team, you’ll like run into problems per the note at the top of the Permissions in App Store Connect section of Developer > Program Roles. Assuming this is an Organization (or Enterprise) team, the next step is to ensure that your operation is compatible with your program role. See the big table at the top of Developer > Support > Articles > Program Roles. Finally, try to do an equivalent operation on the Developer website itself. If that fails, you can seek help via Apple > Developer > Contact Us. But if that works, this is something for your tools vendor to investigate. Share and

[quote='871830022, matthewruzzi, /thread/812360?answerId=871830022#871830022, /profile/matthewruzzi'] Are there any other places that I should post this to get more discussion? [/quote] I can think of least two: JavaScriptCore is open source as part of WebKit project, and they have their own community discussions. Likewise, Swift is open source and has Swift Forums. The best approach kinda depends on who you want to do the work. If you just want Apple to fix something, Feedback Assistant is your best option [1]. But if you want to engage with other developers then things get more nuanced, especially with regards to where the changes land, which is a big factor in what work gets done and who does it. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] For more about that process, see Bug Reporting: How and Why?. And if you do file this in Feedback Assistant, please post your bug number, just for the record.