Xcode 12.2 Beta Release update documentation

Xcode 12.2 Beta Release Notes

Update your application to use new features, and test your application against API changes.


Update cloud map

wordcloud.png


Overview

Xcode 12.2 beta includes SDK for iOS 14.2, iPadOS 14.2, tvOS 14.2, watchOS 7.1 and macOS Big Sur 11. Xcode 12.2 beta version supports debugging on devices with iOS 9 and later, tvOS 9 and later, and watchOS 2 and later. . Xcode 12.2 beta requires a Mac with an Apple chip running macOS Big Sur 11 or higher, or an Intel-based Mac running macOS Catalina 10.15.4 or higher.

general

new function

  • When introducing the iPad app to macOS, you can now enable the "Optimized interface for Mac" target setting to use native Mac controls and resolution. (56344940)

  • Xcode's run target menu now displays the Any Mac target of the Mac solution. This is a new build target that can build each target for all supported architectures in the scheme, regardless of the native architecture of the local Mac. (62736613)

  • Xcode now supports iOS, tvOS and watchOS development on Macs with Apple chips. (64317985, 65077539, 65701094)

Known issues

  • If you use an iOS SDK that is newer than the version supported by macOS to build or run iOS apps with macOS targets, it may fail. (68261281, 68714781, 68948002)

    The failure may occur in one of the following ways:

    • The app crashes on launch

    • Xcode displays an alert stating "The operation could not be completed. (OSStatus error -10825.)"

    • Xcode displays a warning saying "Unable to install"

    Solution : Change the iOS deployment target of the iOS application to a version supported by the macOS version you are using, or upgrade to a macOS version that supports the iOS deployment target configured in the project. When running applications built with Mac Catalyst, macOS 11.0 beta supports the iOS 14.0 deployment target, while macOS 10.15.6 supports the iOS 13.6 deployment target.

Apple Clang Compiler

Known issues

  • In conjunction with Apple’s Mac silicon, stripand may corrupt the linker’s arm64 Mach-O file generated special code signatures. (51911417)install_name_tool``vtool

    Solution : Run the following command to repair the files touched by these tools:

    codesign -s - --preserve-metadata=identifier,entitlements,flags,runtime -f 
    

Build system

solved problem

  • xcodebuildNo longer incorrectly double-escaped output. (63554669)xcodebuild -showBuildSettings -json

Core ML

solved problem

  • Now, when you click "Listen", the "Preview" tab of the "Sound" classifier model of the Core ML editor will display the classification results. In addition, when adding an audio file, clicking the "Play" button will update the timeline when the file is playing. (67515312)

equipment

solved problem

  • When adding app clips to a paired iOS app, you can debug the WatchKit app even if the iOS app is not installed. (65784374) (FB8065876)

Known issues

  • rvictl Hang on macOS 11. (65205535)

Interface builder

new function

  • Added support for inline and compact styles. (65085323) (FB7847821)UIDatePicker

solved problem

  • Fixed the problem of clipping the search field on the navigation bar when dragging from the object library for the first time. For the existing navigation controller in the storyboard, you can correct the cropping by selecting the navigation bar in the controller and enable "Size Inspector"> "Safe Area Relative Margin". (66566017) (FB8269384)

  • Fixed an issue that may cause it to lose the "source list" style when deployed to a macOS version earlier than macOS 11. (67700315) (FB8525478)NSTableView

organizer

solved problem

  • Streamlining "all compatible device variants" no longer causes the export of WatchOS apps for Ad Hoc or Development distribution to fail. (66637482)

Known issues

  • When you start the manager for the first time, the sidebar may change to a horizontal scrolling state, and the selected item may not be highlighted. (67498422)

Playground

Known issues

  • When displaying live view on a Mac with an Apple chip, the playground may crash. (68930351)

trailer

new function

  • The new "Embed..." option in the operation menu allows you to embed the View container specified by the user. (51152198)

  • The action menu now contains the "Embed ZStack" option. (56989502)

  • Now, the "Editor" menu includes "Create Preview" to create, and "Create Library Item" to create. (67110969)PreviewProviderLibraryContentProvider

