I did not know that. Could you please provide an official document confirm that ? Submit your iOS and iPadOS apps to the App Store - https://developer.apple.com/news/?id=itpt8dkc Starting April 2021, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 12 and the iOS 14 SDK. Before April 2021, you can use Xcode 11+ and the iOS 13+ SDK, but not Xcode 10.1.

its not display anything . Then your item.image is not what I expect. Are you sure it does not contain schemes like https:// as you have shown as an example? UPDATE i solved the problem. instead of .urlPathAllowed - urlQueryAllowed and it worked. Thank you so much for help. Happy to hear you solved your issue. If urlQueryAllowed worked, I guess your image contained scheme.

Can you show some example of whole text string? With control+command+spacebar, you can input any Unicode character so it does not give any meaningful info.

What do you mean by the default functions?

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

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?

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)

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?

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

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?

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?

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.

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`.

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 `???`

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.