Is the Swift Playgrounds for iPad (ver 3.4) no longer able to handle a Text() view within a ForEach Loop?

Question

Created Nov ’20

Replies 5

Boosts 0

Views 2.4k

Participants 5

The following code fails to run from a fresh Blank Swift 5.3 playground in the Swift Playgrounds app for iPad.

I have cut and cut the original code down to this ... which I think is pretty simple. I have also tested this for any syntax errors on MBP Xcode (where it runs with no problem). However on the iPad, after the new Playgrounds app update, it fails on line 26 with:

Abort() called

Code Block  swiftimport PlaygroundSupport
import SwiftUI
struct Fruit: Identifiable {
    let id = UUID()
    let name: String
    let emoji: String
    
    static var list = [
        Fruit(name: "Apple", emoji: "🍎"),
        Fruit(name: "Bannanna", emoji: "🍌"),
        Fruit(name: "Cherry", emoji: "🍒"),
        ]
}
struct ContentView: View {
    
    let fruitList = Fruit.list
    let sortAscending = false
    
    var body: some View {
        
        List {
            ForEach( fruitList ) { fruit in
                HStack {
                    Text("\(fruit.emoji)")
                    Text("\(fruit.name)")
                }
                .font(.title)
            }
        }
    }
}
PlaygroundPage.current.setLiveView( ContentView() )

This and many other apps have all broken after the iOS Swift Playgrounds app updated to version 3.4.

Boost

Answer 1

Tylor OP

Nov ’20

This was able to be fixed via added the frame modifier to the list view.

Code Block SwiftList {
	ForEach( fruitList ) { fruit in
		HStack {
			Text("\(fruit.emoji)")
			Text("\(fruit.name)")
		}
		.font(.title)
	}
}.frame(width: 500, height: 500)

I would assume based on the other question with Abort(), that Abort() is called if it is about to crash, and it seems that the view isn't getting the bounds of the screen in the live view, so it doesn't know how/where to render the view.

0

Answer 2

richiwalt OP

Nov ’20

Okay ... More information ... Seems these slew of Errors that I have been observing only occur for Swift Playgrounds app when it is running on an iPad. (And I did not even know you could get this same Swift Playgrounds app on MBP. Of course, if I am going to be working on my MBP, I'd opt to use Xcode instead.)

But all these programs, (that fail when running from this app on my 4th Gen 2020 12.9" iPad Pro), work fine on Mac. Same code, as all my programs are stored in iCloud !

This fact alone negates me having to post examples of what fails, for others to try to spot any errors. If the same code runs fine from MBP, from this app ... but fails when run from this app on iPad ... then we definitely have an implementation issue on iPad for this app.

The question is ... where is the best place to communicate this with Apple ? Does Apple monitor these post and get back with the developers ? If I had an issue with Xcode, or with an app, I could use my Developers account to create a ticket (I guess, I am new to the Developers account). But with this app ... not sure how to create a ticket exactly.

0

Answer 3

DaddieMac OP

Nov ’20

The "fix" of using a frame did not work for me. Really annoying problem!

0

Answer 4

xdman OP

Dec ’20

Paul Hudson recommended to file a feedback at Feedbackassistant. So I did:
Feedback Assistant - https://feedbackassistant.apple.com/feedback/8923682

0

Answer 5

j.che OP

Feb ’21

I have the same problem and the frame() trick hasn’t worked for me. Thought this could be related to my old iPad 5th gen. but clearly it’s not. Here is a kicker I discovered just days ago:

Enter any “Learn to code” tutorial and instead of typing what the lessons ask, try this simple test of the bug:

Code Block import SwiftUI
import PlaygroundSupport
let s = List(1..<6) { n in Text("\(n)") }
PlaygroundPage.current.setLiveView(s)

It will work!! Why not in a clean playground? What’s missing? This issue has extended for too long. I have a mac mini 2012 and can’t run Swift 5.3 code. I eagerly awaited for this update to the IPad app. Really frustrating. I blame Covid-19!!

0