Still having this problem in Xcode 13.4.1. What the heck
Post not yet marked as solved
You must be a teacher with your own opinions already cemented. The documentation is very clear and provides examples. Stop fighting the system and follow the examples, perform actual test, and assess the results instead of fighting those providing the answers to your somewhat rant list of questions. As some will say, Read The ******* Manual.
Look, I am just asking these simple questions:
What exactly is "focus"?
What isn't focus?
What is the relationship between FocusState and accessibility focus?
What is the relationship between whether a SecureField is being edited, and whether it's "focused"?
If you know the answer, even if you're just copy-pasting it from somewhere else, please leave it as a response to this post, and if it's correct then I'll mark it correct.
But please don't just reply and accuse me of being a teacher, because (a) I'm not a teacher, and (b) the documentation does not define what focus means, exactly, or whether it always directly corresponds with what's being edited, or not.
I'm not fighting any systems; I just want to know the answer to these simple questions. Performing tests on devices or simulators won't tell me how it's supposed to work. Thanks.
Post not yet marked as solved
Note: I did find this discussion of the five "focusable states" in tvOS but this doesn't tell me which of these states "isBeingEdited" (if it existed for SecureField, which it doesn't) should correspond to if we're talking about iOS instead of tvOS. https://developer.apple.com/design/human-interface-guidelines/tvos/app-architecture/focus-and-selection/
Post not yet marked as solved
@Frameworks Engineer wrote:
If the system medium detent isn't sufficient for your use case, you may need to continue to use your own card/sheet implementation.
< < <
Problem is, the .sheet modifier doesn't give you the medium detent. It only gives the large detent. (Always covers the whole screen.)
Apple... if you're listening... please add more flexibility to these SwiftUI APIs. Like... why are you adding functionality that's only available to UIKit? Are you deliberately trying to make adoption go as slow as possible while we reinvent every wheel?
Post not yet marked as solved
@EA7K
All we can do is file FB tickets and pester our WWDR reps about them if they don't get addressed.
The squeaky wheel gets grease.
Post not yet marked as solved
On iOS 15, when our app runs we see: AMFI: constraint violation /private/var/containers/Bundle/Application/272392ED-BF0A-48A0-8FB1-4FB707B234A0/REDACTED.app/Frameworks/SwiftProtobuf.framework/SwiftProtobuf has entitlements but is not a main binary
for all our .frameworks.
I checked and all our .frameworks have an empty plist as their entitlements, even though none of them specify an entitlements plist in anywhere in Xcode.
Pray tell why these empty plists are being added Eskimo? And also, why does it trigger a violation in AMFI?
Post not yet marked as solved
We usually see this error when launching tests, where the test bundle has a Mach-O type of "Bundle" as it should.
Post not yet marked as solved
We fixed these issues by adding most of the Xcode executables into the exceptions list of Developer Tools in Security & Privacy system preferences.
There is another trick you can use.
First you make a dummy class that conforms to UIWindowSceneDelegate:
swift
open class MyWindowSceneDelegate: NSObject & UIWindowSceneDelegate {}
Since all the requirements of UIWindowSceneDelegate are optional, the compiler will be happy. Afterwards you can do this:
swift
open class MyRealWindowSceneDelegate: MyWindowSceneDelegate {
@objc var window: MyCustomUIWindowSubclass
}
At runtime when window is resolved, it will be of type MyCustomUIWindowSubclass.
Post not yet marked as solved
Having this problem in Xcode 12 using a playground that used to work in Xcode 11 and 10. Trying to import a class in a framework from the same workspace. Playground compiles fine but then we get "error: Couldn't lookup symbols". Why can't Apple make Playgrounds "just work"? How about giving us a way to explicitly link certain frameworks to the playground so it never has this problem...?
Post not yet marked as solved
Having the same problem. Unless we embed packages directly to the framework that has the code which is being previewed, then previews can't find the package dependencies. Super annoying!
Post not yet marked as solved
Is your DerivedData folder in a location not being indexed by Spotlight? Why would Spotlight have anything to do with whether Instruments can find symbols?
macOS allows the user to omit whatever directories they want from Spotlight. Since Spotlight is such a performance hit and serves no useful purpose, I disable it for everything except /Applications.
Why would that prevent Instruments from finding something? Can't it just use unix find command?
Post not yet marked as solved
Any luck on this? Having the same issue on 12.2
