I build a FAT development framework for distribution which needs to contain arm and intel slices. Forcing it to build just active architecture is not a solution for me. I have been playing with using external myCodeSettings.xcconfig file containing lines like the following: EXCLUDE_ARCHS_FOR_Release_iphoneos=i386 x86_64 EXCLUDE_ARCHS_FOR_Release_iphonesimulator=arm64 arm7s armv7 EXCLUDE_ARCHS= $(__EXCLUDE_ARCHS_FOR_$(CONF)_$(PLATFORM_NAME)) and associate the myCodeSettings.xcconfig in General project settings tab on specific targets that need to build. Appeared to work, by replacing the subsequent EXCLUDEARCHS dynamically based on what you are trying to build. There was one build failure so I was looking into applying similiar technique for VALIDARCHS and ARCHS settings. Anyone feel they have been successful and post their solution?

I don't believe you can remove all architectures from VALIDARCHS or ARCHS or the build will be successful but Xcode would not compile nor link anything for the framework or library. The log should contain a message indicating no archs were specified. Same is true if you exclude all architectures within EXCLUDEARCHS .

For a general short term solution to this issue, the exclusion of arm64 arch needs to be specifically tied to iOS Simulator platform build. If solution is not tied to iOS Simulator platform, you are telling Xcode to never build for the arm64 arch. This solution doesn't work for me since I need to distribute FAT framework with all the iOS archs and all the iOS Simulator archs. The newer Xcode 12 is treating arm64 as an iOS Simulator architecture as well as a legacy iOS architecture probably because MacOS Big Sur 11 running on an Arm64 based Mac will be running the iOS Simulator on arm64... But the Xcode folks didn't appear to think thru the affects. Xcode 12 UX needs to be able to differentiate arm64 iOS Simulator from arm64 iOS in a better way. The generated binary need to include extra metadata so linker can tell choose the correct arch within a FAT library framework without displaying error because it chose unwisely.

Applying the following myProjectSettings.xcconfig settings to the Project Configurations has fixed the issue in my builds and still allows additional .xcconfig settings to be applied to individual targets within the Project. This explicitly sets the architectures for the iphoneos and iphonesimulator Xcode settings that are associated with ARCHS , VALIDARCHS , and EXCLUDEDARCHS. EXCLUDED_ARCHS[sdk=iphoneos*] = x86_64 EXCLUDED_ARCHS[sdk=iphonesimulator*] = arm64 ARCHS[sdk=iphoneos*] = arm64 ARCHS[sdk=iphonesimulator*] = x86_64 VALID_ARCHS[sdk=iphoneos*] = arm64 VALID_ARCHS[sdk=iphonesimulator*] = x86_64 NOTE: More architectures (e.g. armv7, armv7s, arm64e, etc) could be added to each of these settings for your build environment. My specific build intel based macOS environment does not include additional architecture because some third party binary frameworks don't include extra architectures.

Upgraded my iPhone XR from iOS 13 to iOS 14. I am. seeing same issue with both Safari on both WiFi and Cellular connections. Running a DNS tool query from iPhone resolve ***.google.com host name to a correct IP address so this seems specific to Safari. Following inspector log entries shows Safari internal Network Reachabililty or DNS failure on ***.google.com website (NOTE: the hostname ***.google.com appears in reply because www. prefix is not allowed in this reply ) : Timestamp Type Process Subsystem Category Thread Message 00:28.988.415 Debug SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 fetching object for key=SBScenes bundleID=com.apple.mobilesafari (synchronously) 00:28.988.523 Debug SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 checking for prefetched object for key=SBScenes bundleID=com.apple.mobilesafari 00:28.988.669 Debug MobileSafari (1001) com.apple.SystemConfiguration SCNetworkReachability MobileSafari  0x3d44a [0x109625670] create w/name <SCNetworkReachability 0x109625670 [0x203068660]> {name = ***.google.com} 00:28.988.713 Debug SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 found object n/a 00:28.988.714 Debug MobileSafari (1001) com.apple.SystemConfiguration SCNetworkReachability MobileSafari  0x3d44a [0x109625670] scheduled 00:28.988.892 Debug SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 found prefetched object: n/a 00:28.988.971 Default MobileSafari (1001) com.apple.network path MobileSafari  0x3d44a nwpathevaluatorstart [16 Bytes Hostname#e6698e47:0 generic, multipath service: 3, indefinite] path: satisfied (Path is satisfied), interface: en0, ipv4, dns 00:28.988.996 Info MobileSafari (1001) com.apple.network MobileSafari  0x3d453 nwresolvercreatednsgetaddrinfolocked Starting host resolution Hostname#e6698e47:0, flags c000d000 proto 0 using hostname: <NO HOSTNAME> 00:28.989.021 Info SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 setting object for key=SBScenes bundleID=com.apple.mobilesafari object=n/a 00:28.989.026 Error MobileSafari (1001) com.apple.mobilesafari PageLoading MobileSafari  0x3d44a Displaying webpage loading error to user: Error Domain=NSURLErrorDomain Code=-1004 "(null)", networkTaskDescription: LocalDataTask <4B48C5ED-E3D8-4006-B8D3-6B25B05E4205>.<3>. 00:28.989.120 Debug MobileSafari (1001) com.apple.CFBundle strings MobileSafari  0x3d44a Bundle: n/a, key: Safari cannot open the page because it could not connect to the server., value: localized string not found, table: Localizable, localizationName: , result: Safari cannot open the page because it could not connect to the server. 00:28.989.154 Debug SpringBoard (59) com.apple.FrontBoard AppDataStore SpringBoard  0x3c4 updating cache key=SBScenes bundleID=com.apple.mobilesafari object=n/a 00:28.989.164 Default mDNSResponder (136) com.apple.mDNSResponder Default mDNSResponder  0x3d4df [R319,573] getaddrinfo start -- flags: 0xc000d000, ifindex: 0, protocols: 0, hostname: n/a, options: {}, client pid: 1,001 (MobileSafari)

For Chrome, the initial google webpage is displayed but when I try to search for anything, I get an error connection screen displayed.