Automatic signing failed. Xcode failed to provision this target. Please file a bug report - ios

Error: Xcode failed to provision this target. Please file a bug report at https://feedbackassitant.apple.com and include the Update Signing report from the report navigator.
After upgrade of Xcode, MacOS and React Native running the app on a connected real device using Xcode and local environment cannot be done because build process shows the above error.
Environment:
OS: macOS 13.1
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU # 2.30GHz
Memory: 33.82 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.10.0 - ~/.nvm/versions/node/v16.10.0/bin/node
Yarn: 1.22.18 - /usr/local/bin/yarn
npm: 7.24.0 - ~/.nvm/versions/node/v16.10.0/bin/npm
Watchman: 2022.03.21.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 26, 27, 28, 29, 30, 31, 32, 33
Build Tools: 27.0.3, 28.0.3, 29.0.0, 29.0.2, 29.0.3, 30.0.0, 30.0.2, 30.0.3, 31.0.0, 31.0.0, 32.0.0, 32.1.0, 33.0.0, 33.0.0, 33.0.0, 33.0.0, 33.0.1
System Images: android-26 | Intel x86 Atom_64, android-26 | Google Play Intel x86 Atom, android-27 | Intel x86 Atom_64, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom, android-28 | Google X86_ARM Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom, android-30 | Google Play Intel x86 Atom_64, android-31 | Intel x86 Atom_64, android-31 | Google APIs ARM 64 v8a, android-31 | Google APIs Intel x86 Atom_64, android-31 | Google Play ARM 64 v8a, android-31 | Google Play Intel x86 Atom_64, android-32 | Google APIs Intel x86 Atom_64, android-32 | Google Play Intel x86 Atom_64, android-33 | Google APIs Intel x86 Atom_64, android-33 | Google Play Intel x86 Atom_64

Short answer:
There was a problem with provisioning profiles of one of my project targets, <MyProjectName>Tests one. After react native and Xcode update it seems that there is a need for valid profiles for that target to. I removed that target because I don't need it and building and running on real connected devices work now.
Steps:
checked all the certificates
updated my provisioning profiles
checked signing for all targets
removed the test target because that required signing and another update of the provisioning profiles and I didn't need it
cleaned build folder and rebuilt

Related

how do I disable wlan0 hard block from rfkill

there are very similar questions to this one but all of them are solved by disabling some other wifi source by using modprobe and then reseting rfkill
in my case:
artixlinux:[rail]:/etc/modprobe.d$ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
and with nmcli:
wlan0: unavailable
"Qualcomm Atheros AR9485"
wifi (ath9k), 5A:9D:61:C0:BB:F0, sw disabled, hw, mtu 1500
I've already tried to modprobe ath9k but that does nothing
hardware:
[System]
OS: Artix Linux 20220123 n/a
Arch: x86_64
Kernel: 5.18.0-zen1-1-zen
Desktop: KDE
Display Server: x11
[CPU]
Vendor: GenuineIntel
Model: Intel(R) Core(TM) i3-3227U CPU # 1.90GHz
Physical cores: 2
Logical cores: 4
[Memory]
RAM: 3.7 GB
Swap: 0.0 GB
[Graphics]
Vendor: Intel
OpenGL Renderer: Mesa Intel(R) HD Graphics 4000 (IVB GT2)
OpenGL Version: 4.2 (Compatibility Profile) Mesa 22.2.0-devel (git-3e679219a1)
OpenGL Core: 4.2 (Core Profile) Mesa 22.2.0-devel (git-3e679219a1)
OpenGL ES: OpenGL ES 3.0 Mesa 22.2.0-devel (git-3e679219a1)
Vulkan: Supported
See https://askubuntu.com/a/98719
"Hard blocked" cannot be changed by software, look for a wifi toggle on your keyboard or edges of the laptop; the device can also be hard blocked if disabled in the bios.
And:
https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill#comment618926_98719
FYI hard block also happens when the wifi is disabled in the bios.

CreateRemoteThread() fails with Access Denied (0xc00000005)

CreateRemoteThread() runs successfully for "32 bit caller process - 32 bit target process", but fails with Access Denied (0xc00000005) for "x64 caller process - x64 target process" :
handle of target process received with flags PROCESS_CREATE_THREAD | PROCESS_QUERY_INFORMATION | PROCESS_VM_OPERATION | PROCESS_VM_WRITE | PROCESS_VM_READ
both processes are services and run under the Local System Account
both processes are really 64bit - compiled by Visual Studio 2012 (Platform x64)
OS - Windows Server 2016
Thanks!

New expo init bare project not building for iOS

