How does it fail to load? Is there an error? Can we see the code that's trying to load it? We really cannot help you with such little detail. It's like telling us your car won't start but not telling us why.

This is a really strange way of converting an app from ObjC to Swift. You should tell your company that you can convert one bit at a time, and that it will be tested appropriately. Being asked to keep two versions of code working in the same app, to me, seems absolutely insane.

These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks. (Also, you randomly picked some tags to add, which should've been a red flag to you that you were in the wrong place, and now people searching for those tags will have your entirely unrelated post come up.)

Can someone access these texts on a website? If so, then I don't think just displaying some text in an app is at all useful. You need to make the app do a LOT more than just showing religious texts.

Right, so as I said, this is nothing to do with us random developers, and is an issue personal to you and your use of your device. Please post your question with more details in the Apple Support Forums (link in previous reply). Thanks.

Would .navigationBarTitleDisplayMode(.large) work?

Right, so have you implemented anything to adhere to those rejections? Your app really does need to be more useful. If it's just a minimal front-end to a website or something, it doesn't need to be an app and will be rejected. And yes, if you offer to create accounts you have to allow a user to delete their account entirely. I don't see your issue here.

You need to go to your account at: https://developer.apple.com/account/ In there, tap the "Membership details" card at the top, or scroll down. There's an "Auto-renew" switch. If your account expired, there may be something else there (but I can't confirm as my account hasn't expired...). Hope this helps. I wouldn't expect to use the Developer app for this sort of thing.

You need to raise a feedback request for this. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. While there are some Apple employees on here, they aren't here to handle feature requests. You can raise a feedback request here: https://feedbackassistant.apple.com/

Have you definitely added .resizable() to the Image? Show us some code where you've tried frames etc.

That's because I think you're using the preview in the wrong way. The preview is there to show you what you've developed, i.e. your ConsoleView(), but you're adding an extra button into there that doesn't exist in the code you're testing. Just use the preview like this: #Preview { ConsoleView(lines: "x\ny\nz\n") } That previews the ConsoleView with the initial value (x, y, z). You should use the preview to preview code you've developed. If you add extra things like that button, you're not really testing the code you've developed.

Not appropriate for these DEVELOPER FORUMS.

Great. I can't drive to the shops. If I give you very little information you can't help me. It works the other way round, too. How can we actually help you? You need to give us more information. Are you developing an app and you're having an issue with a specific field? If so, give us some code and we might be able to see what the issue is, and suggest a solution. If you aren't developing an app, and you're seeing an issue in some other app that you're using, then either get in touch with the developer of that app, or post your question with more details in the Apple Support Forums. Thanks.

I agree with Claude. Don't do it. Or, change it so it says something else and uses a different font/style. Aside from that, why is there a reflection of someone (you) taking a photograph? I hope you didn't take a photo of this when you could easily take a screenshot... :)

I have issues outstanding that I haven't received a response to for years. I don't expect a response, and for you to complain that your minor issue in one bit of documentation hasn't been addressed in, gosh, just 23 days, is asinine. Any good developer would test their code to confirm it works before sending it to production, and if they'd found an issue, they'd raise it and move on. They wouldn't grumble about not being contacted.