@discorevilo I have also noticed weird connectivity issues on 26.4 beta 1 and 2, specially when connecting to local IPs in WKWebView

Same happening in the Home Assistant Mac (catalyst) app for a long time already, more info in this radar: https://openradar.appspot.com/radar?id=EhAKBVJhZGFyEICAgKbrqe0J

Thanks for the overview once again, the problem is that the app works correctly for long periods of time, until on a random day, the OS tell the app the local access permission is denied, even though if the user manually checks the permission it is enabled. So... I could test my app how many times I want but I can't predict when this will happen. Anyway, I will report this directly then.

At this point my assumption is that it does not work from a widget context.

@DTS Engineer Thanks for the overview but I am in a dead end situation, I just finished reading TN3179 but I still don't know what to do when a user reports that my app is saying that it needs location network permission enabled even though they already enabled that (macOS). If it's difficult for developers (and in this case actually not possible) to reset this permission, for the end user is impossible, so this means I have to tell my end user it is "an Apple bug" once again. Any alternatives to provide? Context: I work on Home Assistant App, a smart home platform which connects locally to their smart home server. The Apps essentially needs the local network permission and every single user gives the permission, but some in macOS 15.3 are reporting that even though the permission is given, the app still reports it is not, and logs also confirm that.

Does anyone found a solution?

Issue also noticed here: https://github.com/react-native-webview/react-native-webview/issues/2356

I found a workaround, if you set visionOS as the BASE SDK, it succeeds

Same here, after adding visionOS as target to my iOS app, I get the same error messages after xcode cloud finishes running

Today I finally made it work, not sure exactly what I did, but first it started working on my iPad with beta iOS, then suddenly also on my iPhone with stable iOS. I also think I removed and added back the ”manage thread networks” capability in the project. QUESTION: The Only thing I wasn’t able to succeed is to store my thread network using THClient “store credentials” method, it always says I’m passing invalid parameter, so my question is how to convert my borderAgentID string into Data properly, same for the dataset string. Anyone succeeded on that?

Same here, even with the official entitlement. I already tested on stable versions of iOS and Xcode aswell as beta versions, no success yet

We are also talking about this herE: https://developer.apple.com/forums/thread/718467?page=2#771875022

I am experiencing the same issue here, when running on iOS 17.1.1 I get: Client: -[THClient getConnectionEntitlementValidity]_block_invoke - Error: And when trying to retrieve credentials: Thread 1: Fatal error: 'try!' expression unexpectedly raised an error: Error Domain=ThreadCredentialsStore Code=3 "Failed to retrieve all active border router records" UserInfo={NSLocalizedDescription=Failed to retrieve all active border router records, NSUnderlyingError=0x282c197a0 {Error Domain=NSOSStatusErrorDomain Code=0 "(null)"}} I also tried to do the same on mac and as previous mentioned in this thread, it silently does nothing, no error but also does not succeed.

Did you find a workaround or a fix for it? I'm also facing the same problem, I can make it happen for large titles but not for small titles. According to the modernising apps session from WWDC19 it should work for both