solved problem

  • Fixed an issue that prevented the preview from loading items whose names or symbols in the items were non-ASCII characters. (57260388) (FB7451792)

  • The preview correctly displays interpolated strings, including localized strings. (64278576)

  • Fixed an issue that prevented the preview from loading code containing multiple lines of string text. (65735599)

  • On Intel-based Macs, previews of iOS, watchOS, or tvOS projects that depend on libraries without arm64 slice can now be loaded. (65890022)

  • Now, the preview canvas will automatically show and hide based on whether it exists in the file being edited. (67083504, 67693254)PreviewProvider

  • When the preview fails to start due to the crash of the underlying application, for example, when the application is not available, the canvas will display the error details. (67955924)EnvironmentObject

Known issues

  • Xcode does not provide previews of macOS widget extensions. (57990060)

  • Using the device name "Mac Catalyst" in the modifier may cause the preview to fail. (65305155)PreviewDevice

    Solution : Delete the modifier and switch to the "My Mac" run target.previewDevice

Sign and distribute

new function

  • Xcode can now use Apple chips to sign iOS applications for development or distribution to Macs. You must register your Mac with Apple Chip on the Developer website to run Mac, iPhone or iPad applications. Registration requires the hardware identifier of the Mac, which can be found in the Xcode error message or in the "Hardware"> "Supply UDID" field of the System Information application. After registering your Mac, you can use Xcode's auto-signed or manually signed apps to run on the device. (54476962, 65752056)

  • Xcode can sign and configure an archived iOS application to run on a Mac with an Apple chip. Find the archive in the manager window, click "Distribute Application", select "Temporary" or "Development", select a distribution option, select "Automatically manage signatures", and then proceed with the rest of the distribution assistant to create an IPA. After creating the IPA, you can transfer it to the Mac through the Apple chip, and then double-click to install it. During the first launch of the application, you will be prompted to open the "Security and Privacy" preference pane to enable the application. To view the launch button in the preference pane, make sure that your Mac is configured to only allow apps from the App Store and designated developers. (68513041, 68528315).

solved problem

  • When using the Ad Hoc or Development method to distribute the iOS archive, Xcode will verify whether the configuration file generated by the automatic signature contains a Mac with an Apple chip. (66803918)

  • Xcode automatic signature includes your registered Mac with Apple chip in the configuration file when exporting the file. (66857321)

Known issues

  • Applications built with Mac Catalyst and signed to run locally on macOS may not run on Mac (Rosetta) targets. (64421496)

Emulator

new function

  • The simulated watchOS 7 device supports 64-bit processes. To verify that the watchOS project is 64-bit pure in Simulator, make sure ARCHSto set it to the default value. (54654060, 66352876)

    note

    The project must be 64-bit clean to run in Simulator on a Mac with an Apple chip, which does not support 32-bit code.

Known issues

  • Even if Xcode Preferences allows you to download these earlier runtimes, iOS 13, tvOS 13, and watchOS 6 or earlier simulators will not run on the Developer Transition Kit. Future Macs with Apple chips will support some older iOS and tvOS simulators. (66115743) (FB8157217)

  • SwiftUI projects using StoreKit cannot be built on simulated watchOS devices. (68931021, 68935233)

    Solution : Build and run on the device.

Deprecated

  • The emulator of watchOS 6 or earlier requires a 32-bit process, which is not supported by Macs with Apple chips. (66352760)

StoreKit

solved problem

  • Fixed a crash that may occur when selecting "Subscription Options" in the StoreKit transaction manager. (68354368)

rapid

Known issues

  • When the body of the function builder contains an empty switch statement, the compiler may crash. This problem may also cause SourceKit to crash when the switch statement is entered in the main body of the SwiftUI view. (65983237) (FB8111944)

Swift Pack

Known issues

  • When you are trying to build a universal binary, the Swift package may not respect the build settings of the "build only active architecture" project. (64344067)

    Solution : Use "any Mac", "any iOS device (arm64)", "any watchOS device" or "any tvOS device" target location to build all applicable devices.

testing

Known issues

  • Xcode cannot run UI tests for iOS apps on Apple chips. If the activity scheme or test plan contains both unit testing and UI testing, Xcode will skip UI testing and record a message in the test activity log indicating that UI testing has been skipped. (60059698)

  • Xcode will not run iOS application tests in parallel on Apple chips. Instead, the tests are run sequentially. (60514529)

  • If the "Host Application" of the test target is set to "None", the iOS unit test cannot be launched on the Apple chip. (65309328)

    Solution : Set the host application as the iOS application target.

Guess you like

Origin blog.csdn.net/iCloudEnd/article/details/108684117