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.

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?

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!

Unable to Submit for Review The items below are required to start the review process: An error has occurred. Try again later.

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.

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?

I have noticed a strange problem today. I have uploaded a build of my app to TestFlight for internal testing using Xcode 12 beta 3. The app has widgets and if I run the app locally from Xcode widgets are working on device. However, when I install a beta from TestFlight the widgets are not suggested by iOS and I can see in the logs that the widgets are actually crashing (something is going on with WidgetKit in the crash logs). This has started only with beta 3, I have previously used TestFlight with widgets in beta 1 and beta 2. Does anyone else have this problem? My feedback number is FB8122742.

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'm trying to do a simple application in SwiftUI taking advantage of SwiftUI 2.0's new multiplatform project template, and I wish to add the option to collapse the sidebar as many other apps do. I've got an extremely simple sidebar I did following the Fruta example project, and I tried adding a boolean state variable that controls whether the sidebar should show or not, but that doesn't work because when the sidebar is hidden, the main view is turned translucent. On iPadOS, a button appears on top of the sidebar that allows to collapse it. How would I do this in macOS? Is there a way to natively achieve this in SwiftUI, or I'll need to resort to a UIKit workaround?  Please note I'm using macOS Big Sur, Xcode 12, and SwiftUI 2.0 Thanks in advance.

I have a macOS app which uses AVFoundation that was building fine with XCode 12 Beta 2. In Beta 3, I get: Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk/usr/lib/swift/AVFoundation.swiftmodule/x86_64-apple-macos.swiftinterface:72:11: 'AVAudioSession' is unavailable in macOS /AVFoundation.AVAudioSession:2:12: 'AVAudioSession' has been explicitly marked unavailable here Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk/usr/lib/swift/AVFoundation.swiftmodule/x86_64-apple-macos.swiftinterface:129:11: 'AVAudioSession' is unavailable in macOS /AVFoundation.AVAudioSession:2:12: 'AVAudioSession' has been explicitly marked unavailable here Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk/usr/lib/swift/AVFoundation.swiftmodule/x86_64-apple-macos.swiftinterface:1:1: Failed to build module 'AVFoundation' from its module interface; the compiler that produced it, 'Apple Swift version 5.3 (swiftlang-1200.2.22.2 clang-1200.0.25.1)', may have used features that aren't supported by this compiler, 'Apple Swift version 5.3 (swiftlang-1200.0.22.4 clang-1200.0.25.1)' I didn't see anything about this in the known issues of Beta 3. Does anyone have any thoughts on what's going on?