It's very real for US-based developers. https://smallappdeveloperassistance.com Here is the actual federal court record: https://www.govinfo.gov/app/details/USCOURTS-cand-4_19-cv-03074 One of the four law firms: https://www.hbsslaw.com/press/apple-ios-app-developers/us-ios-developers-to-benefit-from-100-million-apple-small-developer-assistance-fund-and-changes-to-app-store-policies-in-developer-antitrust-class-action-settlement Important Dates March 21, 2022 — Exclusion Deadline March 21, 2022 — Objection Deadline May 20, 2022 — Claim Deadline June 7, 2022, at 2 P.M. — Final Approval Hearing Do your due diligence in finding the three law firms but this is one of the four law firms that handled the case for the various plaintiffs and mentions the same site above responsible for dispursing the funds. The Canadian Developers are probably sleeping on this one

You might have better luck using one of your Code Level Support Tickets where Apple can investigate directly & discreetly.

Well both can't be presented at the same time. When $isPresente1 is set true always set $isPresente2 to false and vice versa. The correct thing to will be to use only one fullScreenCover and based on some other state show the appropriate view. Something like below but you will have to work out the details. content .fullScreenCover(isPresented: $isPresente1 || $isPresente2, content: { if isPresente1 { return SOMEView() } else if isPresente2 { return SomeView2() } else { EmptyView() } })

The system sometimes does this.

Revisit the design of your data model. Does it represent the state of each question as in being answered or not answered in addition to the question being answered? So when the table view is reloaded it takes into the various states persisted in the data model as it renders the cell.

Using a TableColumn requires a Table {// content } rows: { // data source } pattern similar to below. Where in the example rowItems is a collection of Items for the data source. Items struct Item { let from: Date let to: Date let hours: Double } // The table view Table(selection: $selection, sortOrder: $sortOrder) { // Sort column on \.from key value path of item             TableColumn("From", value:\.from) { item in                 Text(item.from(date: .numeric, time: .omitted))             } // Sort column on \.to key value path of item             TableColumn("To", value:\.to) { item in                 Text(item.to.formatted(date: .numeric, time: .omitted))             } // Sort column on \.hours key value path of item             TableColumn("Total", value:\.hours) { item in                 Text(item.hours)             }         } rows: { // Populate the rows data source with TableRow types containing an item type from the rowItems collection which is passed on each TableColumm.             ForEach(rowItems) { item in                 TableRow(item)             }         } See Apple example code here: https://developer.apple.com/documentation/swiftui/building_a_great_mac_app_with_swiftui

What is LibraryContentProvider and what is the error?

You will not get a response from here your question is better served here as it is developer related: https://discussions.apple.com/welcome

Ensure there is not another fetch request named fetchRequest because you're declaring a let fetch = ... but passing a fetchRequest to the context.fetch(...) instead.

Because you're calling your code in the viewDidLoad override, firstLoad is not required. The viewDidLoad only gets called once and only once per instance. firstLoad and points: [Atkie]() should be instances of the view controller and not globals. One of the nice things about swift are its high order functions. The calculateSumPoints method can be rewritten as follows: func calculateSumPoints() {     let sum = points.compactMap { $0.point } // this remove any nil point string values from the collection         .reduce(0) { previous, next in // using reduce we access to the previous and current value             guard let value = Int(next) else { return previous } // unwrap next as an Int if it fails return the previous calculation             return previous + value // return the sum of the previous value and the next value         }     totalPoints.text = "\(sum)" }

Read here https://www.raywenderlich.com/1484288-preventing-man-in-the-middle-attacks-in-ios-with-ssl-pinning https://betterprogramming.pub/how-to-implement-ssl-pinning-in-swift-7c4e8f6ee821 Recommended https://www.netguru.com/blog/certificate-pinning-in-ios

Please present these questions to your MDM vendor as each MDM solution has its pros and cons.

You have a range of options but first describe what you're doing with the Spin Wheel? By Answering this we will known if you're referring to an item picker for dates and time, or some kind of data model or as Claude31 suggested an activity indicator to indicate there is some kind of background or UI processing taking place.

No.

See here: https://developer.apple.com/documentation/corenfc/building_an_nfc_tag-reader_app