This is the first time I’ve tried to run an Xcode app on my iPhone. To do this, the iPhone must have “Developer Mode” enabled but this settings was not visible on my iPhone. I searched the blog and did not find a suitable solution. Eventually, I got it working so wanted to publish my findings. I am documenting this after trying many things so I am not 100% sure of the magic formula, but “I think” this is what is needed. PROBLEM iPhone -> Settings -> Privacy & Security -> Developer Mode (NOT VISIBLE) ENVIRONMENT iPhone 12 Pro Max running IOS 16.2 MacBook Pro running macOS 12.5.1 Xcode 14.2 CONNECT IPHONE TO MAC (via USB cable) CHECK DEVICE STATUS (in Xcode) Select menu Window -> Devices and Simulators You should see your iPhone but it will show warnings/issues. (e.g. device not in Developer Mode) ADD APPLE ID (in Xcode)  Open your app project in Xcode Select menu Xcode -> Preferences Select Accounts tab Add your Apple ID (It will be listed as a “Personal Team”) SELECT IPHONE AS DESTINATION (in Xcode)  Select menu Product -> Destination -> Choose Destination In the “IOS Device” section, select your iPhone as the destination (NOTE: After doing this, the “Developer Mode” setting was available on my iPhone) iPhone -> Settings -> Privacy & Security -> Developer Mode (Now visible) SELECT DEVELOPER MODE (on iPhone) Settings -> Privacy & Security -> Developer Mode (ENABLE) SELECT APPLE ID AS TEAM (in Xcode)  Select your project in the Project Navigator Select the project in the TARGETS section Select “Signing & Capabilities” tab In the “Signing” section, select the Team as your Apple ID (you previously entered) After this, I had an error and need to modify the “Bundle Identifier” to make it unique. I just added some numbers to the end and it worked. CHECK. DEVICE STATUS (in Xcode)  Select menu Window -> Devices and Simulators This time, your iPhone should appear without any warnings/issues. LOAD APP ONTO IPHONE (in Xcode)  Hit the arrow in Xcode to Start the active scheme. (The App will be loaded onto your iPhone.) RUN APP (on iPhone) Try running the app and the iPhone will not allow it since you have not authorized apps from this developer. Goto Settings -> General -> VPN & Device Management Authorize your Apple ID to run apps on this phone. You should now be able to run the app without issue.

above ios 16 and use Xcode 14 to make ipa this problem will happened when you call MCOIMAPFolerInfoOperation's start method the app crashed ! can not get any logs but below and equal to the 16, it's fine if you run through simulator , it's ok if you Archive a ipa and install it in a iphone with ios version >=16, when you call that method app will crash ! please help me , thanks !

DriverKit Extension or HIDDriveKit is available for ios If it is used on ios, do I need to apply for hid authorization from Apple?

