Post not yet marked as solved
Looks like iOS14 is releasing tomorrow. Maybe we'll get an update today???
Post not yet marked as solved
:facepalm: Well I suppose I can remove my 2.0 to create 1.0.4, but I do not see an option to do so. It's been submitted for test-flight testing, but it's not something that's live on the store.
Posting to help the googlers:
I was experimenting with an in-app-intent, and I defined this intent in the same file as my other out-of-app-intents. The target membership of this single intent definition file needs to be both the standard intent extension and my App. This is so the App can cast the intent passed to the Scene via UserActivity and handle intents that open the app.
It seems however that the in-app intent cannot be compiled into both the out-of-app intents bundle and the main app bundle. (The intent in the ITS error message is an in-app intent)
This was accepted by App Store Connect a few days ago, but I guess they changed their validation rules as they get ready for iOS14. :shrug:
I fixed this by creating a second intent definition file named "InAppIntents.intentsdefinition" and moved the in-app intent into this file. The target membership of this file is set to only be the app.
After duplicating and renaming some intent-types I got it building, and uploaded it without problems.
Post not yet marked as solved
With beta7:
When I scan a QR code, I no longer get the Safari URL notification, however If I exit the camera and navigate to the local experience page and tap "save" then I see the notification pop up.
Seems like it's intercepting the URL, but invoking the sheet. Then when I tap save it "releases" the held up URL and it shows the standard safari notification.
Also, lets say I do us "portfolio.com/OrrangesApp/Clip" Does this have to resolve to an actual web page? If nothing existed on the web server at that location would it direct iOS14 users to the app clip, and other users to a 404?
Post not yet marked as solved
I would also like to know this.
Oof. Putting this here for the community:
Thank you for filing this feedback report. We reviewed your report and determined the behavior you experienced is currently functioning as intended.Existing bookmark are force-expired at the update to iOS 14. There’s nothing the user/developer can do about it, except for checking that the bookmark resolves before presenting it to the user as accessible.You can close this feedback by clicking on the "Close Feedback" link. Thank you.
Thanks Eskimo. Unfortunately this app is new enough that it does not have an iOS12 version. Updates between iOS13 versions have been okay though.
FB8481000
Found my mistake. My closure that was updating the cell was updating a stale cell that had since been replaced.
Updating accessories on cells works great - Just gotta do it on the right cell.
Post not yet marked as solved
My App is breakpointing at this exception on beta4 as well, but If I click "continue" it will proceed as normal.
Post not yet marked as solved
I submitted feedback for this. I saw the same regression between beta3 and 4. In my case I was actually assigning a UIMenu of UIActions, so there was no chance of an un-found selector causing the disabled state.
Found a french tweet that I ran through google translate and finally solved this insanity with NSMenuToolbar item. This is actually available in the previous version of catalyst and I had no idea.
let addItem = NSMenuToolbarItem(itemIdentifier: .addItem)
addItem.itemMenu = menu
addItem.image = UIImage(systemName: "plus")
Post not yet marked as solved
Dropping the following into the didReorder block has helped me a little as I dive into this more. Pasting for future people in my position.
print("++++++++++++")
print("\(transaction.difference.count) TOP LEVEL DIFFERENCE CHANGES")
transaction.difference.forEach { change in
switch change {
case .insert(let offset, let element, let associatedWith):
print("INSERT OFFSET: \(offset) ELEEMENT: \(element) associated: \(associatedWith)")
case .remove(let offset, let element, let associatedWith):
print("REMOVE OFFSET: \(offset) ELEEMENT: \(element) associated: \(associatedWith)")
}
}
print("------------------------------------------------------------")
print("\(transaction.sectionTransactions.count) SECTION TRANSACTIONS")
transaction.sectionTransactions.forEach { sectionTransaction in
print("...........................................................")
print("\(sectionTransaction.difference.count) DIFFERENCE CHANGES in \(sectionTransaction.sectionIdentifier)")
sectionTransaction.difference.forEach { change in
switch change {
case .insert(let offset, let element, let associatedWith):
print("INSERT OFFSET: \(offset) ELEEMENT: \(element) associated: \(associatedWith)")
case .remove(let offset, let element, let associatedWith):
print("REMOVE OFFSET: \(offset) ELEEMENT: \(element) associated: \(associatedWith)")
}
}
print("...........................................................")
}
print("------------------------------------------------------------")
print("++++++++++++")
}
Thank you for posting your answer. This saved me a bunch of hair pulling.
Post not yet marked as solved
The context of this question is setting ViewControllers into the secondary column when in a compact environment. It appears as if it always retains the first view controller no matter how many additional ones I set.
