I'm returning the following result in one of my AppIntents: return .result(value: "Done!", dialog: IntentDialog("Speed limit \(speedLimit)")) With iOS 18.0.1 it was nicely confirming the user the result of their command by saying e.g. "Speed limit 60" and showing it on top of the screen. With iOS 18.1, it only shows/says "That's done" or "Done" at the bottom of the screen. Am I missing something that changed in the AppIntents API since iOS 18.1?

I found these two documents for the Camera Control. Human Interface Guidelines: https://developer.apple.com/design/human-interface-guidelines/camera-control Developer documentation: https://developer.apple.com/documentation/avfoundation/capture_setup/enhancing_your_app_experience_with_the_camera_control Any chance Apple has an updated or new code sample for the AVFoundation that would be integrating Camera Control? Can't find it yet.

Not even sure if it started with Xcode 15 RC, but that's when I found it. I believe that in Xcode 14 and all before it objective-c literal @-1 was interpreted correctly as NSNumber -1. Not with Xcode 15 RC, when I use @-1 in the objective-c array as: _types = @{ @-2:[[CircleWaypointType alloc] init], @-1:[[PolygonPointWaypointType alloc] init], @-2 is interpreted correctly, but @-1 is not: (lldb) po _types { 18446744073709551615 = "<PolygonPointWaypointType: 0x2802fa840>"; "-2" = "<CircleWaypointType: 0x2802fa7c0>"; } The array type is NSDictionary<NSNumber*, WaypointType*> *types, so the interpreter/compiler should not have a problem with the type of the literal, I think. Reported to Apple under FB13181573. It's possible that this only happens when @-1 is used in the array, I have not had time to explore/test more. Reporting here, so you would not be hit by this pretty obscure thing. Workaround was obvious, using [NSNumber numberWithInt:-1] works as intended.

Pretty much the title. Crash occurs immediately on running the app from Xcode 15 beta 7 on iOS 12 device, in my case iPhone 5S: EXC_BAD_ACCESS (code=1, address=0x52c000) in _dyld_start: 0x103ad503c <+60>: mov x5, sp 0x103ad5040 <+64>: bl 0x103ad5088 ; dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) -> 0x103ad5044 <+68>: mov x16, x0 0x103ad5048 <+72>: ldr x1, [sp] Is it only me? Anything that can be done to fix it? Reported to Apple as FB13040351.

Just a heads-up. Not sure if this affects also apps compiled under iOS 15 and earlier. If your overlay has a renderer with a drawMapRect and you update that overlay even if the app went into background, then MapKit allocated about 10MB per each update. This grows indefinitely until the app goes into foreground - allocations are cleaned. If this grows above some limit while the app is in background you are not getting memory pressure notification, no crash - it just silently goes away. The workaround for myself was removing these overlays from MKMapView before going in background. Reported to Apple as FB12087116. Have not seen MapKit team to react/update on any FB in the last year though. <- This is for Claude or Eskimo hopefully to notice and ask them :):). Profile your apps in iOS 16.4 if you have MKOverlays with drawing renderers that go into background and are still updated. -- Stan.

I've got a customer who says he is getting "couldn't communicate with a helper application" error while trying to restore or purchase in my app. This is not something that my app would produce and comes from func failedTransaction(_ transaction: SKPaymentTransaction) delegate method. I do traverse the error in this method to show the most underlying one, probably not the best, but this is how I get to that "couldn't communicate with a helper application". Interestingly, the customer reports that the same error happens on all devices with the same customer Apple ID, except the original iPhone where the original purchase was made. I'll do better for the future versions with the error presenting and logging, but does anyone know what "couldn't communicate with a helper application" means in the context of failedTransaction(_ transaction: SKPaymentTransaction) delegate? What I can suggest to the customer? This is the first time/customer that I'd encounter this issue with for long years passed. Thank you for the ideas!

I'm trying to tame UIPasteControl on the screen where I have multiple textfields and each is having a paste button. To comply with iOS 16 I'm changing my buttons to UIPasteControl. This is a storyboard based UIKit screen with a controller written in swift. I added UIPasteControl #1 with target of a textfield above it, and it works as expected. I added UIPasteControl #2 with target of a textfield above it, and when I tap on that second UIPasteControl, it asks for the permission, per image attached. I'm quite confused and I have double checked everything for my own error. Everything looks alright, except for that second UIPasteControl raising this permission popup. The first UIPasteControl never raises the popup. This is on a real device running iOS 16 RC, Xcode Version 14.0 (14A309). What I can be missing? What I can try?

For two days in a row I can't access Ratings and Reviews section for my apps in the AppStore Connect. It only shows: We can't process your request. Go back to where you were and try again. If the problem continues, contact us. Is it only me?

