Overview

I'm still learning how to code and would love to get recommendations on how to learn swift/swiftui for iOS/macOS app development. Any recommendations are welcome :)

Is it possible to use CoreData with the newly announces SwiftUI App Protocol for 100% SwiftUI apps. If I need to create an app with persistant storage, is there a way to achieve this with the new protocol? I like the idea of having my app fully compatable across all systems. Thanks.

Anyone encountering an issue with Big Sur and the terminal failing to present a shell some reasonably short time after boot? Initially works no problems, after a while new Terminal windows open fine but the shell never loads and you're left looking at a cursor.

When I select the main disk to install to, I get the error message: "The operation couldn't be completed. (BIErrorDomain error 3.)" Has anyone else experienced this? I wanted to try out the Big Sur beta, but didn't want to risk rendering my daily MBP unusable. Thanks!

Will live preview in SwiftUI and the Xcode 11 works on MacBook Pro Retina 2012 perfectly well? The MacBook Pro 2012 still great in 2019? I'm thinking about buying me one. I have a low budget and I need a MacBook Pro that will work for 3-5 years from now, being me a ”Pro” user.

I installed the profile for macOS Big Sur, but I got updated to Catalina beta 10.15.6 beta instead. Is it possible to install the Big Sur beta already?

My app ran without any crashes while using Xcode 11.1. After updating to XCode 11.2, my app experienced a crash:*** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named _UITextLayoutView because no class named _UITextLayoutView was found; the class needs to be defined in source code or linked in from a library (ensure the class is part of the correct target)'This crash seems to occur during a perpare for seque, before any of my views appear on the screen.Any idea on the cause or solution?Thanks.

Hello, we are in the process of releasing a new application in the App Store. I can archive and upload the build ok straight from xcode but then I get this issue: Dear Developer, We identified one or more issues with a recent delivery for your app, "McFamily" 3.2.1 (354). Please correct the following issues, then upload again.  ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).  Best regards, The App Store Team The thing is that we are not using UIWebView in our code. We are using some pods that are using it but those should be in their last version. Here is the pod file: Uncomment the next line to define a global platform for your project platform :ios, '11.0' Uncomment the next line to ignore all warnings from all pods inhibit_all_warnings! Comment the next line if you're not using Swift and don't want to use dynamic frameworks use_frameworks! def pods_base 	pod 'Kingfisher' 	pod 'RSKImageCropper' 	pod 'IHKeyboardAvoiding' 	pod 'RealmSwift' 	pod 'Liferay-iOS-SDK', '~> 7.2.2' 	pod 'LiferayScreens' 	pod 'ActiveLabel' 	pod 'SwiftLinkPreview' 	pod 'AppCenter' 	pod 'Firebase/Analytics' end target 'Ourlounge' do pods_base target 'OurloungeTests' do inherit! :search_paths end end post_install do |installer| 		installer.pods_project.targets.each do |target| 				target.build_configurations.each do |config| 				end 		end end The thing is that we publish this code base for other apps (that target other markets/countries) and have no issues when releasing updates for those other apps. Any help on how to proceed would be very much appreciated.

In Stacks, Grids, and Outlines in SwiftUI - https://developer.apple.com/videos/play/wwdc2020/10031, a recommendation is made to only use lazy stacks when you encounter performance bottlenecks. To quote the session, starting at 4:43: On the other hand, making the stacks within a given hero view lazy doesn't actually confer any benefits. The content is all visible at once, as soon as the view lands on screen. So everything has to be loaded at once, regardless of the container's default behavior. If you aren't sure which stack to use, use VStack or HStack. Adopt lazy stacks as a way to resolve performance bottlenecks that you find after profiling with Instruments. Are there negatives, performance or otherwise, to just always use lazy stacks? I'd like to understand why I shouldn't reach for LazyVStack and LazyHStack first. I understand from the example that using a lazy stack wouldn't confer any benefits, but would we incur any negatives?

It seems that AppDelegate and SceneDelegate are no longer needed in Swift UI in Xcode 12. I'm having trouble figuring out how to build an iCloud/Core Data enabled application with Swift UI. Is there a video/tutorial/guide on implementing Core Data or Cloudkit with the new Swift UI frameworks yet?

I am ready to upload my app from Xcode to App Store Connect. I am using Xcode 11.50 to archive my application. Yesterday, I used Xcode 12 Beta to upload the app, which worked fine at first, but noticed that App Store Connect is not accepting binaries from Xcode 12 Beta. I used Xcode 11.50 today and I keep getting this error while validating my app: Provisioning profile failed qualification: Profile doesn't include the com.apple.application-identifier and com.apple.developer.aps-enviornment entitlements. Provisioning profile failed qualification: Profile doesn't include the com.apple.application-identifier entitlement. What exactly do these errors mean? How can I fix them?