Hi, looks like 15.4.x has broken softwareupdate --verbose --fetch-full-installer --full-installer-version for all versions (still works in 15.3.1) softwareupdate --verbose --list-full-installers Finding available software Software Update found the following full installers: * Title: macOS Sequoia, Version: 15.4.1, Size: 15244333KiB, Build: 24E263, Deferred: NO * Title: macOS Sequoia, Version: 15.4, Size: 15243957KiB, Build: 24E248, Deferred: NO * Title: macOS Sequoia, Version: 15.3.2, Size: 14890483KiB, Build: 24D81, Deferred: NO * Title: macOS Sequoia, Version: 15.3.1, Size: 14891477KiB, Build: 24D70, Deferred: NO * Title: macOS Sequoia, Version: 15.3, Size: 14889290KiB, Build: 24D60, Deferred: NO * Title: macOS Sequoia, Version: 15.2, Size: 14921025KiB, Build: 24C101, Deferred: NO * Title: macOS Sonoma, Version: 14.7.5, Size: 13337289KiB, Build: 23H527, Deferred: NO * Title: macOS Sonoma, Version: 14.7.4, Size: 13332546KiB, Build: 23H420, Deferred: NO * Title: macOS Sonoma, Version: 14.7.3, Size: 13334287Ki
Search results for
smb big sur
11,740 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. System data is the System, i.e. iOS plus necessary files such as logs and cache files. That number will stay pretty static. There's not really a lot you can do to reduce that. Try and offload some of your data to iCloud. Enable iCloud Photos and turn on Optimise iPhone Storage in Settings > Apps > Photos. Regardless, you have a 64GB iPhone, which isn't that big these days. It might've been fine five years ago, but not really now.
Topic:
Community
SubTopic:
Apple Developers
Tags:
Lots of people write apps that connect to their web servers. I think it's pretty unusual when an app doesn't do that. Internally, Apple is really old-school, big-iron corporate. I don't know specific details of specific products, but Apple's a big company, so there are lots of them. Generally speaking, if a 3rd party corporate networking/security app was a Big Deal 15 years ago, Apple probably still uses it today. Probably the two most important things to check are IPv6 and SSL. Make sure your app works in a purely IPv6 environment. Curiously, this policy is 9 years old now. Apple has a solid track record of announcing major changes 9 years before making a hard change. People who ignore those warnings because their app is working fine then get blindsided years later. Also, Apple can be very strict about SSL certificates for its own use. It really doesn't matter if your website works great in Chrome. It might not work from an Apple app or from an Apple internal network. People who ro
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
I’m not sure what’s happen in your exact case but I wanna step back and ask about the big picture. /usr/lib/libc++.1.dylib is macOS’s built-in copy of the C++ standard library. It’s meant to be referenced by an absolute path: % grep install-name /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/libc++.1.tbd install-name: '/usr/lib/libc++.1.dylib' Why are you trying to load it via an rpath-relative reference? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I am using react-native to build an ios app. After updating to macOS Big Sur - Version 11.6 a couple of days ago, my build started failing when using VS Code. I am getting this error- xcodebuild: error: Unable to find a destination matching the provided destination specifier: { id:5F135958-0789-4409-9C64-6D3939A54B03 } Available destinations for the MediLab scheme: { platform:macOS, arch:arm64, variant:Designed for [iPad,iPhone], id:7C6CDA97-38E3-591E-A991-8C4580349A5C } { platform:iOS Simulator, id:24E5BDF6-3EE5-4232-9E39-EBF4B48A9A2E, OS:15.0, name:iPad (9th generation) } { platform:iOS Simulator, id:FF4BFEEB-3DA8-4BB3-93E6-E3889C94F556, OS:15.0, name:iPad Air (4th generation) } { platform:iOS Simulator, id:624A99D1-6A8E-440A-AB96-3F7C0828C701, OS:15.0, name:iPad Pro (9.7-inch) } { platform:iOS Simulator, id:9C8A5850-F1D0-4B81-B7BE-2242BC3A1DB3, OS:15.0, name:iPad Pro (11-inch) (3rd generation) } { platform:iOS Simulator, id:2B47305A-7F97-44AE-8E53-30456CF02FBC, OS:15.0, name:iPad Pro (12.
All my apps work on both the iPhone and iPad, but due to the amount of changes - some structural - that are required to get an iPhone version to look and work properly on the iPad, I use two different views: @main struct MainApp: App { // ... var body: some Scene { WindowGroup { if(UIDevice.current.userInterfaceIdiom == .pad) { TabletView() } else { PhoneView() } } } } So, if the user is using an iPhone, the PhoneView() is the main entry point. For iPads, it's TabletView(). The reason I did this is because the iPad has much more space and allows me to do more things, so the TabletView has more things in it. Also, I'd rather not have one big, unmanageable View full of if ... else statements and ternary operators. It also means your spacers and padding values apply only to that device type. Where the two views have similar UI, those bits are extracted into their own little View structs and called within those two main entry points. When you separate out the two views you may find you're duplicating som
I’ve asked as well on the app support forum. As a dev, I often answer questions on my github that are config or usage related. And yes, these are my apps so it’s different but these questions are normally asked on dedicated support forums not on GH. Anyway, I’m not sure we need to make a big fuzz about that, let’s say then that my ask to devs in general here, related to my issue, is ”please don’t do the same in your apps and make sure that when you use certs, you don’t forbid use of IP-addresses directly”.
Topic:
Community
SubTopic:
Apple Developers
Tags:
I’m building an app similar to the Files app, where users navigate through folders using a NavigationStack with a bound NavigationPath. I need to display the current path — meaning a breadcrumb-like UI that shows the folder hierarchy the user has drilled down into. However, I’m running into a big limitation: We can’t access the current values inside NavigationPath. It doesn’t conform to Sequence, and there’s no documented way to extract the typed path elements to construct a path string like Documents / MyFolder / Subfolder. To work around this, I tried maintaining a separate [FileItem] array alongside NavigationPath, and that works well in iOS 17+ and iOS 18. But when I test on iOS 16, and navigate to another detail view in my NavigationSplitView, the app crashes. I searched around and found others hit this issue too — switching back to NavigationPath fixes the crash, but now I’m back to square one: I can’t figure out the current folder path from the stack. So my questions are: • Is there any suppor
Topic:
UI Frameworks
SubTopic:
SwiftUI
Regarding using notification to test the behavior, the idea is nice, but the slight problem is that it requires somebody closely watching the phone to quickly react to unpredictable background fetch event. Not really. The sysdiagnose capture covers a very long period of time (hour to days, depending on circumstances) so as long as the device hasn't been rebooted* it doesn't actually matter when you collect the log. While closer in time is theoretically better, for an issue like this there isn't really any practical difference between collecting a long immediately vs 30+ minutes later. *A lot of log data is purged at reboot, so that is a problem for this sort of thing. For most issue I actually recommend developer wait 5-10 min. after an issue before they trigger the log, as that makes sure that the log noise of the sysdiagnose isn't mixed in with any trailing log data. I'll also say that the upper time band here is pretty big. I don't like saying sure, collect it 4 days later because things do go wro
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
When I toggle a panel like navigationsidebar, I get a message in the console. I guess it's not a big issue, but is there a way to fix this message? because it appears in every project. Unable to open mach-O at path: /AppleInternal/Library/BuildRoots/d187757d-b9a3-11ef-83e5-aabfac210453/Library/Caches/com.apple.xbs/Binaries/RenderBox/install/TempContent/Root/System/Library/PrivateFrameworks/RenderBox.framework/Versions/A/Resources/default.metallib Error:2
Bienvenue sur le forum. Est ce que votre app utilise 'un service de connexion tiers,' tel que Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, ou WeChat Login Si non, il faut le signaler au reviewer, que vous n'êtes pas dans ce cas. Si oui, vous pouvez soit utiliser la connexion avec Apple login, à la place de celle utilisée, soit montrer que vous respectez les exigences 2 et 3. Attention, la traduction que vous avez des guidelines est imprecise. Les exigences sont: le service de connexion limite la collecte de données au nom et à l'adresse électronique de l'utilisateur ; le service de connexion permet aux utilisateurs de ne pas divulguer leur adresse électronique lors de la création de leur compte ; et le service de connexion ne collecte pas les interactions avec votre application à des fins publicitaires sans le consentement de l'utilisateur. Et enfin, mettez à jour les copies d'écran si besoin.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
any URLs should be passed to: func application(_ application: UIApplication, open url: URL, options: [UIApplication.OpenURLOptionsKey : Any] = [:] ) -> Bool I do not register the above application function to be called I'm a bit confused by what you're saying here. That's the function the system uses to pass URLs into your app. Why haven't you implemented it? instead this one is executed during app start with launchOptions always being nil: func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool This is the case regardless of if the App is started fresh or was already running in the background. Unfortunately, the system's implementation would be much more coherent if we completely removed launchOptions. The issue here is that application(_:didFinishLaunchingWithOptions:) is very, very old, dating from iOS 3. When it was original introduced the big innovation here was that the system could now pass informa
Topic:
App & System Services
SubTopic:
General
Tags:
Ideally, accessibility traits are consistent in an experience, but for apps as large as Settings or as big as your own it may be possible for inconsistencies to arise in applying the .button trait. In these cases, VoiceOver users are typically able to intuit the functionality of accessibility elements based on the context of the UI around it. There's not really a wrong answer here, but it may be omitted for brevity if it's clear otherwise. The .selected trait is certainly the more important of the two, and its usage should be applied anywhere a selection or choice is made and communicated through symbols like this checkmark.
Topic:
Accessibility & Inclusion
SubTopic:
General
Tags:
If you sell your app from your site it could be a problem with your receipts and verification. If this is happening to users that buy it from the App Store then it's likely that there's a BIG problem with 15.5. I understand your frustration with Mac development - crappy documentation in Swift only, very weak developer support, etc.
Topic:
App & System Services
SubTopic:
StoreKit
Tags:
Hi, In a Mac Catalyst app, I need to allow the user insert a passcode using a UITextField. The field is used to insert a one time passcode and I want to keep the content hidden. For this reason I set the isSecureTextEntry property to true. passcodeTextField.isSecureTextEntry = true By doing this, a button to allow the user to pick a password from the keychain is displayed: This option in my case should not appear because the password is a one time password that change every time. For that reason I set the textContentType to oneTimeCode. passcodeTextField.textContentType = .oneTimeCode This actually removes the password button, but introduce something weird. If the user type something and then delete everything, a big empty box appear under the field: I have no idea what this box is and why it appears. Does anyone know why it appears and how I can remove it? Thank you