Universal Apps

RSS for tag

A single Universal app includes native binaries that run on Intel-based Macs and Apple Silicon Macs.

Posts under Universal Apps tag

102 Posts

Post

Replies

Boosts

Views

Activity

Can I submit 32-bit (Universal) apps to iOS App Store
I just saw a developer claim that the App Store will no longer accept 32-bit builds. Which presumably means we won’t be able to submit universal. I had wanted to continue to support our few remaining iPad 2 customers, but it sounds like that won’t be possible. I haven’t had any luck finding any official statement about this. I’ve been using Xcode 13.1 and it still lets me target iOS 9…
1
0
1.4k
Jan ’22
Could not find module for target 'arm64-apple-macos'; found: x86_64, x86_64-apple-macos
I have an XCode Workspace that builds a product as a universal binary for Intel and Apple Silicon. On an Intel-based machine, I am attempting to import a Swift Package dependency by accessing a private git repository. When I attempt to import my dependency into my code and build, I'm getting the following error: Could not find module '<swift package name>' for target 'arm64-apple-macos'; found: x86_64, x86_64-apple-macos The project has Standard Architectures set for the ARCHS build setting and ONLY_ACTIVE_ARCH = NO. When I switch ONLY_ACTIVE_ARCH = YES, it builds fine. Is there a way to instruct the compiler to build the swift package dependency as universal and resolve this issue?
1
0
3.1k
Dec ’21
(macOS) dlopen universal dylib leads to "slice is not page aligned"
Built using Xcode Version 13.1 (13A1030d) on macOS Monterey 12.0.1. The dylib was built in a release configuration with architectures set to $(ARCHS_STANDARD). This builds a FAT binary with x86_64 and arm64, as expected. However, when I dlopen it with RTLD_NOW | RTLD_GLOBAL, it fails and dlerror reports "slice is not page aligned" twice, and a message saying that it is looking for x86_64h but only finds x86_64,arm64 is reported. Not sure what the root cause is, but certainly the slice not being page aligned is causing issues. The question may therefore be: how can I ensure the dylib generated as a FAT binary has its slices aligned in Xcode 13?
1
0
1.6k
Dec ’21
Command PhaseScriptExecution failed with a nonzero exit code
Since a few days I can't compile my flutter project anymore. I tried several solutions found on the internet but none of them worked for me. I am using a MacBook Pro M1 with XCODE version 12.5.1 (12E507). You can find the output of the error I'm experiencing in the attached copy. Thank you for any useful help that can save me from this situation. Error message: 👇🏾  /bin/sh -c /Users/donarias/Library/Developer/Xcode/DerivedData/Runner-fdbfjdxtqbyzbqgfhspjraxpjmdc/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Script-9740EEB61CF901F6004384FC.sh ../../../../../.pub-cache/hosted/pub.dartlang.org/flutter_datetime_picker-1.5.1/lib/flutter_datetime_picker.dart:311:32: Warning: Operand of null-aware operation '??' has type 'Color' which excludes null.  - 'Color' is from 'dart:ui'.                   color: theme.backgroundColor ?? Colors.white,                                ^ ../../../../../.pub-cache/hosted/pub.dartlang.org/get-4.3.4/lib/get_navigation/src/root/get_material_app.dart:297:15: Error: No named parameter with the name 'scrollBehavior'.               scrollBehavior: scrollBehavior,               ^^^^^^^^^^^^^^ ../../../../flutter/packages/flutter/lib/src/material/app.dart:217:9: Context: Found this candidate, but the arguments don't match.   const MaterialApp.router({         ^^^^^^^^^^^^^^^^^^ ../../../../../.pub-cache/hosted/pub.dartlang.org/get-4.3.4/lib/get_navigation/src/root/get_material_app.dart:340:15: Error: No named parameter with the name 'scrollBehavior'.               scrollBehavior: scrollBehavior,               ^^^^^^^^^^^^^^ ../../../../flutter/packages/flutter/lib/src/material/app.dart:167:9: Context: Found this candidate, but the arguments don't match.   const MaterialApp({         ^^^^^^^^^^^ Command PhaseScriptExecution failed with a nonzero exit code
2
0
1.8k
Dec ’21
My app is damaged and can't be opened when porting to M1 ?
I have porting my existing application to support native M1, there a a lot of framework and library that I have already build for both platform. The strange result is when I archive the app on Intel machine. The binary work on Intel platform well. When I archive my application on M1 machine, the app can work on M1 well. But when I try to run app that build on M1 on Intel Machine, then I got the message said my app is damaged and can't be opened. The same situation got for build in Intel platform one. I try "lipo -archs" command on my app and I did get "x86_64 arm64" as result, so my app should already a universal app I guess. Does any body know are there some way to check what happened on my application? Thanks, any opinion will be appreciated ! Eric
3
0
4.5k
Dec ’21
ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1
Hi, I'm facing the same error! You example is Passed! But it doesn't work when I compile NCURSES. It seems that there are something wrong with my ld % ld -v @(#)PROGRAM:ld  PROJECT:ld64-711 BUILD 18:11:19 Aug  3 2021 configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em LTO support using: LLVM version 13.0.0, (clang-1300.0.29.3) (static support for 27, runtime is 27) TAPI support using: Apple TAPI version 13.0.0 (tapi-1300.0.6.5) % clang -v Apple clang version 13.0.0 (clang-1300.0.29.3) Target: arm64-apple-darwin21.1.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin Here are the configuration and error. ** Configuration summary for NCURSES 6.3 20211021:        extended funcs: yes        xterm terminfo: xterm-new         bin directory: /usr/local/bin         lib directory: /usr/local/lib     include directory: /usr/local/include/ncurses         man directory: /usr/local/share/man    terminfo directory: /usr/local/share/terminfo ** Include-directory is not in a standard location``` gcc ../objects/tic.o ../objects/dump_entry.o ../objects/tparm_type.o ../objects/transform.o -L../lib -Wl,-search_paths_first -DHAVE_CONFIG_H -I../progs -I. -I../include -D_DARWIN_C_SOURCE -DNDEBUG -O2 -Qunused-arguments -Wno-error=implicit-function-declaration -no-cpp-precomp  -DNCURSES_STATIC -L../lib  -lncurses -lncurses    -o tic ld: warning: ignoring file ../lib/libncurses.a, building for macOS-arm64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 ) Undefined symbols for architecture arm64:   "__nc_boolcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_boolfnames", referenced from:       _dump_init in dump_entry.o   "__nc_boolnames", referenced from:       _dump_init in dump_entry.o   "__nc_capcmp", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o   "__nc_check_termtype2", referenced from:       _main in tic.o   "__nc_curr_col", referenced from:       _main in tic.o   "__nc_curr_line", referenced from:       _main in tic.o   "__nc_disable_period", referenced from:       _main in tic.o   "__nc_doalloc", referenced from:       _main in tic.o       _fmt_entry in dump_entry.o       _strcpy_DYN in dump_entry.o       _fmt_complex in dump_entry.o       _strncpy_DYN in dump_entry.o   "__nc_find_entry", referenced from:       _check_user_capability_type in tic.o       _nametrans in dump_entry.o   "__nc_find_user_entry", referenced from:       _check_termtype in tic.o       _check_user_capability_type in tic.o   "__nc_first_name", referenced from:       _main in tic.o       _check_termtype in tic.o       _fmt_complex in dump_entry.o       _dump_entry in dump_entry.o   "__nc_get_hash_table", referenced from:       _check_user_capability_type in tic.o       _nametrans in dump_entry.o   "__nc_head", referenced from:       _main in tic.o   "__nc_home_terminfo", referenced from:       _show_databases in tic.o   "__nc_infotocap", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o   "__nc_name_match", referenced from:       _main in tic.o   "__nc_numcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_numfnames", referenced from:       _dump_init in dump_entry.o   "__nc_numnames", referenced from:       _dump_init in dump_entry.o   "__nc_pathlast", referenced from:       _valid_db_path in tic.o   "__nc_read_entry_source", referenced from:       _main in tic.o   "__nc_reset_tparm", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o   "__nc_resolve_uses2", referenced from:       _main in tic.o   "__nc_rootname", referenced from:       _main in tic.o   "__nc_set_source", referenced from:       _main in tic.o   "__nc_set_type", referenced from:       _main in tic.o   "__nc_set_writedir", referenced from:       _main in tic.o   "__nc_strcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_strfnames", referenced from:       _dump_init in dump_entry.o   "__nc_strict_bsd", referenced from:       _main in tic.o   "__nc_strnames", referenced from:       _check_termtype in tic.o      _dump_init in dump_entry.o       _dump_entry in dump_entry.o   "__nc_syntax", referenced from:       _check_termtype in tic.o   "__nc_tail", referenced from:       _main in tic.o   "__nc_tic_dir", referenced from:   _main in tic.o       _show_databases in tic.o   "__nc_tic_expand", referenced from:       _check_ansi_cursor in tic.o       _fmt_entry in dump_entry.o   "__nc_tic_written", referenced from:       _main in tic.o   "__nc_tinfo_fkeysf", referenced from:       _check_termtype in tic.o   "__nc_tiparm", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o       _check_1_infotocap in tic.o       _same_color in tic.o   "__nc_tparm_analyze", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o   "__nc_tparm_err", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o   "__nc_tracing", referenced from:       _main in tic.o   "__nc_trim_sgr0", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o   "__nc_user_definable", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o       _compare_entry in dump_entry.o   "__nc_visbuf", referenced from:       _similar_sgr in tic.o   "__nc_visbuf2", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o       _similar_sgr in tic.o   "__nc_warning", referenced from:       _check_termtype in tic.o       _check_user_capability_type in tic.o       _check_sgr in tic.o       _check_sgr_param in tic.o       _check_1_infotocap in tic.o       _check_noaddress in tic.o       _check_ansi_cursor in tic.o       ...   "__nc_write_entry", referenced from:       _main in tic.o   "__nc_write_object", referenced from:       _dump_entry in dump_entry.o   "_curses_version", referenced from:       _main in tic.o   "_keyname", referenced from:       _check_termtype in tic.o   "_tgoto", referenced from:       _check_sgr_param in tic.o   "_tigetflag", referenced from:       _check_termtype in tic.o   "_tigetstr", referenced from:       _check_termtype in tic.o   "_tparm", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o      (maybe you meant: _tparm_type, _guess_tparm_type )   "_use_extended_names", referenced from:       _main in tic.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[1]: *** [tic] Error 1 make: *** [all] Error 2
0
0
1.4k
Dec ’21
Universal App Not Resizable as Expected
I have an app that started out as an iPhone/iPad app and I added support for Mac. According to videos and documentation I've read online, one of the things you get for free is the ability to resize screens. It does, in fact, work that way when I build to MacOS from Xcode. However, when I upload the build to Testflight and run that version of the app, installed by Testflight, it doesn't resize. I should qualify that. I can drag a corner to switch it between portrait and landscape, but the size remains the same. I'm not sure what to look for, especially since resizing works when I build from Xcode. Any suggestions? I'm using SideMenu as the navigation controller for the app. The main view controller that instantiates Side Menu adds four view controllers as children. One of those is a portrait-only view controller. Since it works as expected when I build from Xcode, anything I try will have to be archived and uploaded to Testflight. So any suggestions of likely things to try would be greatly appreciated. I am NOT doing anything with windowScene size restrictions.
1
0
922
Nov ’21
What can be done to execute Intel-based Mac executables on an M1 Mac running Big Sur 11.6?
Rosetta and Rosetta 2 do not appear to be available.  All attempts to execute the Intel code failed with the "zsh: bad CPU type in executable" message.  Since I wasn't prompted to install Rosetta or Rosetta 2, I executed the following, % softwareupdate --install-rosetta which responded with I have read and agree to the terms of the software license agreement. A list of Apple SLAs may be found here: http://www.apple.com/legal/sla/ Type A and press return to agree: So, I typed the A and the return.  The result was 2021-10-03 04:31:49.497 softwareupdate[1775:240889] Package Authoring Error: 071-97390: Package reference com.apple.pkg.RosettaUpdateAuto is missing install KBytes attribute Install of Rosetta 2 finished successfully Although the message ended with "finished successfully", note the error disclosed. Furthermore, the behavior of my M1 Mac running Big Sur 11.6 did not change, i.e. my Intel-based Mac executables still failed to execute. So, what can be done?
0
0
980
Oct ’21
XPC so universal app can interact with ARM or Intel dylib?
Hello - TLDR - Is there any sample code to demonstrate how one goes about creating dedicated XPCServices to wrap ARM and Intel-specific dylibs? We have an app we're looking at moving to a universal binary. In that same app we have a framework that currently wraps R functionality by directly linking to /Library/Frameworks/R.framework/Current . R now has dedicated Intel and ARM builds (https://mac.r-project.org/) After watching the 2020 WWDC session "Port your Mac app to Apple silicon" (https://developer.apple.com/videos/play/wwdc2020/10214/?time=2006), it sounds like, for us to deploy a universal binary I should look at wrapping the R interaction bits into dedicated ARM and Intel XPC services so the appropriate architecture for R will run. Is anyone aware of any sample code or extended documentation demonstrating the ins and outs of how to think about this? Thank you
9
0
2.4k
Sep ’21
Rosetta error when trying to use a x86_64-only library via XPC
I'm trying to get my macOS app running natively on the Apple Silicon DTK and it's going fine so far. Unfortunately it makes use of a third party library which isn't (and probably won't ever be) available in form of a Universal Binary. This should be no problem, though, because I've been using that library via XPC before and the documentation clearly states that mixed architectures are supported as long as they are out-of-process. So I went ahead and configured Xcode's build settings as follows for the x86-only XPC target: ARCHS: x86_64 VALID_ARCHS: x86_64 The main app and also the XPC compile fine. But when running the app it fails to launch the XPC with the following error in the console: oah error: /var/db/oah/e089a6709d38c1a085254c76a7cb592fcceddb3f234a4aa318bb4ec25fe40d27/a37f39d2b061393d7731233ae89d90cd87c97f4edeeb46a78ad791/ c43ac96d2b/my.xpcBundleID.aot: unable to mmap __TEXT: 1 Does anyone know what's going on here?
2
0
3.8k
Sep ’21
Apple Silicon Kit .ipa installation is not working
I have the Silicon Kit Mac mini and I am trying to run the IPA file for my iOS app on the Mac. I added the Mac to the provisioning profile and built the app on another computer. When I try to open the generated .ipa file on the silicon Mac I get the following error: Unable to install "[my app's name]" This app cannot be installed because its integrity could not be verified. I am using macOS Big Sur Version 11 Beta with the Apple A12Z chip.
6
0
4.6k
Aug ’21
Compiler directives in SwiftUI for platform-specific attributes
I'm building a universal application with SwiftUI that has an iOS app and Share Extension as well as a macOS app and Share Extension. There's a few places where I'm using SwiftUI attributes that are iOS-specific (example a NavigationView that has a StackNavigationViewStyle attribute) and need to provide an alternative when running on macOS. My question is: How do I ensure that these attributes that are only available for one platform don't cause build issues for the other platform? I've tried using the #if os(iOS) compiler directive, but then I get a build error saying "Unexpected platform condition (expected 'os' 'arch' or 'swift')" when doing something like this: &#9;&#9;&#9;&#9;NavigationView { &#9;&#9;&#9;&#9;&#9;&#9;... &#9;&#9;&#9;&#9;}         #if os(iOS)&#9;&#9;&#9; &#9;&#9;&#9;&#9;.navigationViewStyle(StackNavigationViewStyle())         #endif
4
0
6.7k
Jul ’21
optional (weak-link) framework in UB app with only intel arch present?
I'm working getting a large app to Universal Binary, which uses a number of libraries and frameworks with third-party dependencies, a few of which are not yet available as arm64. If a framework is marked as Optional in the app's build settings, the app will still link when it is absent. I expected that if the framework only had one architecture needed for UB (e.g. just x86_64), we should be able to optionally link it successfully, and it would not matter if one architecture was missing. However this isn't how Xcode handles it, we get a linker error for the missing architecture even if the framework is optional. Is there a way to do what I'm expecting? Include an optional framework with only one architecture in a UB app, with the app taking responsibility for correct handling of the framework at runtime (just as it would for a missing optional framework in a single-architecture app)?
3
0
3.7k
Jul ’21
Notarization of universal static library (fat file) doesn't work
I am trying to notarize a framework built for both platforms, arm64 and x8664 (universal). The framework contains a static library (fat file) which can't be notarized. I get the following errors in the log: "The binary is not signed." and "The signature does not include a secure timestamp." When I build only for one of the two architectures (non-fat file), the notarization works without any issues. Universal: % file libtbarcode11.a  libtbarcode11.a: Mach-O universal binary with 2 architectures: [x8664:current ar archive] [arm64] libtbarcode11.a (for architecture x8664): current ar archive libtbarcode11.a (for architecture arm64): current ar archive % lipo -info libtbarcode11.a Architectures in the fat file: libtbarcode11.a are: x8664 arm64   % codesign -v --verify libtbarcode11.a libtbarcode11.a: valid on disk libtbarcode11.a: satisfies its Designated Requirement arm64: % file libtbarcode11.a libtbarcode11.a: current ar archive % lipo -info libtbarcode11.a Non-fat file: libtbarcode11.a is architecture: arm64 % codesign -v --verify libtbarcode11.a libtbarcode11.a: valid on disk libtbarcode11.a: satisfies its Designated Requirement codesign commands I tried so far: codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" libtbarcode11.a codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --options runtime libtbarcode11.a codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --deep libtbarcode11.a
9
0
3.3k
Jul ’21
Can I submit 32-bit (Universal) apps to iOS App Store
I just saw a developer claim that the App Store will no longer accept 32-bit builds. Which presumably means we won’t be able to submit universal. I had wanted to continue to support our few remaining iPad 2 customers, but it sounds like that won’t be possible. I haven’t had any luck finding any official statement about this. I’ve been using Xcode 13.1 and it still lets me target iOS 9…
Replies
1
Boosts
0
Views
1.4k
Activity
Jan ’22
Could not find module for target 'arm64-apple-macos'; found: x86_64, x86_64-apple-macos
I have an XCode Workspace that builds a product as a universal binary for Intel and Apple Silicon. On an Intel-based machine, I am attempting to import a Swift Package dependency by accessing a private git repository. When I attempt to import my dependency into my code and build, I'm getting the following error: Could not find module '<swift package name>' for target 'arm64-apple-macos'; found: x86_64, x86_64-apple-macos The project has Standard Architectures set for the ARCHS build setting and ONLY_ACTIVE_ARCH = NO. When I switch ONLY_ACTIVE_ARCH = YES, it builds fine. Is there a way to instruct the compiler to build the swift package dependency as universal and resolve this issue?
Replies
1
Boosts
0
Views
3.1k
Activity
Dec ’21
(macOS) dlopen universal dylib leads to "slice is not page aligned"
Built using Xcode Version 13.1 (13A1030d) on macOS Monterey 12.0.1. The dylib was built in a release configuration with architectures set to $(ARCHS_STANDARD). This builds a FAT binary with x86_64 and arm64, as expected. However, when I dlopen it with RTLD_NOW | RTLD_GLOBAL, it fails and dlerror reports "slice is not page aligned" twice, and a message saying that it is looking for x86_64h but only finds x86_64,arm64 is reported. Not sure what the root cause is, but certainly the slice not being page aligned is causing issues. The question may therefore be: how can I ensure the dylib generated as a FAT binary has its slices aligned in Xcode 13?
Replies
1
Boosts
0
Views
1.6k
Activity
Dec ’21
Command PhaseScriptExecution failed with a nonzero exit code
Since a few days I can't compile my flutter project anymore. I tried several solutions found on the internet but none of them worked for me. I am using a MacBook Pro M1 with XCODE version 12.5.1 (12E507). You can find the output of the error I'm experiencing in the attached copy. Thank you for any useful help that can save me from this situation. Error message: 👇🏾  /bin/sh -c /Users/donarias/Library/Developer/Xcode/DerivedData/Runner-fdbfjdxtqbyzbqgfhspjraxpjmdc/Build/Intermediates.noindex/Runner.build/Debug-iphonesimulator/Runner.build/Script-9740EEB61CF901F6004384FC.sh ../../../../../.pub-cache/hosted/pub.dartlang.org/flutter_datetime_picker-1.5.1/lib/flutter_datetime_picker.dart:311:32: Warning: Operand of null-aware operation '??' has type 'Color' which excludes null.  - 'Color' is from 'dart:ui'.                   color: theme.backgroundColor ?? Colors.white,                                ^ ../../../../../.pub-cache/hosted/pub.dartlang.org/get-4.3.4/lib/get_navigation/src/root/get_material_app.dart:297:15: Error: No named parameter with the name 'scrollBehavior'.               scrollBehavior: scrollBehavior,               ^^^^^^^^^^^^^^ ../../../../flutter/packages/flutter/lib/src/material/app.dart:217:9: Context: Found this candidate, but the arguments don't match.   const MaterialApp.router({         ^^^^^^^^^^^^^^^^^^ ../../../../../.pub-cache/hosted/pub.dartlang.org/get-4.3.4/lib/get_navigation/src/root/get_material_app.dart:340:15: Error: No named parameter with the name 'scrollBehavior'.               scrollBehavior: scrollBehavior,               ^^^^^^^^^^^^^^ ../../../../flutter/packages/flutter/lib/src/material/app.dart:167:9: Context: Found this candidate, but the arguments don't match.   const MaterialApp({         ^^^^^^^^^^^ Command PhaseScriptExecution failed with a nonzero exit code
Replies
2
Boosts
0
Views
1.8k
Activity
Dec ’21
My app is damaged and can't be opened when porting to M1 ?
I have porting my existing application to support native M1, there a a lot of framework and library that I have already build for both platform. The strange result is when I archive the app on Intel machine. The binary work on Intel platform well. When I archive my application on M1 machine, the app can work on M1 well. But when I try to run app that build on M1 on Intel Machine, then I got the message said my app is damaged and can't be opened. The same situation got for build in Intel platform one. I try "lipo -archs" command on my app and I did get "x86_64 arm64" as result, so my app should already a universal app I guess. Does any body know are there some way to check what happened on my application? Thanks, any opinion will be appreciated ! Eric
Replies
3
Boosts
0
Views
4.5k
Activity
Dec ’21
ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1
Hi, I'm facing the same error! You example is Passed! But it doesn't work when I compile NCURSES. It seems that there are something wrong with my ld % ld -v @(#)PROGRAM:ld  PROJECT:ld64-711 BUILD 18:11:19 Aug  3 2021 configured to support archs: armv6 armv7 armv7s arm64 arm64e arm64_32 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em LTO support using: LLVM version 13.0.0, (clang-1300.0.29.3) (static support for 27, runtime is 27) TAPI support using: Apple TAPI version 13.0.0 (tapi-1300.0.6.5) % clang -v Apple clang version 13.0.0 (clang-1300.0.29.3) Target: arm64-apple-darwin21.1.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin Here are the configuration and error. ** Configuration summary for NCURSES 6.3 20211021:        extended funcs: yes        xterm terminfo: xterm-new         bin directory: /usr/local/bin         lib directory: /usr/local/lib     include directory: /usr/local/include/ncurses         man directory: /usr/local/share/man    terminfo directory: /usr/local/share/terminfo ** Include-directory is not in a standard location``` gcc ../objects/tic.o ../objects/dump_entry.o ../objects/tparm_type.o ../objects/transform.o -L../lib -Wl,-search_paths_first -DHAVE_CONFIG_H -I../progs -I. -I../include -D_DARWIN_C_SOURCE -DNDEBUG -O2 -Qunused-arguments -Wno-error=implicit-function-declaration -no-cpp-precomp  -DNCURSES_STATIC -L../lib  -lncurses -lncurses    -o tic ld: warning: ignoring file ../lib/libncurses.a, building for macOS-arm64 but attempting to link with file built for unknown-unsupported file format ( 0x21 0x3C 0x61 0x72 0x63 0x68 0x3E 0x0A 0x2F 0x20 0x20 0x20 0x20 0x20 0x20 0x20 ) Undefined symbols for architecture arm64:   "__nc_boolcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_boolfnames", referenced from:       _dump_init in dump_entry.o   "__nc_boolnames", referenced from:       _dump_init in dump_entry.o   "__nc_capcmp", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o   "__nc_check_termtype2", referenced from:       _main in tic.o   "__nc_curr_col", referenced from:       _main in tic.o   "__nc_curr_line", referenced from:       _main in tic.o   "__nc_disable_period", referenced from:       _main in tic.o   "__nc_doalloc", referenced from:       _main in tic.o       _fmt_entry in dump_entry.o       _strcpy_DYN in dump_entry.o       _fmt_complex in dump_entry.o       _strncpy_DYN in dump_entry.o   "__nc_find_entry", referenced from:       _check_user_capability_type in tic.o       _nametrans in dump_entry.o   "__nc_find_user_entry", referenced from:       _check_termtype in tic.o       _check_user_capability_type in tic.o   "__nc_first_name", referenced from:       _main in tic.o       _check_termtype in tic.o       _fmt_complex in dump_entry.o       _dump_entry in dump_entry.o   "__nc_get_hash_table", referenced from:       _check_user_capability_type in tic.o       _nametrans in dump_entry.o   "__nc_head", referenced from:       _main in tic.o   "__nc_home_terminfo", referenced from:       _show_databases in tic.o   "__nc_infotocap", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o   "__nc_name_match", referenced from:       _main in tic.o   "__nc_numcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_numfnames", referenced from:       _dump_init in dump_entry.o   "__nc_numnames", referenced from:       _dump_init in dump_entry.o   "__nc_pathlast", referenced from:       _valid_db_path in tic.o   "__nc_read_entry_source", referenced from:       _main in tic.o   "__nc_reset_tparm", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o   "__nc_resolve_uses2", referenced from:       _main in tic.o   "__nc_rootname", referenced from:       _main in tic.o   "__nc_set_source", referenced from:       _main in tic.o   "__nc_set_type", referenced from:       _main in tic.o   "__nc_set_writedir", referenced from:       _main in tic.o   "__nc_strcodes", referenced from:       _nametrans in dump_entry.o       _dump_init in dump_entry.o   "__nc_strfnames", referenced from:       _dump_init in dump_entry.o   "__nc_strict_bsd", referenced from:       _main in tic.o   "__nc_strnames", referenced from:       _check_termtype in tic.o      _dump_init in dump_entry.o       _dump_entry in dump_entry.o   "__nc_syntax", referenced from:       _check_termtype in tic.o   "__nc_tail", referenced from:       _main in tic.o   "__nc_tic_dir", referenced from:   _main in tic.o       _show_databases in tic.o   "__nc_tic_expand", referenced from:       _check_ansi_cursor in tic.o       _fmt_entry in dump_entry.o   "__nc_tic_written", referenced from:       _main in tic.o   "__nc_tinfo_fkeysf", referenced from:       _check_termtype in tic.o   "__nc_tiparm", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o       _check_1_infotocap in tic.o       _same_color in tic.o   "__nc_tparm_analyze", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o   "__nc_tparm_err", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o   "__nc_tracing", referenced from:       _main in tic.o   "__nc_trim_sgr0", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o   "__nc_user_definable", referenced from:       _check_termtype in tic.o       _fmt_entry in dump_entry.o       _compare_entry in dump_entry.o   "__nc_visbuf", referenced from:       _similar_sgr in tic.o   "__nc_visbuf2", referenced from:       _check_termtype in tic.o       _check_sgr in tic.o       _similar_sgr in tic.o   "__nc_warning", referenced from:       _check_termtype in tic.o       _check_user_capability_type in tic.o       _check_sgr in tic.o       _check_sgr_param in tic.o       _check_1_infotocap in tic.o       _check_noaddress in tic.o       _check_ansi_cursor in tic.o       ...   "__nc_write_entry", referenced from:       _main in tic.o   "__nc_write_object", referenced from:       _dump_entry in dump_entry.o   "_curses_version", referenced from:       _main in tic.o   "_keyname", referenced from:       _check_termtype in tic.o   "_tgoto", referenced from:       _check_sgr_param in tic.o   "_tigetflag", referenced from:       _check_termtype in tic.o   "_tigetstr", referenced from:       _check_termtype in tic.o   "_tparm", referenced from:       _check_termtype in tic.o       _check_1_infotocap in tic.o      (maybe you meant: _tparm_type, _guess_tparm_type )   "_use_extended_names", referenced from:       _main in tic.o ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[1]: *** [tic] Error 1 make: *** [all] Error 2
Replies
0
Boosts
0
Views
1.4k
Activity
Dec ’21
Xcode won't build for macOS Apple Silicon
I just got an M1 MacBook Pro. I'm trying to build one of my macOS projects for Apple Silicon, but it only gives me "My Mac (Rosetta)" as a run destination (or "Any Mac (Intel)"), even though I've set the build archs to universal. Googling is no help.
Replies
1
Boosts
0
Views
1.8k
Activity
Nov ’21
Universal App Not Resizable as Expected
I have an app that started out as an iPhone/iPad app and I added support for Mac. According to videos and documentation I've read online, one of the things you get for free is the ability to resize screens. It does, in fact, work that way when I build to MacOS from Xcode. However, when I upload the build to Testflight and run that version of the app, installed by Testflight, it doesn't resize. I should qualify that. I can drag a corner to switch it between portrait and landscape, but the size remains the same. I'm not sure what to look for, especially since resizing works when I build from Xcode. Any suggestions? I'm using SideMenu as the navigation controller for the app. The main view controller that instantiates Side Menu adds four view controllers as children. One of those is a portrait-only view controller. Since it works as expected when I build from Xcode, anything I try will have to be archived and uploaded to Testflight. So any suggestions of likely things to try would be greatly appreciated. I am NOT doing anything with windowScene size restrictions.
Replies
1
Boosts
0
Views
922
Activity
Nov ’21
Xcode 12.2 'IPA processing failed' to distribute IPA from archived app
I could archive the app in Xcode 12.2 DKT device. however when I try to distribute IPA from archived files and it failed with 'IPA processing failed'. from the log files, there is no useful information. Does anyone have similar issues? I appreciate any suggestions how to solve this issue.
Replies
5
Boosts
0
Views
10k
Activity
Oct ’21
Is there a planned end of life for Rosetta 2?
I found some articles on MacOS 11.3, that are several months old, that intimated that Rosetta 2 will be discontinued in future releases. Is there any official timeline for the deprecation of Rosetta 2 for ARM based Macs? Thanks.
Replies
1
Boosts
0
Views
3.1k
Activity
Oct ’21
What can be done to execute Intel-based Mac executables on an M1 Mac running Big Sur 11.6?
Rosetta and Rosetta 2 do not appear to be available.  All attempts to execute the Intel code failed with the "zsh: bad CPU type in executable" message.  Since I wasn't prompted to install Rosetta or Rosetta 2, I executed the following, % softwareupdate --install-rosetta which responded with I have read and agree to the terms of the software license agreement. A list of Apple SLAs may be found here: http://www.apple.com/legal/sla/ Type A and press return to agree: So, I typed the A and the return.  The result was 2021-10-03 04:31:49.497 softwareupdate[1775:240889] Package Authoring Error: 071-97390: Package reference com.apple.pkg.RosettaUpdateAuto is missing install KBytes attribute Install of Rosetta 2 finished successfully Although the message ended with "finished successfully", note the error disclosed. Furthermore, the behavior of my M1 Mac running Big Sur 11.6 did not change, i.e. my Intel-based Mac executables still failed to execute. So, what can be done?
Replies
0
Boosts
0
Views
980
Activity
Oct ’21
XPC so universal app can interact with ARM or Intel dylib?
Hello - TLDR - Is there any sample code to demonstrate how one goes about creating dedicated XPCServices to wrap ARM and Intel-specific dylibs? We have an app we're looking at moving to a universal binary. In that same app we have a framework that currently wraps R functionality by directly linking to /Library/Frameworks/R.framework/Current . R now has dedicated Intel and ARM builds (https://mac.r-project.org/) After watching the 2020 WWDC session "Port your Mac app to Apple silicon" (https://developer.apple.com/videos/play/wwdc2020/10214/?time=2006), it sounds like, for us to deploy a universal binary I should look at wrapping the R interaction bits into dedicated ARM and Intel XPC services so the appropriate architecture for R will run. Is anyone aware of any sample code or extended documentation demonstrating the ins and outs of how to think about this? Thank you
Replies
9
Boosts
0
Views
2.4k
Activity
Sep ’21
Rosetta error when trying to use a x86_64-only library via XPC
I'm trying to get my macOS app running natively on the Apple Silicon DTK and it's going fine so far. Unfortunately it makes use of a third party library which isn't (and probably won't ever be) available in form of a Universal Binary. This should be no problem, though, because I've been using that library via XPC before and the documentation clearly states that mixed architectures are supported as long as they are out-of-process. So I went ahead and configured Xcode's build settings as follows for the x86-only XPC target: ARCHS: x86_64 VALID_ARCHS: x86_64 The main app and also the XPC compile fine. But when running the app it fails to launch the XPC with the following error in the console: oah error: /var/db/oah/e089a6709d38c1a085254c76a7cb592fcceddb3f234a4aa318bb4ec25fe40d27/a37f39d2b061393d7731233ae89d90cd87c97f4edeeb46a78ad791/ c43ac96d2b/my.xpcBundleID.aot: unable to mmap __TEXT: 1 Does anyone know what's going on here?
Replies
2
Boosts
0
Views
3.8k
Activity
Sep ’21
Apple Silicon Kit .ipa installation is not working
I have the Silicon Kit Mac mini and I am trying to run the IPA file for my iOS app on the Mac. I added the Mac to the provisioning profile and built the app on another computer. When I try to open the generated .ipa file on the silicon Mac I get the following error: Unable to install "[my app's name]" This app cannot be installed because its integrity could not be verified. I am using macOS Big Sur Version 11 Beta with the Apple A12Z chip.
Replies
6
Boosts
0
Views
4.6k
Activity
Aug ’21
Compiler directives in SwiftUI for platform-specific attributes
I'm building a universal application with SwiftUI that has an iOS app and Share Extension as well as a macOS app and Share Extension. There's a few places where I'm using SwiftUI attributes that are iOS-specific (example a NavigationView that has a StackNavigationViewStyle attribute) and need to provide an alternative when running on macOS. My question is: How do I ensure that these attributes that are only available for one platform don't cause build issues for the other platform? I've tried using the #if os(iOS) compiler directive, but then I get a build error saying "Unexpected platform condition (expected 'os' 'arch' or 'swift')" when doing something like this: &#9;&#9;&#9;&#9;NavigationView { &#9;&#9;&#9;&#9;&#9;&#9;... &#9;&#9;&#9;&#9;}         #if os(iOS)&#9;&#9;&#9; &#9;&#9;&#9;&#9;.navigationViewStyle(StackNavigationViewStyle())         #endif
Replies
4
Boosts
0
Views
6.7k
Activity
Jul ’21
optional (weak-link) framework in UB app with only intel arch present?
I'm working getting a large app to Universal Binary, which uses a number of libraries and frameworks with third-party dependencies, a few of which are not yet available as arm64. If a framework is marked as Optional in the app's build settings, the app will still link when it is absent. I expected that if the framework only had one architecture needed for UB (e.g. just x86_64), we should be able to optionally link it successfully, and it would not matter if one architecture was missing. However this isn't how Xcode handles it, we get a linker error for the missing architecture even if the framework is optional. Is there a way to do what I'm expecting? Include an optional framework with only one architecture in a UB app, with the app taking responsibility for correct handling of the framework at runtime (just as it would for a missing optional framework in a single-architecture app)?
Replies
3
Boosts
0
Views
3.7k
Activity
Jul ’21
Notarization of universal static library (fat file) doesn't work
I am trying to notarize a framework built for both platforms, arm64 and x8664 (universal). The framework contains a static library (fat file) which can't be notarized. I get the following errors in the log: "The binary is not signed." and "The signature does not include a secure timestamp." When I build only for one of the two architectures (non-fat file), the notarization works without any issues. Universal: % file libtbarcode11.a  libtbarcode11.a: Mach-O universal binary with 2 architectures: [x8664:current ar archive] [arm64] libtbarcode11.a (for architecture x8664): current ar archive libtbarcode11.a (for architecture arm64): current ar archive % lipo -info libtbarcode11.a Architectures in the fat file: libtbarcode11.a are: x8664 arm64   % codesign -v --verify libtbarcode11.a libtbarcode11.a: valid on disk libtbarcode11.a: satisfies its Designated Requirement arm64: % file libtbarcode11.a libtbarcode11.a: current ar archive % lipo -info libtbarcode11.a Non-fat file: libtbarcode11.a is architecture: arm64 % codesign -v --verify libtbarcode11.a libtbarcode11.a: valid on disk libtbarcode11.a: satisfies its Designated Requirement codesign commands I tried so far: codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" libtbarcode11.a codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --options runtime libtbarcode11.a codesign --force --verify --verbose --sign "MyDeveloperIDApplicationCert" --deep libtbarcode11.a
Replies
9
Boosts
0
Views
3.3k
Activity
Jul ’21
Command CompileSwift failed with a nonzero exit code
How to fix 'Command CompileSwift failed with a nonzero exit code' in Xcode?
Replies
0
Boosts
0
Views
751
Activity
Jul ’21
libexif universal library
Has anyone created a universal libexif.a that will work on both Intel and Apple silicon? Can someone please share a link.
Replies
0
Boosts
0
Views
528
Activity
Jul ’21
DeviceCheck on Apple M1 mac's don't work in iOS app
DCDevice.isSupported = false if iOS app running on Apple M1 Chip Mac. Bug?
Replies
2
Boosts
0
Views
1.5k
Activity
Jun ’21