Post not yet marked as solved
This question was originally posted to StackOverflow, but I found it more suitable to be placed here.
Was working on migrating one of my app from AppDelegate lifecycle to SwiftUI lifecycle according to this question.
After following all the steps, The simulator simply shows a blank screen (the app does not launch at all):
There is no log in the console. However, if the app is removed from the simulator (or device) and reinstalled, it will launch the new SwiftUI lifecycle correctly. So there seems to be some problem with scene caching that causes iOS to be confused after the migration.
Am I missing something during the migration?
Post not yet marked as solved
In AppKit, you can use the NSTrackingSeparatorToolbarItem item to create a toolbar item that automatically attaches to the separator in a split view.
However, I didn't find an equivalent in SwiftUI yet. I tried to add a .toolbar modifier to each individual view, however, that didn't seems to achieve the effect. All the item are just on the right side of the window.
Any native SwiftUI way to achieve this, or do I have to go back to using AppKit windows?
Post not yet marked as solved
Hello, when I try to install macOS 11 beta 3 from beta 2, I downloaded the incremental update as shown in the release log (press the more info and press download). After it downloads, it install for roughly 10 minutes, and then it takes me straight back to the login screen (of course the update did not install).
When I download the full update, it gets stuck on Downloading 12.88GB of 12.88GB for almost an hour with no response.
Anyone else have the same issue?
Thanks!
Post not yet marked as solved
My app is crashing with a bizzare error on beta5. Here are a little history of this:beta1, 2, 3 - working perfectlybeta4 - unable to compilebeta5 - can build, but crash on launch, details below.My code is unchanged since beta3 - so definitely not something I've modified since then.Here is the error:2019-08-06 22:47:11.181717+0800 My App Mobile[19708:876341] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '(null)'
*** First throw call stack:
Call stacks here. I don't think this is neccessaryI've placed some breakpoint, it crashed after running:application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?)and:application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions)
Post not yet marked as solved
After updating to the latest iOS 13 beta I want to add a card to Wallet. However, it is telling me to change my passcode to something more secure (that does not have repeats or consecutive digits). I don't really have one of these password that I can remember well to change into. I either have to change it to a very unfamiliar one, or use one of my really long passwords that i normally use for desktop things, which can get really annoying on a phoneAnyone else have this problem?I have 4 cards in my wallet and this new card will be my 5th one.
Post not yet marked as solved
Just updated to iOS 13 beta 2. I have an IPSec VPN server running on Ubuntu. It is hosted on a web service platform. After updating, the VPN can still connect, but it does not make anymore connections (I can't load anything). This is confirmed to be related to this beta as I updated 1 iPhone, 1 iPad, and 1 Mac, and the same VPN configuration that were working before all stopped working. Tested the exact same configuration 1 minute ago with my iOS 12 stable device, it does connect and will load webpages, so definitely not my server's problem. Anyone else have this problem? Let me know any information about my VPN server is wanted. Thanks
I am using the exact same code from the Apple WWDC19 Session 235:This code is in the scene(_:, willConnectTo:, options:) method:#if targetEnvironment(UIKitForMac)
if let windowScene = scene as? UIWindowScene {
if let titleBar = windowScene.titlebar {
let toolbar = NSToolbar()
// Setup toolbar
}
}
#endifHowever, on the 3rd line there, it just tells me that the windowScene property does not have the titlebar property within it.Am I missing something?
I have a UISplitViewController where the master is a regular UIViewController (not a UITableViewController). I setted the primaryBackgroundStyle to .sidebar on the split view controller subclass, but it doesn't seems to affect the view controller's background at all. I do have a custom background color on the UIViewController set for the iOS version, but setting it to clear doesn't help, just makes the background looks really wierd.Any idea on whether this is not supported at all or it's just a bug in the beta?All the demos I'ves seen are with a table view on the left, not a regular view controller.
Tom1234.