Better visit forums.swift.org, where you can find the core members of the Swift team.

What sort of CocoaSlideshow have you downloaded? I cannot find one in Apple's pages. I cannot display the interface in XCode. Old apps may be using .xib (or .nib, if it's too old) instead of .storyboard. Or the app may be constructing UI by code. How can I display the interface in this project? If you cannot find any in a buildable project, no way. The project may not have a visual interface definitions like storyboard or xib.

Please try View Debug Area Activate Console. The debugging console will show automatically with this. If you want to keep the Debug Area always shown, View Debug Area Show Debug Area.

It may happen when you touched project files directly from outside of Xcode. And may happen in another cases. Can you explain what you have done till you get the error?

SwiftUI encountered an issue when pushing aNavigationLink. Please file a bug. Seems to be a different issue than the problem in your opening post of this thread. Better start a new thread for the new issue, please keep one thread one topic. But as the error message is suggesting, it may be caused by some bugs of the current implementation of SwiftUI. If you find some weird behavior which might be related to the message, you may need to find some workarounds until Apple fix it.

Your Fighter has only one initializer taking a parameter name. What do you want to pass to the parameter name? let fighter = Fighter(name: ???) //- You need to clarify what is placed to `???`

Thanks for showing your code, but please use the Code block feature (see icon `) of this site. NavigationView{...} is only needed in the root view. Remove it from the second and third view. the back button is coming further and further down the screen vertically. That happens because your are stacking many navigation bars using nested NavigationView`.

It depends on the definition of Fighter. Please show the code of Fighter. And please use Code block (see the icon ``) feature of this site when posting codes. And you should better not show partial code, when parentheses are not matching, there may be some issue in the hidden parts.

Your code is sort of a mess (an example of bad usage of bytes) and can be simplified as: func peripheral(_ peripheral: CBPeripheral, didUpdateValueFor characteristic: CBCharacteristic, error: Error?) { let u16 = characteristic.value![0] let chart = Character(UnicodeScalar(u16))// make into a character // } (And you should better avoid naming u16 for a variable of type UInt8.) So, where is your 20 bytes placed? Next to the first byte (u16)? Or some where else? One more, what the 20 bytes are representing? 10 sixteen-bit integers? Or a text containing maximum-20 ascii characters? Or something else?

Maybe you are using NavigationView in a wrong way. Can you show all the codes of your views, from the root to the third view?

Although this is clearly recommended by documentation. The article you have referred does not contain any sort of recommendation for third party apps.

The following produces the same error, which I reckon is a compiler bug I do not understand why you think your new code would be a compiler bug. You declare a let constant stop without initial value, so you need to assign an initial value to it before it is used. But you are using it and that is causing the compiler error you described. Why do you think your new code is valid?

Thanks for showing the issue-reproducible code. I do not have a font named Lato-bold nor a Color primaryColor, but could have confirmed that what you have described did happen with some specific fonts. Can't you use baselineOffset modifier? Text("\(quiz.question)") .font(.custom("Lato-Bold", size: 17)) .baselineOffset(5) //- .foregroundColor(Color.red/*("primaryColor")*/) .multilineTextAlignment(.center) .fixedSize(horizontal: false, vertical: true) .lineLimit(nil) .padding(.horizontal)

my background-view is not adapted to the display size.  Only the background-view is your issue and other things in other views are shown using full screen?

can someone help ?  You should better start your own thread. Not many readers make attention to the thread marked as SOLVED.