Friendly Hint: paste your code (using "Paste and Match Style") into a code-block, then it will look nice, and people will be able to read it.

Try class SignInController: ObservableObject {     @Published var signedIn: Bool = false } (By the way, in MainView, I think your ZStack should be a VStack)

It could be a bad QR code. Share it here, then we can see if it works.

If you are serious about app development, you probably want to use Xcode rather than Playgrounds. ("Playgrounds"... the clue is in the name!)

Xcode 13.2.1 is now available on the App Store, fixing the Swift Package issue.

The App Store Xcode 13.2 has a serious issue with Swift Packages. Xcode 13.2.1 is now available, which should fix the issue.

Not WYSIWYG as such, but you could look at using Markdown in Text views.

Reported as Spam

If the app has been backgrounded for about an hour, then it is reactivated... It might still be in memory, so it will "resume" operation It might have been removed from memory, so it will "relaunch" The first step in your diagnosis is to distinguish between those two cases. Other thoughts: Are you saving state when the app is backgrounded? Are you restoring state on foregrounding? Is what you call the "SplashScreen" actually the Launch Screen, that shows when the app is Launched, or is it something else?

You can choose the location of the Derived Data folder. Xcode > Preferences > Locations > Derived Data The "Default" location is in the user's Library folder (which is a hidden folder, of course).

Screenshot?

I agree, this doesn't look as expected. But I can still choose to run an iOS app on a range of Simulators. I see: Xcode 13.2.1 (13C100) Interestingly, the same issue was reported here on the forum, for Xcode 9.3.1. That led to a bug report being submitted, and the issue eventually went away. https://developer.apple.com/forums/thread/102783

When the user taps "update" they will get the latest version from the App Store. They could (in theory) be updating to the latest version from any previous version. You need to handle all such cases. As you suggest, this can be a problem if you change the way User Defaults are handled, between versions. One strategy is to examine User Defaults on app launch, and update it's format, if required. (You can also, for example, save the app version in User Defaults, to make this process easier.)

The MacBook arrived dead... You would normally expect a new MacBook to have some charge in the battery. However, it is not impossible for one to arrive with a flat battery, and need charging. If it charged up okay, and now works correctly from the battery, then I would not worry. The part number... MYD82HN/A The page you link to, "Identify your MacBook Pro model", shows: Part Numbers: MYD83xx/A, MYD92xx/A, MYDA2xx/A, MYDC2xx/A From the Apple Menu, select "About This Mac", then "System Report"... You should see something like: You can use the Serial Number to check your MacBook, on this page: https://checkcoverage.apple.com/gb/en/;jsessionid=node01o4ua0xnvvwgv16a1o8styskf02159173.node0

In Xcode, from your apps TARGET, go to the "Signing &Capabilities" tab... Add the Capability "Sign in with Apple"