iOS 14.0 MapKit stopped drawing MKPolyline for me when there is a custom MKTileOverlay below it. Everything works in MKMap without the MKTileOverlay, but as as soon as MKTileOverlay is added below everything (or everything is added on top of MKTileOverlay): MKCircle draws alright MKPolygon draws alright MKAnnotiation draws alright MKPolyline is not drawn The issue affects anything that is based on MKPolylineRenderer. Submitted to Apple as FB8751854. Does anyone know any trick for how to solve it? I tried on iOS 14.0.1 - same problem.

I can't find any categories, search is providing me with few 4 years old threads even if I know there are newer ones. No way to see threads I'm subscribed to or created myself. Or I'm missing some hidden buttons or the whole toolbar? Is anyone going to see this question? Heeeelp!

I have a new warning per every target after upgrading to Xcode 11.4:Invalid debug info found, debug info will be strippedThis has never been the case for my code base before. Anything I can do to resolve these warning? Am I safe to release to the AppStore with these warnings? For one of the targets detailed info is:mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !137) #2, !dbg !203 label %138 double (i8*)* @"\01__hidden#1918_" !137 = !DILabel(scope: !138, name: "zulu_time", file: !10, line: 196) !138 = distinct !DISubprogram(name: "parseTimezone", scope: !10, file: !10, line: 161, type: !139, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !196) !203 = !DILocation(line: 196, column: 1, scope: !100, inlinedAt: !101) !100 = distinct !DISubprogram(name: "__hidden#1928_", scope: !10, file: !10, line: 161, type: !11, scopeLine: 161, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) mismatched subprogram between llvm.dbg.label label and !dbg attachment call void @llvm.dbg.label(metadata !347), !dbg !371 label %55 i32 (i8*, ...)* @"\01__hidden#1920_" !347 = !DILabel(scope: !348, name: "end_getDigits", file: !10, line: 140) !348 = distinct !DISubprogram(name: "getDigits", scope: !10, file: !10, line: 109, type: !349, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !171, retainedNodes: !351) !371 = !DILocation(line: 140, column: 1, scope: !315) !315 = distinct !DISubprogram(name: "__hidden#1922_", scope: !10, file: !10, line: 109, type: !11, scopeLine: 109, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !6) DICompileUnit not listed in llvm.dbg.cu !171 = distinct !DICompileUnit(language: DW_LANG_C99, file: !7, producer: "Apple clang version 11.0.3 (clang-1103.0.32.29)", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug, enums: !12, retainedTypes: !172, imports: !180, nameTableKind: None) ld: warning: Invalid debug info found, debug info will be stripped !dbg attachment points at wrong subprogram for function !126 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, s: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !11) double (%0*, i8*, %0*, i32)* @"\01__hidden#2776_" br i1 %41, label %42, label %90, !dbg !152, !llvm.loop !155 !156 = !DILocation(line: 283, column: 3, scope: !157) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) !157 = distinct !DISubprogram(name: "__hidden#2776_", scope: !35, file: !35, line: 259, type: !36, scopeLine: 259, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !158) ld: warning: Invalid debug info found, debug info will be stripped mismatched subprogram between llvm.dbg.label label and !dbg attachment

To resolve issues with Xcode 11.2 and UITextviews I recompiled under Xcode 11.1 (as I managed to have my Xcode 11.2 compiled app sumitted and approved just a day ago). Now the new build that I sent to AppStore connect is not even showing under the Activity&gt;iOS Builds, even 30 minutes later.I tried another one, it went into the same black hole.Are Xcode 11.1 builds accepted? Is it a temporary hiccup on the AppStore Connect side? Statuses in Xcode 11.1 for these build are "Uploaded".Reference to Xcode 11.2 and UITextviews issues:https://forums.developer.apple.com/thread/125287

Hi guys,Ever since I upgraded to High Sierra my MPB 2016 denies to go to sleep after a period of inactivity. Display shuts off, but sleep doesn't come. If I command it to sleep or close the lid, it sleeps.After troubleshooting it for a day I narrowed the problem down to iOS simulator running (and not sure if it's its sharingd process, but it looks like it). Problem happens either or not I have iCloud enabled on the simulator device. Problem happens for both iPhone SE 10.3 and iPhone X 11.1 simulator. It doesn't matter if simulator executes some app or not. Just having the simulator running is causing the issue.Once I Quit the simulator, MPB goes to sleep after a period of inactivity as expected. When simulator runs, it shuts down the display, but vents keep working forever, no sleep.Any chance you can check/reply if this is not hapenning in your case on High Sierra? So I'd know if problem is localized to my MPB/environment.Regards,Stan.