smb big sur

Hi, so here's my situation: I am currently building an app of which I want to have an Apple Watch standalone version / companion (idk yet, also doesn't matter). For it to be compatible with basically every Watch except for the original (Series 0) I want support for down to watchOS 6, as many models ended there. I also don't need the newest features for basic functionality and I can still add more for newer versions while keeping the basic functionality for watchOS 6, so that is not a concern, I'd rather have the compatibility. However, watchOS 6 is the last version to require the Storyboard architecture with an app bundle and extension target. I did some research and found out that you can create that and set the development target to 6.0 while also having a SwiftUI target with a development target of 7.0. That would have the benefit of being able to use SwiftUI for modern features to give a nice experience while building a basic but functional version for 6.0 in Storyboard architecture. And it would figure o

Is anyone else getting new warning about menu items with submenus when running on Tahoe? I'm getting big performance problems using my menu as well as seeing these messages and I'm wondering if there's a connection. My app is faceless with a NSStatusItem with an NSMenu. Specifically it's my own subclass of NSMenu where I have a lot of code to manage the menu's dynamic behavior. This code is directly in the menu subclass instead of in a controller because the app I forked had it this way, a little wacky but I don't see it being a problem. A nib defines the contents of the menu, and it's instantiated manually with code like: var nibObjects: NSArray? = [] guard let nib = NSNib(nibNamed: AppMenu, bundle: nil) else { ... } guard nib.instantiate(withOwner: owner, topLevelObjects: &nibObjects) else { ... } guard let menu = nibObjects?.compactMap({ $0 as? Self }).first else { ... } Within that nib.instantiate call I see a warning logged that seems new to Tahoe, before the menu's awakeFromNib is called, t

Hello Everyone! I recently got a termination notice. I've already sent an appeal 20 days back, I did get the response saying they'll not change the decision which is really a big problem! I've been developing apps and have been supporting my family for quite some time. But because of a small-mistake, I lost my entire account (Although I've made changes and re-submitted, but the app which got the removal isn't going for review) Anyone can you please help? I never got any kind of warning from Apple and I understood that since I'm using a commercial API, I could use it in my title, but it triggered removal of my entire account. Here's the notice I got: Upon further review of the activity associated with your Apple Developer Program membership, it's been determined that your membership has been used for dishonest or fraudulent activity, in violation of the Apple Developer Program License Agreement and the Developer Code of Conduct (App Review Guideline 5.6). Given the severity of the identified issues, y

Once, the App Store empowered indie creators - small teams could launch great apps and find users easily. But in 2025, that era feels long gone, with algorithms, big players, and pay-to-win discoverability reshaping everything. Is there still a real chance for indie iOS developers today, or has Apple’s evolving ecosystem made independent success nearly impossible?

Create a static widget kit based widget for watchKit. Use swiftUI and an image. IE on 42mm you can import a 141x141 image at 2x. Import a 141x141 image in the widget and load it in swiftUI. In watchOS 11.x simulator the image will allow up to the size for X Large circles, and on os26, it will not load and complain the image is too large and report the area for the smaller circle, IE 89x89 @ 2x for 41mm Also submitted a feedback ticket FB20506200 This is a big issue b/c the size difference for X large circles v the smaller circles is really large. To get existing images to load I am having to resize them down 75-80% on OS26 in the X Large complication.

Hey everyone, I’ve noticed a big drop in my keyword rankings lately, and it seems linked to Apple’s recent ASO update that’s been trending on Twitter. Has anyone figured out what changed? It looks like app titles may now have less impact on rankings.

I have an iPad app with a classic sidebar. It's been working fine for years. Now with iPadOS 26 the sidebar sometime gets this fake transparency that makes it really hard to quickly grok. A part of Liquid Glass seems to be to sometimes (but not always) take whatever is in the secondary area (the main big content), blur it, mirror it and then use as the background for the sidebar. This is silly and does not work at all for an app like mine. It maybe looks decent if your background is a photo or similar, but not for an app that manages data. Not all views cause the sidebar to get this ugly unreadable background. In most of the cases the sidebar keeps its normal opaque background that it has always had. See this example for how it looks when it's really bad: This is how it should look. Notice that the content of the main view is pretty similar to the case where it gets the ugly background. The difference is the segmented thing at the top, ie. a different root view. Is there some good way for me to force