I’m building a Flutter plugin to access the new menubar API on iPadOS. Everything works fine with a single scene, but I’m running into issues when adding support for multiple scenes: Only odd-numbered windows (first, third, etc.) build their menus correctly. Even-numbered windows ignore the menus sent from Flutter and fall back to a default menubar. When switching between scenes, the last rendered menu always persists instead of updating to the current focus. So far, I’ve: Implemented the plugin as a singleton. Tried to persist menu state per scene, but without success. What would be the recommended approach here? Should I avoid a singleton and manage state entirely per UIScene instance? The project is open-source, and if anyone is willing to take a look, here are the relevant files: /ios/Classes/IpadOSMenubarPlugin.swift /example/ios/Runner/AppDelegate.swift Any guidance would be much appreciated.
Search results for
build disappears
49,445 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
See if ASSETCATALOG_COMPILER_LAUNCHIMAGE_NAME is still set in your build settings. It's also known as the Asset Catalog Launch Image Set Name. — Ed Ford, DTS Engineer
Topic:
Developer Tools & Services
SubTopic:
Xcode
I have three toolbar buttons with images from Assets.xcassets. Initially, I didn't use @1x, @2x, @3x sizes. I just put one size (72 x 72) for all of them. It was never a problem till a few days ago. The reviewer has reported numerous issues, which all seem to originate from miniaturized toolbar images. They have given me a screenshot from an iPad. Now, each of the three to the left has shrunken to 4 x 4, according to them. Some lines of code are the following. import SwiftUI struct ContentView: View { var body: some View { NavigationStack { ZStack { VStack { ... ... ... } .background(.brown) .navigationBarTitleDisplayMode(.inline) .navigationBarItems( leading: HStack(content: { Button { } label: { Image(ToolbarImage1) .resizable() .foregroundColor(.red) .aspectRatio(contentMode: .fit) .frame(width: 28) } Button { } label: { Image(ToolbarImage2) .resizable() .foregroundColor(.cyan) .aspectRatio(contentMode: .fit) .frame(width: 28) } Button { } label: { Image(ToolbarImage3) .resizable() .foregroundColor(.gray)
Topic:
UI Frameworks
SubTopic:
SwiftUI
Hi - thanks for the quick response. I'll try to answer as best as I can. Could you tell me more about these watchOS targets? My primary curiosity is how they are able to build successfully even during a normal build, if their dependencies do not support watchOS. I mentioned at the bottom of my original post that our app is [a mixture of] SPM packages and traditional target structure. This is mostly because SPM was introduced after our app was already published and created. We've slowly been migrating old features to SPM, and new features get added to SPM. The reason we love SPM is it introduces modularity for us, and enables greater code sharing. The way we decided to structure SPM within the context of all of our targets is one shared Package.swift file. This is because so many of our targets share the same code, it seemed easier at the time to keep all our various libraries within one SPM package (I hope that makes sense). So our one Package.swift declares all platforms like this: platform
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Thank you for your post. For help with the CarPlay , please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers. https://discussions.apple.com/welcome If you are using a beta version of iOS (please provide the version and build) with CarPlay , please file bug reports through Feedback Assistant. https://feedbackassistant.apple.com/ Hope this helps and you find the solution quickly. Albert Pascual
Worldwide Developer Relations.
Topic:
Community
SubTopic:
Apple Developers
Tags:
OK, so this is the part I haven't explained as well as I should. You don't actually need to build the kernel, as you already have a development build of the kernel in the KDK. That's what kernel.development.t6020 and kernel.kasan.t6020 installed by the KDK in /System/Library/Kernels are That was it - I built a kext collection using this pre-shipped kernels in the KDK and I was then able to boot this custom kext collection without any issues. I used the kernel.development variant for my test. Upon boot I even verified that it was indeed using the development variant of the kernel: $> sysctl kern.osbuildconfig kern.osbuildconfig: development Thank you very much Kevin for this very valuable help. I have several other things to read and try out (including hopefully building a trivially modified kernel version from xnu sources and booting it), but this initial step had blocked me for several months to even think of these additional experiments. For now, I will just write up these step
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Hello - For the situation you describe, the only possible mechanism for cancelling the subscription purchased in a TestFlight build using a production user account is to have your app call and present the App Store manage subscriptions sheet within the app itself, as documented here. Without that in-app capability, you must wait for the Sandbox subscription to cycle through its expected six (6) renewals before automatically cancelling, as documented here. If the Sandbox subscription purchased through your TestFlight app is not automatically cancelling after 6 renewals as expected, you can provide us with more details (the app name/id, a Sandbox transaction ID, etc.) and we can investigate further to see if the renewals and cancellations are not behaving as expected. Thank you.
Topic:
App Store Distribution & Marketing
SubTopic:
TestFlight
Tags:
Hey All, Curious if you guys are seeing the same thing for those who are using Interface Builder Files (Xib) i set the line seperator to none and on my app (built against ios 18 on the app store, but doesnt matter if i build it against ios 26, or ios 26.1) when running on iOS 26.1 the line seperator will show even when i set it to None. Funny enough if i just play around with the XIB file and set it to single line and maybe RED color the IB file will show it but when running it its the same old default dark greyish color. BUT if i set the line seperator in CODE either to be none or with single line + red it looks good when running on sim / device. So it seems to be an issue with XIB files not being respected in iOS 26.1 (only) i have submitted a feed back FB20466783, hope this helps any xcode devs / uikit devs. thank you !
Is there a better mechanism for this? We have been trying for 6 months to get an Enterprise Account - We have less than 100 employees, but we are contracting for a company that has a few thousand employees, who wants to MDM the app internally. The web pages to sign up keep kicking the application back, and every time we get an email from a person, it is obvious that no one is actually reading the application. The company we are contracting for logistical reasons CAN NOT USE TESTFLIGHT. They absolutely need it to be an enterprise build. Is there a better link than the one provided, because it’s very frustrating.
Topic:
Business & Education
SubTopic:
General
Tags:
After upgrading to macOS 26, I cannot install or update my app from either the App Store or TestFlight. Other apps update and install normally. Steps: Before upgrading, the app was installed via TestFlight and worked fine. After upgrading, I tried to update the app from the App Store: The update stalls at ~90% and never completes. Other apps update successfully. I launched the already-installed TestFlight version — it worked. After deleting the app, I tried reinstalling from TestFlight and got the error: “The app couldn’t be downloaded. Try again.” I tried rebooting, logging out/in of my Apple ID, and submitting a new TestFlight build — same issue. Environment: Originally built with Xcode 14 Also tried a new build with Xcode 16 App is compatible with macOS 26. Distribution outside the App Store (Developer ID signed and notarized build) runs fine
Hi, yesterday when I was trying to release the TestFlight build of my app the xcode said that it could not authenticate my apple ID. I then came to know that it actually wanted me to complete and aggrement which was Paid Apps Agreement. This agreeemnet is to be made if one has to sell their app on AppStore or make in-app-purchases. I want to ask if it was mandatory for me to sign that agreement? As the solution which I could come across suggested that xcode blocks the distribution if there is a pending agreement.
I filed a bug report (FB20465338) but I also want to note some more details here in case this is useful to someone: When navigating back/forward in a WebView or WKWebView, the page suddenly jumps up. The reason appears to be that WebKit automatically adds some padding to the top of the webpage to account for the unsafe nav bar area, but it then forgets to account for this padding when navigating back/forward. The effect is especially pronounced if you swipe back/forward. When swiping you see a static preview of the incoming page, but when you release the swipe, the page suddenly jumps up. As far as I can tell, this has always been an issue, but before iOS 26 it wasn't really a problem because the WebView would usually be flush against a solid nav bar. However, in iOS 26, this bug is problematic because Apple is asking us to flow the web content behind the nav bar; indeed, this is the default behavior of a WebView. There's effectively no good solution in iOS 26 because you basically have two choices: Adopt the
Topic:
Safari & Web
SubTopic:
General
Tags:
It will only work if you're building the app using Xcode 26. You also need to add the .icon file to your app. I was able to just drag and drop the file next to me assets bundle and it deployed it to my asset bundle in the next build.
[quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] the project is open source anyway. [/quote] Yeah, but if you send me a binary then I don’t have to mess around with build systems (-: [quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] Here is the zipped .app [/quote] Thank you! This layout is much what I’d expected: mach-o-images.txt Note I’m using the FindMachO.sh script from here. Or, as a hierarchy: hierarchy.txt That is, you have a vast array of code embedded within the Contents/Resources directory. It’s feasible to sign and distribute this. It doesn’t follow the rules in Placing content in a bundle, but this particular structure is tolerable, at least for the moment [1]. So, to sign this you need to generate a list of these code items, sort them in dependency order, and sign each one in that order. This is pretty much the process described in Creating distribution-signed code for macOS. Share and Enjoy — Q
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Since legacyScreenSaver is still the thing running screensavers we make, and it's still buggy, why won't they give us a new template for building screensavers that run in the new engine? And hopefully they don't require them to blend in with the desktop, because most of us don't want that. A wallpaper is a wallpaper, and a screensaver is a screensaver.