I  am completely at a loss here - I have a react native app created within expo. It runs perfectly well with expo go. I then built it using eas on my Mac (latest Ventura OS installed) and posted it to app store connect and installed it through TestFlight - it crashed immediately. I'm VERY new to this so it took me a long time to figure out how to troubleshoot this but I ended up finding this in the crash logs: Thread 2 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Thread 2 Crashed: 0 libsystem_kernel.dylib 0x2076d8200 __pthread_kill + 8 1 libsystem_pthread.dylib 0x217b3a1ac pthread_kill + 268 2 libsystem_c.dylib 0x1d2111c8c abort + 180 3 libc++abi.dylib 0x217a7ab8c abort_message + 132 4 libc++abi.dylib 0x217a6aa80 demangling_terminate_handler() + 336 5 libobjc.A.dylib 0x1c3e11d3c _objc_terminate() + 144 6 libc++abi.dylib 0x217a79f28 std::__terminate(void (*)()) + 20 7 libc++abi.dylib 0x217a79ec4 std::terminate() + 56 8 libdispatch.dylib 0x1d20adff0 _dispatch_client_callout + 40 9 libdispatch.dylib 0x1d20b5694 _dispatch_lane_serial_drain + 672 10 libdispatch.dylib 0x1d20b61e0 _dispatch_lane_invoke + 384 11 libdispatch.dylib 0x1d20c0e10 _dispatch_workloop_worker_thread + 652 12 libsystem_pthread.dylib 0x217b33df8 _pthread_wqthread + 288 13 libsystem_pthread.dylib 0x217b33b98 start_wqthread + 8 And: Thread 2 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000217a7e0f5 x5: 0x000000016b4c6430 x6: 0x000000000000006e x7: 0xffffffff00000600 x8: 0xb1cfaa93a40be1da x9: 0xb1cfaa92cf4791da x10: 0x0000000000000200 x11: 0x000000000000000b x12: 0x000000000000000b x13: 0x00000000001ff800 x14: 0x00000000000007fb x15: 0x000000008c033819 x16: 0x0000000000000148 x17: 0x000000016b4c7000 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x0000000000001603 x21: 0x000000016b4c70e0 x22: 0x0000000000000000 x23: 0x000000016b4c70e0 x24: 0x0000000000000000 x25: 0x0000000280c888e8 x26: 0x0000000000000114 x27: 0x0000000000000000 x28: 0x0000000283787840 fp: 0x000000016b4c63a0 lr: 0x0000000217b3a1ac sp: 0x000000016b4c6380 pc: 0x00000002076d8200 cpsr: 0x40001000 far: 0x000000021e5abf50 esr: 0x56000080 Address size fault I  spent an entire day searching for causes surrounding these errors - there were references to this but nothing related to what I was doing. I then went back to the basics - literally: npx create-expo-app TestApp eas build:configure eas build --platform ios And loaded this into a simulator (downloaded the ipa file, changed it to a .zip file, transferred the app file to the simulator) and it immediately crashed again. I've used various versions of expo, node, eas cli, etc - all giving me the same results. I tried using ErrorUtils to send an error to my node server but that didn't work (I might have set it up wrong). I'm not sure how to proceed in troubleshooting this. It seems like the basic process of creating an expo app and having it installable in a simulator or an iPhone isn't working for me. I haven't used (nor do I know how to) Xcode much outside of using the simulators. Any help would be VERY MUCH appreciated.

Hi, I've recently experienced a weird crash that only happening on iOS 16 device (iOS 16.xx - 16.3). Here is the stack trace 0 libobjc.A.dylib 0x00000001bc11ae5c _objc_retain_x0 (in libobjc.A.dylib) + 16 1 UIKitCore 0x00000001c5c06a5c -[UIKeyboardTaskQueue promoteDeferredTaskIfIdle] (in UIKitCore) + 72 2 UIKitCore 0x00000001c5c069e8 -[UIKeyboardTaskQueue performDeferredTaskIfIdle] (in UIKitCore) + 28 3 UIKitCore 0x00000001c54039c8 -[UIKeyboardTaskQueue continueExecutionOnMainThread] (in UIKitCore) + 372 4 Foundation 0x00000001bd21484c ___NSThreadPerformPerform (in Foundation) + 260 5 CoreFoundation 0x00000001c2f31f30 ___CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ (in CoreFoundation) + 24 6 CoreFoundation 0x00000001c2f3e308 ___CFRunLoopDoSource0 (in CoreFoundation) + 172 7 CoreFoundation 0x00000001c2ec222c ___CFRunLoopDoSources0 (in CoreFoundation) + 336 8 CoreFoundation 0x00000001c2ed7b88 ___CFRunLoopRun (in CoreFoundation) + 832 9 CoreFoundation 0x00000001c2edcebc _CFRunLoopRunSpecific (in CoreFoundation) + 608 10 GraphicsServices 0x00000001fcf33364 _GSEventRunModal (in GraphicsServices) + 160 11 UIKitCore 0x00000001c53d2868 -[UIApplication _run] (in UIKitCore) + 884 12 UIKitCore 0x00000001c53d24cc _UIApplicationMain (in UIKitCore) + 336 13 News 0x00000001106d5d1c main (in News) (main.m:23) 14 dyld 0x00000001e16fe95c start (in dyld) + 2524