Started by using expo init app and used bare-minimum typescript template, the app is not building using react-native run-ios, but works if expo start in the Expo-go app.
here is the error code:
info Installing "/Users/mac/Library/Developer/Xcode/DerivedData/myproject-ccluoxcwmsrveqavqitrwaszccss/Build/Products/Debug-iphonesimulator/myproject"
An error was encountered processing the command (domain=IXUserPresentableErrorDomain, code=1):
This app could not be installed at this time.
Could not install at this time.
Failed to chmod /Users/mac/Library/Developer/CoreSimulator/Devices/2D6990A9-04F6-4391-BFA3-BFF2AA6890A5/data/Bundle/Application/2B342978-B520-410C-ABB0-F5961248B7BF/myproject.app/myproject : No such file or directory
Underlying error (domain=MIInstallerErrorDomain, code=4):
Failed to chmod /Users/mac/Library/Developer/CoreSimulator/Devices/2D6990A9-04F6-4391-BFA3-BFF2AA6890A5/data/Bundle/Application/2B342978-B520-410C-ABB0-F5961248B7BF/myproject.app/myproject : No such file or directory
info Launching "org.name.myproject"
error Failed to launch the app on simulator, An error was encountered processing the command (domain=FBSOpenApplicationServiceErrorDomain, code=1):
The request to open "org.name.myproject" failed.
The request was denied by service delegate (SBMainWorkspace) for reason: NotFound ("Application "org.name. myproject" is unknown to FrontBoard").
Underlying error (domain=FBSOpenApplicationErrorDomain, code=4):
The operation couldn’t be completed. Application "org.name.myproject" is unknown to FrontBoard.
Application "org.name.myproject" is unknown to FrontBoard.
When app is launched in Xcode the build is successful but the app don't load on simulator and I get this error message:
the config:
Expo CLI 4.1.6 environment info:
System:
OS: macOS 11.0.1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.15.5 - ~/.nvm/versions/node/v14.15.5/bin/node
Yarn: 1.22.0 - /usr/local/bin/yarn
npm: 6.14.11 - ~/.nvm/versions/node/v14.15.5/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 23, 24, 27, 28, 29
Build Tools: 23.0.1, 27.0.3, 28.0.2, 28.0.3, 29.0.2
System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
IDEs:
Xcode: 11.7/11E801a - /usr/bin/xcodebuild
npmPackages:
expo: ~40.0.0 => 40.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.1
react-native: ~0.63.4 => 0.63.4
react-native-web: ~0.13.12 => 0.13.18
Expo Workflow: bare

iOS Native Module - Invariant Violation: Native module cannot be null

I have an issue with upgrading react-native version from 0.59.10 to 0.61.5. We are using our own native modules and it seems like to be problem with them. This problem I have only on iOS.
ERROR:
Invariant Violation: Native module cannot be null.
React Native version:
System:
OS: macOS 10.15.2
CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU # 2.30GHz
Memory: 70.44 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.5.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.12.0 - /usr/local/bin/npm
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 27, 28, 29
Build Tools: 28.0.3, 29.0.0, 29.0.1, 29.0.2
System Images: android-26 | Google APIs Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
Android NDK: 20.0.5594570
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5791312
Xcode: 11.3/11C29 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
react-native: 0.61.5
GITHUB: https://github.com/facebook/react-native/issues/27975

Xcode simulator not working error - could not load inserted library '/usr/lib/libignitor2.dylib' because no suitable image found

Updated my xcode this evening to 7.2.1 im running on yosemite 10.10.5
i've just started learning swift, and everytime i try to run the simulator it crashes with the error:
could not load inserted library '/usr/lib/libignitor2.dylib' because no suitable image found.
I have spent the last 4 hours searching online, there seems to be a few similar errors of inserted library missing but nothing that i can see that helps with this error. The full code can be seen below.
Process: Simulator [2907]
Path: /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
Identifier: com.apple.iphonesimulator
Version: 9.2 (643)
Build Info: Indigo-643000000000000~28
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Simulator [2907]
User ID: 501
Date/Time: 2016-09-10 03:00:48.102 +0100
OS Version: Mac OS X 10.10.5 (14F1912)
Report Version: 11
Anonymous UUID: 1ACB9325-E877-4FA4-FEBD-B9450D15E13A
Time Awake Since Boot: 10000 seconds
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
DYLD_INSERT_LIBRARIES=/usr/lib/libignitor2.dylib
Dyld Error Message:
could not load inserted library '/usr/lib/libignitor2.dylib' because no suitable image found. Did find:
/usr/lib/libignitor2.dylib: mmap() error 1 at address=0x107DE9000, size=0x00001000 segment=__TEXT in Segment::map() mapping /usr/lib/libignitor2.dylib
Binary Images:
0x107da0000 - 0x107dccff7 com.apple.iphonesimulator (9.2 - 643) <2A577F90-517C-3363-A980-EEB79D21FEBF> /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator
0x7fff65635000 - 0x7fff6566b92f dyld (353.2.4) <708E385E-50C6-32A3-983C-42E97BEE4346> /usr/lib/dyld
Model: MacBookPro12,1, BootROM MBP121.0167.B14, 2 processors, Intel Core i5, 2.7 GHz, 16 GB, SMC 2.28f7
Graphics: Intel Iris Graphics 6100, Intel Iris Graphics 6100, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1867 MHz, 0x02FE, 0x4544464232333241314D412D4A442D460000
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x133), Broadcom BCM43xx 1.0 (7.15.166.24.3)
Bluetooth: Version 4.3.6f3 16238, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0128G, 121.33 GB
USB Device: Internal Memory Card Reader
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 27.1
Any help would be appreciated. thanks
You could try
sudo update_dyld_shared_cache -force
I'm trying to fix my beta but it appears to be trying to get after an update and this is the solution I"m working with. If it fails you can try
https://apple.stackexchange.com/questions/217232/trying-to-force-update-dyld-shared-cache-but-having-some-errors
I hope this is helpful

Resources