User Profile

Hi, it seems gRPC stopped working on WatchOS 9. I suspect it's the same underlying reason as https://developer.apple.com/forums/thread/127232 and https://developer.apple.com/forums/thread/715024?answerId=728915022#728915022. Is that correct? My gRPC client works fine in the Watch simulator and on iOS, but on Watch devices channels seem to disconnect. Does anybody know if this functionality is gone for good, or is it expected to work?

I'm implementing XCUI tests for an Apple Watch app and have trouble with text fields. I suspect it's a bug (FB9983700) TextField("Hello, World!", text: $text) .accessibilityIdentifier("hellotext") XCTAssertTrue(app.textFields["hellotext"].exists) // Fails on watch but works on iPhone I found a workaround by using otherElements instead of textFields, but then the test will have to be different between iOS and watchOS. Does anyone know of a better way?

I'm using ASWebAuthenticationSession using Authorization Code Flow. In this flow I get a code token back from ASWebAuthenticationSession that I exchange for access and refresh tokens from my server. I store those in KeyChain. This works fine, but the problem is when I want to log out and log in with a different account.Logging out is two steps:1. Throw away my keychain tokens2. Call ASWebAuthenticationSession to logout from the servers.The second step has a strange user experience though, as it will ask concent for logging _in_! If I skip this step, and try logging in again using ASWebAuthenticationSession, it will not show the web view unless enough time has passed since the previous login.So, I was thinking that most users don't login and logout often so I could check if enough time passed since the login and then skip step 2. Not good, but still an improvement.Does anyone know how long that timeout is? I tested and it seems it may be one hour. Perhaps it's some kind of cookie lifetime or something that the server controls.Or is there a better solution?