Hi, I have 2 questions: the api for L2CAP is only for BLE or can also work for BR/EDR? (currently didn't manage to connect with BR/EDR) I use https://github.com/bluekitchen/CBL2CAPChannel-Demo on iPhone with le_credit_based_flow_control_mode from blue kitchen and the throughput was very low. I also tried to use L2TEST from Bluez (which uses L2CAP BASIC MODE) but it failed to connect Can anybody help how to increase throughput? The best result I received was 18 kilobyte/second. Thank you

The Problem: I am building an app that uses PayPal for payments, and I set up universal links so that the user gets redirected into the app after the user has confirmed the payment at PayPal's site. Universal links are working in general. But here is what I have discovered: The following scenario works: The app opens the nextActionUrl from PayPal using SFSafariViewController. User has to log in and presses the login button. User presses the confirmation button on the PayPal site. PayPal redirects to the return_url that was provided when creating the payment intent. The browser closes, and the user gets redirected into the app. Now when the user has just recently logged into PayPal then PayPal does not show the login page, instead the user has to only press one button. This scenario fails: The app opens the nextActionUrl from PayPal using SFSafariViewController. User does not have to log in and presses the confirmation button on PayPal site. PayPal redirects to the return_url that was provided when creating the payment intent. The browser opens the website behind the universal link instead of redirecting to the app. This scenario also works: The app opens the nextActionUrl from PayPal using SFSafariViewController. User does not have to log in, but actively logs out. User has to log in and presses the login button. User presses the confirmation button on the PayPal site. PayPal redirects to the return_url that was provided when creating the payment intent. The browser closes, and the user gets redirected into the app. This happens consistently and reproducible. Some additional details: I am developing the App using Flutter I set up the Runner.entitlements as follows: ... <key>com.apple.developer.associated-domains</key> <array> <string>applinks:sub.example.com</string> </array> ... I set up the Info.plist as follows for deep links with different schema: ... <key>CFBundleURLTypes</key> <array> <dict> <key>CFBundleTypeRole</key> <string>Editor</string> <key>CFBundleURLName</key> <string>sub.example.com</string> <key>CFBundleURLSchemes</key> <array> <string>web+example</string> </array> </dict> </array> ... I set up the apple-app-site-association file on the website at https://sub.example.com/.well-known/apple-app-site-association as follows: { "activitycontinuation": {}, "webcredentials": {}, "applinks": { "apps": [], "details": [ { "appID": "XXXXXXXXXX.com.example.example", "paths": [ "/*" ] } ] } } To open the urls from Flutter I am using the package url_launcher and simply call await launchUrl(nextActionUrl) What I've tried and what I've learned: I tried many things, before I discovered this consistent behavior. For example: I connected my device to the mac and opened the console for it in xcode to see how the logs look like when it works and how it looks like when it does not work. I found out that when it works there is a log entry that requests the switch to my App from the SpringBoard-process: [Received trusted open application request for <applicationId> from <FBProcess: ...], but in the cases where it does not work there isn't a rejected request or anything. The SafariViewController does not even seem to try to go the universal link route and instead opens the link as a website directly. For even more logs, I pressed and hold the volume buttons and clicked the lock screen button until a haptic feedback occurred. After that, I extracted the syslogs that were generated from the settings/privacy section via AirDrop on to the mac. I took a look at the swcutil_show.txt file and the universal link is definitely set up correctly there. I also skimmed around in the other logs, but I couldn't find anything helpful. I have inspected the url_launcher package to see how it works for iOS and if there may be something wrong, but I didn't really find a problem. I only discovered that the package is using the SFSafariViewController and after some googling I've read the WKWebView would be more suitable, but it didn't seem to be the problem. I googled a lot and found many problems related with setting up universal links correctly, but no topics about universal links sometimes working and sometimes not. The only thing close I found was that a universal link won't redirect you to your app if you type it into safari directly but if you click it for example from an email. The work-a-round that works... After I confirmed that it consistently works after logging in first, my theory was that it needs at least one navigation between opening the PayPal site in the browser and PayPal redirecting to the universal link. To confirm my theory, I created an intermediate page that redirects the user immediately after the load event to the PayPal site, and I was disappointed. It didn't change anything. Then I thought: Maybe it's the User-Interaction that is needed, and I change the intermediate page to only redirect if the user presses a button. And from there on, redirecting to the App using a universal link always worked. But this isn't a nice solution - at max, this is an ugly work-a-round that may help someone. My question(s) Now I am not sure if this is a bug on Apple's side since I didn't find anything on the web or maybe even something strange on PayPal's side? Am I doing something wrong? Did someone experience the same thing and has a solution? Thank you for your time and hopefully for your input on this!

We have QR-scanner feature implemented on web view (WKWebView). If it's dark we want to light our QR-code using flashlight in iPhone. In general, this feature works, but without flashlight. But have that problems: If we turn on torch then camera preview disappears. If turn off torch then camera preview appears. Do you have any idea why it's so? And how can we sort it out? Thanks

The documentation states that Xcode Cloud comes with support for git lfs (https://developer.apple.com/documentation/xcode/source-code-management-setup) but when I run my unit tests in Xcode Cloud, which have many images which are stored in git lfs, the tests all fail because they don't have the images. How do I get Xcode Cloud to fetch git lfs images? Thanks

Question about App Clips. Is anyone aware of a mechanism whereby an app clip can return the user to the app from which it was invoked when the task is completed? For example, for an app clip invoked via a url in safari, is there a way to programmatically close the app clip after the task is complete and return the user to safari? I imagine this might be technically possible via a deep link if you were to know the custom url scheme for whichever system app invoked the app clip, if system apps do in fact even have custom url schemes that are usable by non-system apps, but that seems like a poor practice. There is lots of documentation and guidance around app clip invocation but none that I can find around the conclusion of the experience. Is the guidance or best practice just to inform the user that they need to manually navigate away from the app clip after the task completes? Surprised to see so little information about this given Apple's emphasis on using app clips to allow the user to complete a discrete task or flow. Thanks in advance for any insights.

Hello everyone, I am having a error when I run a flutter app on iPhone's simulator, this message error is following: Error (Xcode): could not build module 'ObjectiveC' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/usr/include/os/object.h:113:8 Error (Xcode): could not build module 'os_object' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/usr/include/dispatch/dispatch.h:62:9 Error (Xcode): could not build module 'os_object' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/usr/include/os/workgroup_base.h:18:9 Error (Xcode): could not build module 'Dispatch' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:19:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:5:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/Security.framework/Headers/SecBase.h:27:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CFNetwork.framework/Headers/CFNetwork.h:17:9 Error (Xcode): could not build module 'Foundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIKit.h:7:8 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreGraphics.framework/Headers/CGBase.h:11:9 Error (Xcode): could not build module 'CoreGraphics' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreImage.framework/Headers/CoreImageDefines.h:16:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreVideo.framework/Headers/CVBase.h:29:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/IOSurface.framework/Headers/IOSurfaceBase.h:35:9 Error (Xcode): could not build module 'Foundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/OpenGLES.framework/Headers/EAGL.h:7:9 Error (Xcode): could not build module 'Foundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/Metal.framework/Headers/MTLTypes.h:7:8 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/ImageIO.framework/Headers/ImageIOBase.h:15:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreText.framework/Headers/CTFontTraits.h:13:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/QuartzCore.framework/Headers/CABase.h:15:9 Error (Xcode): could not build module 'Foundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/FileProvider.framework/Headers/NSFileProviderDomain.h:7:8 Error (Xcode): could not build module 'Foundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/UserNotifications.framework/Headers/NSString+UserNotifications.h:7:8 Error (Xcode): could not build module 'UIKit' /Users/usuario/Documents/GitHub/valdivia-asociados-app/build/ios/Debug-iphonesimulator/Flutter.framework/Headers/FlutterAppDelegate.h:7:8 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreMedia.framework/Headers/CMBase.h:166:9 Error (Xcode): could not build module 'CoreFoundation' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreAudioTypes.framework/Headers/CoreAudioBaseTypes.h:17:9 Error (Xcode): could not build module 'CoreAudioTypes' /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.2.sdk/System/Library/Frameworks/CoreAudio.framework/Headers/CoreAudioTypes.h:3:9 Error (Xcode): could not build module 'Flutter' /Users/usuario/Documents/GitHub/valdivia-asociados-app/ios/Runner/GeneratedPluginRegistrant.h:9:8 Error (Xcode): failed to emit precompiled header '/Users/usuario/Library/Developer/Xcode/DerivedData/Runner-arkjnantpvustwgwgpubahjupcap/Build/Intermediates.noindex/PrecompiledHeaders/Runner-Bridging-Header-swift_2SDB0BH26RSRB-clang_2PKV74KGMIP1K.pch' for bridging header '/Users/usuario/Documents/GitHub/valdivia-asociados-app/ios/Runner/Runner-Bridging-Header.h' Could not build the application for the simulator. Error launching application on iPhone 14 Pro.

Hi I am receiving this error in crashlytics and I am not sure what is going on. Based from the crashlytics report, it is only happening from iOS 16.2 and above. Any tips and hints on this problem would be great. Here is the bug report. Fatal Exception: NSInternalInconsistencyException 0 CoreFoundation         0x9e48 __exceptionPreprocess 1 libobjc.A.dylib        0x178d8 objc_exception_throw 2 Foundation           0x545a88 -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] 3 UIKitCore           0x6a2724 __UIKIT_DID_NOT_RECEIVE_A_REMOTE_CACONTEXT_FROM_COREANIMATION_INDICATING_A_POSSIBLE_BACKBOARDD_CRASH 4 UIKitCore           0x5260ec __UIKIT_IS_REQUESTING_A_CACONTEXT_FROM_COREANIMATION 5 UIKitCore           0x347ef0 +[_UIContextBinder createContextForBindable:withSubstrate:] 6 UIKitCore           0x347c64 -[_UIContextBinder _contextForBindable:] 7 UIKitCore           0x347b40 -[_UIContextBinder attachBindable:] 8 UIKitCore           0x13ab50 -[UIWindowScene _windowUpdatedVisibility:] 9 UIKitCore           0x206b80 -[UIWindow _updateLayerOrderingAndSetLayerHidden:actionBlock:] 10 UIKitCore           0x20643c -[UIWindow _setHidden:forced:] 11 UIKitCore           0x34608c -[UITextEffectsWindow _commonInitWithOptions:] 12 UIKitCore           0x345fb8 -[UITextEffectsWindow(UIObjectsForPerCanvas) _initWithCanvas:options:] 13 UIKitCore           0x206908 +[_UIObjectPerCanvas objectOfClass:forCanvas:withOptions:createIfNecessary:] 14 UIKitCore           0xf1d6c4 +[UITextEffectsWindow _sharedTextEffectsWindowforWindowScene:allowHosted:forViewService:matchesStatusBarOrientationOnAccess:shouldCreateIfNecessary:] 15 UIKitCore           0xf1d844 +[UITextEffectsWindow sharedTextEffectsWindowForWindowScene:forViewService:] 16 UIKitCore           0x8e39e4 -[UIKeyboardSceneDelegate containerWindowForViewService:] 17 UIKitCore           0x235094 -[UITextSelectionView showInitialCaret] 18 UIKitCore           0x234120 -[UITextSelectionView updateSelectionRects] 19 UIKitCore           0x233754 -[UITextSelectionView updateSelectionRectsIfNeeded] 20 UIKitCore           0x2336e4 __51-[UITextSelectionView deferredUpdateSelectionRects]_block_invoke 21 CoreFoundation         0x91d40 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ 22 CoreFoundation         0x1a290 __CFRunLoopDoObservers 23 CoreFoundation         0x7bb70 __CFRunLoopRun 24 CoreFoundation         0x80ec0 CFRunLoopRunSpecific 25 GraphicsServices        0x1368 GSEventRunModal 26 UIKitCore           0x3a186c -[UIApplication _run] 27 UIKitCore           0x3a14d0 UIApplicationMain 28 MyApp           0x6274 main + 32 (AppDelegate.swift:32) 29 ???              0x1aad76960 (Missing)

I have an iOS app that I would like to execute on mac os with the "Designed for iPad" feature (not catalyst). I would like to know if there is a way to have specific behaviour on macOS ? I have tested all the UIDevice information but it all comes with iPad information.

In a SwiftUI app on iPhone when the device is put to sleep by pressing the power button, while the app is presenting a .sheet, waking the device will result in the touch layout to not match the UI layout. See attached project to reproduce the issue. This happens with Xcode 14.2, targeting iOS 16.0. Steps to reproduce (assuming the app has been built an running on a real device, xcode project linked at the bottom): Tap the “Hello World” button. This opens a plain sheet with a fully green color content Push the device’s power button to put it to sleep Push the device’s power button again to wake the device Optionally unlock the device if needed Dismiss the opened green sheet (the app should still be open and displaying the sheet after waking the device) Try to tap the “Hello World” button again. Observed behavior: the area required to tap to activate the button no longer matches the UI and you have to tap below the button to activate it. Desired behavior: after waking the device and dismissing the sheet, the touch and ui layout should still be correct. Demonstration XCode project

Hi, we are facing on a strange behaviour since iOS 16. In a registration view, we have two text field to insert password (password textfield and confirm password text field). Suggest strong password is abilitate (from iCloud... password & keychain). When user tap on password text field, can choose between strong password or text custom password. If user choose custom password, can text his own password as usually. But when he tap the second text field (confirm password) Apple fill in automatic both text field, cleaning the first text field... So user entry in a loop where he text password and when go next, previous textfield be cleaned and both text field filled with a new suggestion. Searching on the web we don't find any solution to it. Also because we try just to set text fields as .password or .newPassword. But this behaviour is always the same. Maybe is it a bug of iOS 16? How we can allow user to chose a custom password if the system fill always in automatic the password text fields, every time he tap on them?

Hi, I'm developing an app that reads the NFC tags. So far so good, everything worked as expected, the app reads the passports and the IDs, until we encountered the french ID issued after March 2021. My app has the following entitlements: <dict> <key>com.apple.developer.nfc.readersession.formats</key> <array> <string>TAG</string> </array> </dict> And this additional entries in the .plist: <key>NFCReaderUsageDescription</key> <string>NFC usage to scan ID chip</string> ... <key>com.apple.developer.nfc.readersession.iso7816.select-identifiers</key> <array> <string>A0000002471001</string> <string>A0000002472001</string> <string>00000000000000</string> </array> According to an article which I cannot link on this forum because the domain is not permitted, iOS started supporting this specific ID from version 16. When I look at the docs, I can see the .pace polling mode was added. I tried specifying this additional polling mode in my app like so: var pollingOptions: NFCTagReaderSession.PollingOption = [.iso14443] if #available(iOS 16, *) { pollingOptions.insert(.pace) } self.session = NFCTagReaderSession(pollingOption: pollingOptions, delegate: self, queue: nil) But when I try to start the session it gets instantly invalidated with this message: Missing required entitlement. I'm pretty confident the message is misleading and something else is missing somewhere, my bet would be on the .plist entry com.apple.developer.nfc.readersession.iso7816.select-identifiers missing one of the cryptic numbers, but I have no idea where this can be taken from. How do I implement this .pace polling mode, can someone give me some guidance?

When I create a ProcessInfo instance using ProcessInfo(), it seems to mess up the internally created singleton instance. Because afterwards, when I use ProcessInfo.processInfo to retrieve the low power mode state of the device, it returns the same result (the mode when ProcessInfo() was called) regardless of what the actual mode is at that moment. I tested this on 15.6.1.

My IAP is working fine in Sandbox Environment and Test Flight. But the problem is, its not working in Production Environment (App Store). Even the price information is not returned back from App Store in production. I also sent this query to Apple Support. But didn't get any response despite waiting more than 48 hours.

Hello, I've upgraded from xcode 14.2 to xcode 14.3 beta, and now I can't archive anymore for Any iOS Device (arm64) with the following error : PhaseScriptExecution [CP]\ Embed\ Pods\ Frameworks mkdir -p /Users/max/Library/Developer/Xcode/DerivedData/Max-dmwafkgdrzqavzcmbdjbjgmmuxby/Build/Intermediates.noindex/ArchiveIntermediates/Release_preprod/BuildProductsPath/Release_preprod-iphoneos/MaxApp.app/Frameworks Symlinked... rsync --delete -av --filter P .*.?????? --links --filter "- CVS/" --filter "- .svn/" --filter "- .git/" --filter "- .hg/" --filter "- Headers" --filter "- PrivateHeaders" --filter "- Modules" "../../../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/ActionSheetPicker_3_0.framework" "/Users/max/Library/Developer/Xcode/DerivedData/Max-dmwafkgdrzqavzcmbdjbjgmmuxby/Build/Intermediates.noindex/ArchiveIntermediates/Release_preprod/InstallationBuildProductsLocation/Applications/MaxApp.app/Frameworks" building file list ... rsync: link_stat "/Users/max/Workspace/MaxApp/../../../IntermediateBuildFilesPath/UninstalledProducts/iphoneos/ActionSheetPicker_3_0.framework" failed: No such file or directory (2) done sent 29 bytes received 20 bytes 98.00 bytes/sec total size is 0 speedup is 0.00 rsync error: some files could not be transferred (code 23) at /AppleInternal/Library/BuildRoots/9e200cfa-7d96-11ed-886f-a23c4f261b56/Library/Caches/com.apple.xbs/Sources/rsync/rsync/main.c(996) [sender=2.6.9] Command PhaseScriptExecution failed with a nonzero exit code Any idea why it works fine with xCode 14.2 and not with xCode 14.3 beta please ? I tryed to delete the [CP] Embed Pods Frameworks script, but it has re-created it and get the same issue. I tryed to build and debug in a simulator, and it works fine. I tryed to delete "EXCLUDED_ARCHS[sdk=iphonesimulator*]" = arm64; in the .pbxproj file

The following crash is happening in iOS 16 when we call snapshot.reconfigureItems(ids). We get the ids to reload by calling the CollectionView's indexPathsForVisibleItems, where the idea is to refresh the currently visible items. #0 (null) in __exceptionPreprocess () #1 (null) in objc_exception_throw () #2 (null) in -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] () #3 (null) in -[__UIDiffableDataSourceSnapshot _validateReloadUpdateThrowingIfNeeded:] () #4 (null) in -[__UIDiffableDataSourceSnapshot _commitUpdateAtomic:] () #5 (null) in -[__UIDiffableDataSourceSnapshot reconfigureItemsWithIdentifiers:] () #6 (null) in NSDiffableDataSourceSnapshot.deleteItems(_:) () We are also seeing a slight variation of the same crash: #0 (null) in __exceptionPreprocess () #1 (null) in objc_exception_throw () #2 (null) in -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] () #3 (null) in -[_UIDiffableDataSourceUpdate initWithIdentifiers:sectionIdentifiers:action:desinationIdentifier:relativePosition:destinationIsSection:] () #4 (null) in -[_UIDiffableDataSourceUpdate initWithReconfiguredItemIdentifiers:] () #5 (null) in -[__UIDiffableDataSourceSnapshot reconfigureItemsWithIdentifiers:] () #6 (null) in NSDiffableDataSourceSnapshot.deleteItems(_:) () These two crashes taken together currently account for 50% of all our app's crashes. According to the data we have, it is specific to iOS 16. Some questions: Is there anything we can do to mitigate this crash? Can we safely call snapshot.reloadItems(ids) instead? If so, how much of a performance hit would we expect to get?