“xcode github”

I see this: default 15:14:10.967991+0200 sharingd Received Handoff payload reply from via Rapport () with requestIdentifier , xid default 15:14:10.968033+0200 sharingd Received requested Handoff payload via from () for with activity payload of size for requestIdentifier (). RTT: default 15:14:10.970822+0200 sharingd DeviceDiscoveryUpdate: SFDeviceDiscovery (CLink), 0x1 < Info >, cflags 0x21 < AdvData >, ScanRate Invalid, ScreenOff, RSSI Change Detection, RSSI >= -80 info 15:14:10.972649+0200 sharingd NearbyInfo sending activity level, original: 0xb encrypted:0x2 info 15:14:10.972951+0200 sharingd [NearbyAction] Scan restart skipped when unchanged info 15:14:10.972982+0200 sharingd [NearbyInfo] Scan restart skipped when unchanged info 15:14:10.973205+0200 sharingd [Prox] Scan restart skipped when unchanged default 15:14:11.011373+0200 sharingd Streams are being requested from service = default 15:14:11.011430+0200 sharingd Streams are being requested for bonjour name = info 15:14:11.011

Thanks again for your clarifications @DTS Engineer! Here is the flow I am thinking to follow with my existing app so far: Network Traffic │ NETransparentProxyProvider │ ├─ Detect Protocol (first bytes) │ ├─ HTTP ─────> HTTPFlowLogger (existing) │ └─-------- HTTPS │ TLS Interceptor (NEW) │ ┌─────---───────────────┐ │ │ Client TLS Server TLS (terminate) (re-initiate) │ │ └──── Decrypted Bytes ─----┘ │ HTTPFlowLogger (reuse) To start with, I am thinking of something basic: Supporting all HTTP/1.1 traffic so that I can reuse my existing HTTP parser. Is it possible to downgrade(at least a part of) HTTPS traffic without loosing anything while doing so? What can I expect in terms of complexity and performance here? Now, As you've mentioned: Keep in mind that the world has moved on from HTTP/1. A good TLS inspection product should support HTTP/2 + TLS + TCP and HTTP/3 + QUIC + DTLS + UDP To support at least HTTP/2 + TLS + TCP(as I think most of the traffic these days), What's the best approach in this scenario? On

The first sample didn't reproduce on the simulator or device without an accessibility override, which I had active on my device, but forgot. The second sample always reproduces on an iPhone 15 device / sim with affected iOS. Did you test also with this second sample or only the sample code from the initial post? For an iPhone 15 sim the following OS give these results: 17.5 works 18.6 truncates 26.4 truncates 26.5 truncates So it's likely an iOS 18.x regression. To pinpoint this more it would be necessary to download more iOS 18 SDKs. Regarding devices it seems to need a device with 2556x1179 resolution. So an iPhone 16 also reproduces this issue. struct ContentView: View { var body: some View { Text(txt) .dynamicTypeSize(.medium) .fixedSize(horizontal: false, vertical: true) .padding(.horizontal, 20) .frame(maxHeight: .infinity) } } Whether you wrap that ContentView in a ScrollView or not doesn't affect the truncation in my tests. In our main app this is part of an UICollectionView so also

Hi, as I mentioned I'm not able to reproduce it locally, I tried on all my available devices. so I don't have any error logs. I have NSPhotoLibraryAddUsageDescription and I reuse the same code in 3 of my production app that are on the marked for 9 and 10 years I never had those complaints until last month. My app also supports accessing user content (videos from Photos or Documents) they can load videos and reference them side-by-side with the recorded content. But it seems like a bug to me on the new version? I don't see anything that I changed. 2. It affects maybe 1% of users, and it works fine for 99% of users just fine. 3. In the analytics it appears there are no users affected by those error with Full Photos access, but I added those analytics just a couple days ago, before I wasn't tracking those errors. 4. I think I should be able to reproduce the error given how many times I already tried. However until recently I was still using Xcode 16.3 to deploy to AppStore because of supporting older iO

Hello! Thanks for reporting this issue! We believe it's fixed in Xcode 26.5 Beta 3: https://developer.apple.com/documentation/xcode-release-notes/xcode-26_5-release-notes#Localization When you have a chance, can you please download Beta 3 and verify it? Thanks!

Hi Marcin, Were you able to solve this? Or perhaps a newer Xcode version solved it?

I think you’ve misunderstood the point of this thread. When everything is working correctly you can indeed delete simulator runtimes using Xcode > Settings > Components. The issue that jamesic and revoceci have encountered indicates that things are not working correctly. The thread that revoceci referenced is where we’ve been discussing this issue in more depth. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com