Post not yet marked as solved
Perhaps the fix has been implemented in Xcode 12.5 Beta 3:
Resolved Issues
Fixed an issue that caused OS X 10.11 and earlier to reject packages signed on OS X 10.11 and earlier. (71695608)
Known Issues
OS X 10.11 and earlier may reject code signatures added to universal binaries by Xcode 12.5. (70724583) (FB8830007)
Workaround: Specify --digest-algorithm=sha1,sha256 to the codesign utility at signing time. In Xcode, specify this using the OTHER_CODE_SIGN_FLAGS build setting.
I understood that you would a single click on the "+" button create a new List's item and follows its link.
If it is so the NavigationLink init has to be the one with a tag and reference to a tags' selection, the addJob function have to create the new job's item and set the reference to point to it.
The simplified code below use an, improper, set of Int as job's ID.
import SwiftUI
struct ContentView: View {
var body: some View {
JobsView()
}
}
extension Int: Identifiable
{
public var id: Self { self }
}
struct JobsView: View {
@State private var jobs = [0, 1, 2]
@State private var selection: Int? = nil
var body: some View {
NavigationView {
List {
ForEach(jobs) { job in
NavigationLink("job \(job)",
destination: JobOverView(job: job),
tag: job,
selection: $selection)
}
}
.toolbar {
Button(action: addJob,
label: {Image(systemName:"plus")}
)
}
.navigationTitle("Jobs")
}
}
private func addJob() {
jobs.append(jobs.last!+1)
selection = jobs.last
}
}
struct JobOverView: View {
let job: Int
var body: some View {
Label("Job Info \(job)", systemImage: "chevron.down.circle.fill")
}
}
Post not yet marked as solved
In my case I restored from iCloud as well as from iMac backup and both worked.
Anyway the restoration don't change the iPhone boot, so in case of a failure (perhaps a power loss) the restore could be done again.
The restore from a full, password protected, backup in iMac restored also sensitive data as passwords and fingerprints, in either case password will be re-synched from iCloud, if the were there, and fingerprints have to be re-recorded.
Post not yet marked as solved
I found that List in a ScrollView works only if it don't use the entire space.
GeometryReader
{ (geometry) in
ScrollView()
{
let w = geometry.size.width
let h = geometry.size.height
List
{
....
}
.frame(width: w>0.1 ? w-0.1 : 0, height: h>0.1 ? h-0.1 : 0)
}
}
Post not yet marked as solved
DocumentGroup(
newDocument:
{ () -> MyDocumentClass in
return MyDocumentClass() // Create a new document
},
editor:
{ (file: ReferenceFileDocumentConfiguration<MyDocumentClass>) -> FieldViewWrapper in
file.document.url = file.fileURL // Now get the url
ContentView() // View/Edit the document
}
)
Post not yet marked as solved
Using Reference File Document Group followed by NavigationView I've been able to have a document group that open a navigation view, which have the sidebar.
Here an extract:
import SwiftUI
@main
struct MyApp: App
{
var body: some Scene
{
DocumentGroup(newDocument:
{ () -> myDocumentClass in // Create a new document
return myDocumentClass()
},
editor:
{ (file: ReferenceFileDocumentConfiguration<myDocumentClass>) -> ContentView in
return ContentView()
}
)
}
}
class myDocumentClass: ReferenceFileDocument
{
typealias Snapshot = ContentView
var myData: Snapshot
...
}
struct ContentView: View
{
var body: some View
{
NavigationView
{
sideBar()
mainView()
}
.navigationViewStyle(DoubleColumnNavigationViewStyle())
}
}
Post not yet marked as solved
I have the same issue, and studied various solutions. In my opinion 'preferredFilename' seems be the best, in theory. unfortunately currently even I didn't found a working solution.
Post not yet marked as solved
With Xcode12.2 beta (12B5018i) I don't have anymore the issue. It should be resolved.
I found by myself that is possible since on iOS 14.
func encode(to encoder: Encoder) throws
{
var container = encoder.container(keyedBy: CodingKeys.self)
if #available(iOS 14.0, *)
{
let convertedColor = UIColor(mycolor)
let colorData = try NSKeyedArchiver.archivedData(withRootObject: convertedColor, requiringSecureCoding: false)
try container.encode(colorData, forKey: .color)
} else
{
// Fallback on earlier versions
}
}
Code 12 beta 3 fixed the issue.
Post not yet marked as solved
Xcode 11.6 Beta is currently, June 23 2020, the only one supporting iOS 13.6
I have a payd account to Apple Developer Program since 17 April.
I'm a "new" developer but I have another App already available on the App Store in its second version (and its 8th build).
Post not yet marked as solved
I received from Apple's support the suggestion to remove the revoked certificates from the Keychain, leaving only the current one, which is valid (for my peace I did a bakup just before deleting the old certificates).After that I retried and the upload was succesfull.So I shared here this experience in the hope it could be beneficial to all, of at least some, of you.Of course I'm going to replay to Apple support that this workaround shouldn't be the case closure. I'm going to report here eventual news.
Post not yet marked as solved
Thanks joelloyd-bybox,hope this has been a temporary issue already resolved (perhaps after the support request I, perhaps also others, have sent).I'll notify here as soon as I receive an official reply from Apple
