smb big sur

Guideline 1.1 - Safety - Objectionable Content We found that your app or metadata includes content that some users may find upsetting, offensive, or otherwise objectionable. Specifically, Lolicon references. The app was rejected from guideline 1.1 above. The meta app details are as follows: There are no sexy dress images in the app and the app rating is 12+ (but in app rating is 16+). The app icon will be an image of an anime girl with big eyes, wearing a uniform. The screenshot is an 18-year-old teenager wearing a gura shark costume. The app details refer to anime, manga. We would like to know which specific details reference lolicon so we can fix the problem.

I have a simple impossible task, to restore /var/root/Library/Application Support/multipassd/qemu/vault/instances/gcc-cobol/ubuntu-22.04-server-cloudimg-arm64.img as of 8:02 Saturday morning. Because /var/root is owned by, well, root, the usual techniques don't work. This is a VM image hosted by qemu via Canonical's Multipass. ISTM the strategy would be to first mount the NAS filesystem and then use tmutil(8) to list the backups and recover the file. But $ sudo mount -v -o rdonly -t smb //nasa.local/TimeMachine /usr/local/mnt/ mount: exec /Library/Filesystems/smb.fs/Contents/Resources/mount_smb for /usr/local/mnt: No such file or directory mount: /usr/local/mnt failed with 72 Must I defeat SIP to do this?

I've faced with some performance issues developing my readonly filesystem using fskit. For below screenshot: enumerateDirectory returns two hardcoded items, compiled with release config 3000 readdirsync are done from nodejs. macos 15.5 (24F74) I see that getdirentries syscall takes avg 121us. Because all other variables are minimised, it seems like it's fskit<->kernel overhead. This itself seems like a big number. I need to compare it with fuse though to be sure. But what fuse has and fskit seams don't (I checked every page in fskit docs) is kernel caching. Fuse supports: caching lookups (entry_timeout) negative lookups (entry_timeout) attributes (attr_timeout) readdir (via opendir cache_readdir and keep_cache) read and write ops but thats another topic. And afaik it works for both readonly and read-write file systems, because kernel can assume (if client is providing this) that cache is valid until kernel do write operations on corresponding inodes (create, setattr, write, etc). Questions are:

On iPhone, I would like to have a more button at the top right of the navigation bar, a search field in the bottom toolbar, and a plus button to the right of the search field. I've achieved this via the code below. But on iPad they should be in the navigation bar at the trailing edge from left to right: plus, more, search field. Just like the Shortcuts app, if there's not enough horizontal space, the search field should collapse into a button, and with even smaller space the search bar should become full-width under the navigation bar. Right now on iPad the search bar is full width under the navigation bar, more at top right, plus at bottom middle, no matter how big the window is. How can I achieve that? Any way to specify them for the system to more automatically do the right thing, or would I need to check specifically for iPhone vs iPad UIDevice to change the code? struct ContentView: View { @State private var searchText = var body: some View { NavigationStack { VStack { Text(Hello, world!) } .na

Code that reproduces the issue import SwiftUI @main struct KeyboardLayoutProblemApp: App { var body: some Scene { WindowGroup { iOSTabView() } } } struct iOSTabView: View { var body: some View { TabView { GameView() .frame(maxWidth: UIScreen.main.bounds.width, maxHeight: UIScreen.main.bounds.height) .tabItem { Label(Play, systemImage: gamecontroller.fill) } } } } struct GameView: View { var body: some View { VStack { Text(Play) Spacer() KeyboardView() } .padding() } } struct KeyboardView: View { let firstRowLetters = qwertyuiop.map { $0 } let secondRowLetters = asdfghjkl.map { $0 } let thirdRowLetters = zxcvbnm.map { $0 } var body: some View { VStack { HStack { ForEach(firstRowLetters, id: .self) { LetterKeyView(character: $0) } } HStack { ForEach(secondRowLetters, id: .self) { LetterKeyView(character: $0) } } HStack { ForEach(thirdRowLetters, id: .self) { LetterKeyView(character: $0) } } } .padding() } } struct LetterKeyView: View { let character: Character var width: CGFloat { height*0.8 } @ScaledMetric(rel