Hi developers,
I'm searching for a kind of way of working to develop my apps on a different machine than testing and final building.
For development I have a MacBook Pro m4 and for testing I want to outsource this to a Mac mini m1. I was searching for a solution and also contacted the support, but the answer wasn't really helpful.
Any ideas how to setup this configuration to automate this kind of tests?
Thanks a lot!
Developer Tools
RSS for tagAsk questions about the tools you can use to build apps.
Posts under Developer Tools tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
Hello Everyone,
Planning to add one Devoloper to my team for Xcode app development.
whats best to configure Xcloud ,Git and push updates to the main branches .
and i prefer not to use third party software or additional tools .
Thanks a lot and much appreciated
I have a very large terminal project that relies on the ncurses library. As of the update on Dec. 11, 2024, the ncurses (and forms) API's no longer work when the app is launched from Xcode. If I run the app by double-clicking on the executable from Finder, the API's work as expected - but of course, that does not allow for debugging - which is the purpose of running within Xcode.
I have tested on a simple project that simply outputs "Hello World" and waits for the input of CR before ending. What should happen, is that "Hello Word" is output on the terminal, but instead no output occurs. I stress that everything worked prior to the update on Dec.11.
The code for main is simply this:
#include <iostream>
#include "stdlib.h"
#include "stdio.h"
#ifdef __cplusplus
#include <iostream>
#endif
#include <cassert>
#include <ncurses.h>
#include <form.h>
using namespace std;
int main(int argc, const char * argv[]) {
// cout << "Hello, World!" << endl;
// Basic test
initscr();
printw("Hello World !!!");
refresh();
int ch = 0;
while (ch != 10) {
ch = getch();
}
endwin();
return 0;
}
To link to libncurses.tbd, in Build Phases, add the libncurses.tbd from the list of Frameworks.
To output on the terminal, select the Product menu item in Xcode, then Edit Schema. Under the Options tab, change the Console selection to Terminal.
When the application runs, the terminal will launch, but no output will occur. I have Googled every topic imaginable for 2 days now but have not come up with a solution. Is there something that I need to update? It looks to me like the libraries have been updated on Dec. 11 as well, but is there something else I need to do?
For a more detailed image of one of the many screens I have working prior to this issue:
I have been using US Cellular without any issues, and my previous device worked seamlessly with a stable connection. However, after updating to iOS 18.3 (22D5040d), I have been experiencing significant connectivity problems. In most locations, I have no internet access, and when I do, the speeds are extremely slow, typically around 2 Mbps at best.
I have been trying for the past month to complete the payment for the Apple Developer Program enrollment. However, every time I attempt the payment, it fails, and my account remains pending.
I have tried contacting Apple Support multiple times, and each time a case ID is created, but I do not receive any response. I have also tried using different cards for the payment, but the issue persists.
I am attempting to create the account from Bangladesh.
I'm pulling my hair out here with this new Xcode 16, it complains that my app's dSYM is empty though it's clearly not, it's about 25MB.
I'm working on a project using an internal static library, everything is built inhouse using swift, we own all the source code. It worked just fine until the other week, when I updated the Xcode, and now I can't debug anything. I keep getting "type for self cannot be reconstructed" when I run "po self.some_property". Why is that?
The Debug information Format is set to DWARF with dSYM File for both the executable and lib projects.
I've been a Unix guy since before I knew myself and I enjoy fixing things myself, down to bare metal, but man, this bug is driving me crazy. Is it even a bug??
It's the first time in more than 15 years since I started coding on Mac and iPhone when a bug has defeated me. I was always able to fix things using just the documentation and google, but the Apple toolchain is getting worse and worse nowadays.
I remember the time when Apple made the complicated things simple, now they make the simple things complicated :(
I just split the static lib from the main project one year ago, because of the ridiculously long build time. Should I merge back all the code in a single project? Something seems wrong to me.
So I created this account to ask the masters. How can I get back my debug info (and sanity)? Using Xcode 15 is not an option because it doesn't run on Sequoia.
I’m trying to fix an issue with a pipeline that automatically distributes an app to the App Store (TestFlight). Unfortunately, universal links don’t work because the .entitlements file in the build doesn’t include the specified associated domains, even though they are defined. I’ve double-checked the certificates, provisioning profiles, and Xcode settings — everything seems correct. Therefore, I assume the issue lies in the build commands, which are as follows:
Create Archive
xcodebuild -workspace ios/ClientDomain.xcworkspace -scheme ClientDomain archive -sdk iphoneos -configuration ClientDomain -archivePath ios/ClientDomain.xcarchive CODE_SIGN_STYLE=Manual CODE_SIGN_IDENTITY="Apple Distribution: Company Name (XXXXXXXXXX)" PROVISIONING_PROFILE=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx CODE_SIGNING_ALLOWED=No
Export Archive
xcodebuild -exportArchive -archivePath ios/ClientDomain.xcarchive -exportPath ios -exportOptionsPlist ios/exportOptions.plist
I also want to provide files I use, in order to make sure I don't have any mistakes:
ClientDomain.entitlements
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>com.apple.developer.associated-domains</key>
<array>
<string>applinks:www.site.com</string>
<string>webcredentials:www.site.com</string>
</array>
</dict>
</plist>
exportOptions.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>destination</key>
<string>export</string>
<key>generateAppStoreInformation</key>
<false/>
<key>manageAppVersionAndBuildNumber</key>
<true/>
<key>method</key>
<string>app-store-connect</string>
<key>provisioningProfiles</key>
<dict>
<key>com.bundle.app</key>
<string>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</string>
</dict>
<key>signingCertificate</key>
<string>Apple Distribution: Company Name (XXXXXXXXXX)</string>
<key>signingStyle</key>
<string>manual</string>
<key>stripSwiftSymbols</key>
<true/>
<key>teamID</key>
<string>XXXXXXXXXX</string>
<key>testFlightInternalTestingOnly</key>
<false/>
<key>uploadSymbols</key>
<true/>
</dict>
</plist>
I'm curious, how people usually distribute their apps to App Store. What if I do something wrong?
Due to legal issues, our build machine is not connected to the Internet.
We built the app through the "xcodebuild" command, and we have all the supplies for the build without internet connection.
Certificate for valid deployment on keychain (including private key)
Provisioning Profiles
Disable the ability to automatically sign on to build settings.
After updating to xcode16.0, I found that the build doesn't work at all.
When I checked the release notes(xcod16.0), I saw that the provisioning profile needs to be newly issued and then built.
When I issued and built a new provisioning profile, the app build was successful, but we found that it took more than twice the build time.
When I look at the build log, it is exposed, and it is estimated that there is a long wait.
The stage where this log comes out
GatherProvisioningInputs
The moment you start exporting after the archive has been completed
1.GatherProvisioningInputs
13-Jan-2025 12:31:13 2025-01-13 12:31:13.072 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for CC992AE6-495A-419C-B6B8-65D10F340DAE: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username}
13-Jan-2025 12:31:13 2025-01-13 12:31:13.078 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for D604A570-36EF-438B-BDEE-7D097892F46F: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username}
13-Jan-2025 12:31:13 2025-01-13 12:31:13.085 xcodebuild[36909:161529200] DVTDeveloperAccountManager: Failed to load credentials for mymailadress: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for mymailadress, missing Xcode-Token" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for mymailadress, missing Xcode-Token}
The moment you start exporting after the archive has been completed
13-Jan-2025 12:39:59
** ARCHIVE SUCCEEDED **
13-Jan-2025 12:39:59
13-Jan-2025 12:40:01
2025-01-13 12:40:01.028 xcodebuild[44083:161711515] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path "/var/folders/zv/mn5wc_kx19n19vntm4mwqv800000gn/T/NewLotteCard Release_2025-01-13_12-40-01.025.xcdistributionlogs".
13-Jan-2025 12:40:02
2025-01-13 12:40:02.016 xcodebuild[44083:161711515] [MT] IDEDistribution: Command line name "app-store" is deprecated. Use "app-store-connect" instead.
13-Jan-2025 12:40:03
2025-01-13 12:40:03.287 xcodebuild[44083:161713365] DVTDeveloperAccountManager: Failed to load credentials for CC992AE6-495A-419C-B6B8-65D10F340DAE: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for CC992AE6-495A-419C-B6B8-65D10F340DAE, missing Xcode-Username}
13-Jan-2025 12:40:03
2025-01-13 12:40:03.291 xcodebuild[44083:161713365] DVTDeveloperAccountManager: Failed to load credentials for D604A570-36EF-438B-BDEE-7D097892F46F: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for D604A570-36EF-438B-BDEE-7D097892F46F, missing Xcode-Username}
13-Jan-2025 12:40:03
2025-01-13 12:40:03.295 xcodebuild[44083:161713365] DVTDeveloperAccountManager: Failed to load credentials for 7E18031A-9964-4A42-9F5C-6D36B08ACD40: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for 7E18031A-9964-4A42-9F5C-6D36B08ACD40, missing Xcode-Username" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for 7E18031A-9964-4A42-9F5C-6D36B08ACD40, missing Xcode-Username}
13-Jan-2025 12:40:03
2025-01-13 12:40:03.300 xcodebuild[44083:161713365] DVTDeveloperAccountManager: Failed to load credentials for mymailadress: Error Domain=DVTDeveloperAccountCredentialsError Code=0 "Invalid credentials in keychain for mymailadress, missing Xcode-Token" UserInfo={NSLocalizedDescription=Invalid credentials in keychain for mymailadress, missing Xcode-Token}
13-Jan-2025 12:41:04
2025-01-13 12:41:04.323 xcodebuild[44083:161713365] IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account (Error Domain=DVTServicesAccountBasedSessionErrorDomain Code=1 "Unable to log in with account ''." UserInfo={NSLocalizedFailureReason=Unable to log in with account ''., NSLocalizedRecoverySuggestion=An unexpected failure occurred while logging in (Underlying error code -1001)., DVTDeveloperAccountErrorAccount=<DVTAppleIDBasedDeveloperAccount: 0x6000037a8e80; username=''>, NSUnderlyingError=0x600003eb9920 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600003ebd290 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <23649340-3ED0-4D97-A0E7-3F46ED30721F>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
13-Jan-2025 12:41:04
"LocalDataTask <23649340-3ED0-4D97-A0E7-3F46ED30721F>.<1>"
13-Jan-2025 12:41:04
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action?clientId=XABBG36SBA, NSErrorFailingURLKey=https://developerservices2.apple.com/services/QH65B2/viewDeveloper.action?clientId=XABBG36SBA, _kCFStreamErrorDomainKey=4}}})
13-Jan-2025 12:42:05
2025-01-13 12:42:05.319 xcodebuild[44083:161713365] IDEDistribution: Failed to log in with account "(null)" while checking for an App Store Connect account (Error Domain=DVTServicesAccountBasedSessionErrorDomain Code=1 "Unable to log in with account ''." UserInfo={NSLocalizedFailureReason=Unable to log in with account ''., NSLocalizedRecoverySuggestion=An unexpected failure occurred while logging in (Underlying error code -1001)., DVTDeveloperAccountErrorAccount=
The xcode version cannot be updated due to obfuscation solution issues,
I would like to ask if you have any ideas.
thank you
Hi! So I am not really sure how all this works.
I want to use realtime data from the trains and buses in Sweden.
This is their page: https://www.trafiklab.se/api/
As I understand it I should use GTFS data which come in Protobuf format.
I think I must convert the Protobuf-data to Swift code. Not sure if this involves json.
One file I have has the extension .pb.
I tried to use this page:
https://medium.com/@andy.nguyen.1993/protobuf-in-swift-809658ecdb22
When I write this:
$ git checkout tags/1.1.1
$ swift build -c release -Xswiftc -static-stdlib
I get this error:
"error: 'swift-protobuf': the Swift tools version specification is possibly missing a version specifier; consider using '// swift-tools-version: 6.0.3' to specify the current Swift toolchain version as the lowest Swift version supported by the project"
As you understand I am really not sure what I'm doing. Maybe there is a better way?
Any help would be highly appreciated.
I have a flutter application with Firebase token and it is working in my local as expected I loaded my application to Appstore but it is not working, can anyone help me for fix the issue.
Thank you
A new app I submitted to review was rejected due to a crash.
I cannot reproduce the crash, even running it on exact the same device model used by App Review.
So I need to symbolicate the ips crash log they provided me.
Using MacSymbolicate and the archive located using Xcode Organizer I was able to partially symbolicate the crash log.
To fully symbolicate the crash log, however, according to MacSymbolicate, I would need two more symbol files, which can't be located, because they relate to system frameworks (SwiftData and _SwiftData_SwiftUI).
I have tried to follow the instructions provided on
https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report
but I had no success.
It seems to me that the instructions contained there for symbolicating using Xcode do not apply for crash logs downloaded from appstoreconnect after an App Review rejection. Also, the instructions seem to be out of date, e.g. "To symbolicate in Xcode, click the Device Logs button in the Devices and Simulators window.": This button was replaced by "Open Recent Logs", which opens what seems to be a different window (according to some online research).
Is it possible to fully symbolicate such an ips file downloaded from App Review team?
If so, how can this be achieved?
Thanks
This is how the partially symbolicated crash log looks like:
Hardware Model: iPad13,16
...
AppStoreTools: 16C5031b
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
...
OS Version: iPhone OS 18.2.1 (22C161)
Release Type: User
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000018c100e2c
Termination Reason: SIGNAL 5 Trace/BPT trap: 5
Terminating Process: exc handler [6226]
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libswiftCore.dylib 0x18c100e2c _assertionFailure(_:_:file:line:flags:) + 264
1 SwiftData 0x24fa6f3b4 0x24fa4a000 + 152500
...
14 SwiftData 0x24fa89700 0x24fa4a000 + 259840
15 _SwiftData_SwiftUI 0x250cd34e4 0x250cce000 + 21732
16 _SwiftData_SwiftUI 0x250cd1364 0x250cce000 + 13156
17 *** 0x10451f7ac closure #1 in closure #2 in closure #1 in PaymentsMonthView.body.getter (in ***) (PaymentsMonthView.swift:119) + 1324972
18 *** 0x10451ea14 closure #1 in PaymentsMonthView.body.getter (in ***) (PaymentsMonthView.swift:99) + 1321492
19 SwiftUICore 0x24fd5d304 specialized ViewBodyAccessor.updateBody(of:changed:) + 1240
20 SwiftUICore 0x24fd5cd4c closure #1 in DynamicBody.updateValue() + 600
21 SwiftUICore 0x24fd5c008 DynamicBody.updateValue() + 928
...
...
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x000000011128b208 x1: 0x0000000200000003 x2: 0x0000000000000001 x3: 0x00000001130be744
x4: 0xfffffffffe1cd413 x5: 0x0000000000000013 x6: 0x0000000000000020 x7: 0x00000000000007fc
x8: 0xfffffffe00000000 x9: 0x0000000200000003 x10: 0x0000000000000003 x11: 0x0000000000000000
x12: 0x00180080004019e0 x13: 0x00100000004017fc x14: 0x00000001046d23e0 x15: 0x00000000000001e0
x16: 0x952d0001130bde00 x17: 0x00000000020007fc x18: 0x0000000000000000 x19: 0x000000024fb661e0
x20: 0x000000011128b200 x21: 0x0000000000000000 x22: 0x000000000000000b x23: 0x000000000000001d
x24: 0x0000000000000040 x25: 0x000000024fb64790 x26: 0xf000000000000977 x27: 0x0000000000000000
x28: 0x000000024fb64750 fp: 0x000000016ba188f0 lr: 0x000000018c100e2c
sp: 0x000000016ba18820 pc: 0x000000018c100e2c cpsr: 0x60001000
far: 0x0000000000000000 esr: 0xf2000001 (Breakpoint) brk 1
Binary Images:
0x1043dc000 - 0x104633fff Locador arm64 <78fc8961d731321ba0c8f9bb051109c5> /private/var/containers/Bundle/Application/FE1C10C5-49C1-4022-860A-6C3515E2F8BB/Locador.app/Locador
0x1047fc000 - 0x104807fff libobjc-trampolines.dylib arm64e <be05652226b13a508ad193ac99fcdc9c> /private/preboot/Cryptexes/OS/usr/lib/libobjc-trampolines.dylib
0x18c0c9000 - 0x18c66afff libswiftCore.dylib arm64e <e9b1dc6b7fef3bbbb083f4e8faaa53df> /usr/lib/swift/libswiftCore.dylib
0x24fa4a000 - 0x24fb88ff7 SwiftData arm64e <90275b26954b349996ff44ada39f0358> /System/Library/Frameworks/SwiftData.framework/SwiftData
0x250cce000 - 0x250cebff8 _SwiftData_SwiftUI arm64e <d250fe30854c3f1c85fc8a89dec5d484> /System/Library/Frameworks/_SwiftData_SwiftUI.framework/_SwiftData_SwiftUI
0x24fcf8000 - 0x2508d4fff SwiftUICore arm64e <647b91f1620d3741bd708f9f26b5674b> /System/Library/Frameworks/SwiftUICore.framework/SwiftUICore
0x1ba831000 - 0x1ba874fff AttributeGraph arm64e <5eeff865ac123665a9dba9d612eb0e9f> /System/Library/PrivateFrameworks/AttributeGraph.framework/AttributeGraph
0x19220e000 - 0x1934d0fff SwiftUI arm64e <0b283f5831ae385f9c8ff128fd0e30b8> /System/Library/Frameworks/SwiftUI.framework/SwiftUI
0x1902f8000 - 0x19220dfff UIKitCore arm64e <f80c6ee450ca346f90ebbb3da9817503> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore
0x18dadc000 - 0x18e01ffff CoreFoundation arm64e <6a60be13e6573beca9acba239ae29862> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x1dacec000 - 0x1dacf4fff GraphicsServices arm64e <f4e7a885f4913721862dc57403f4d821> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x1b3d31000 - 0x1b3db413f dyld arm64e <4eb7459fe23738ce82403f3e2e1ce5ab> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? unknown-arch <00000000000000000000000000000000> ???
0x1df105000 - 0x1df13efe3 libsystem_kernel.dylib arm64e <e3965df1a3a3374a94eaf86739c5cc8e> /usr/lib/system/libsystem_kernel.dylib
0x18c6e1000 - 0x18d411fff Foundation arm64e <7274dde368d634a08e677726e1265e80> /System/Library/Frameworks/Foundation.framework/Foundation
0x2185fc000 - 0x218608ff3 libsystem_pthread.dylib arm64e <b2fe0dfa67de3d7282676c42073e0e8d> /usr/lib/system/libsystem_pthread.dylib
0x1958ce000 - 0x19594dffb libsystem_c.dylib arm64e <8d425c7257c93e54a1e1e243cbdfc446> /usr/lib/system/libsystem_c.dylib
EOF
A new app I submitted to review was rejected due to a crash.
I cannot reproduce the crash, even running it on exact the same device model used by App Review.
So I need to symbolicate the ips crash log they provided me.
Using MacSymbolicate and the archive located using Xcode Organizer I was able to partially symbolicate the crash log.
To fully symbolicate the crash log, however, according to MacSymbolicate, I would need two more symbol files, which can't be located, because they relate to system frameworks (SwiftData and _SwiftData_SwiftUI).
I have tried to follow the instructions provided on
https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report
but I had no success.
It seems to me that the instructions contained there for symbolicating using Xcode do not apply for crash logs downloaded from appstoreconnect after an App Review rejection. Also, the instructions seem to be out of date, e.g. "To symbolicate in Xcode, click the Device Logs button in the Devices and Simulators window.": This button was replaced by "Open Recent Logs", which opens what seems to be a different window (according to some online research).
Is it possible to fully symbolicate such an ips file downloaded from App Review team?
If so, how can this be achieved?
Thanks
This is how the partially symbolicated crash log looks like:
Hardware Model: iPad13,16
...
AppStoreTools: 16C5031b
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
...
OS Version: iPhone OS 18.2.1 (22C161)
Release Type: User
Report Version: 104
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000018c100e2c
Termination Reason: SIGNAL 5 Trace/BPT trap: 5
Terminating Process: exc handler [6226]
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libswiftCore.dylib 0x18c100e2c _assertionFailure(_:_:file:line:flags:) + 264
1 SwiftData 0x24fa6f3b4 0x24fa4a000 + 152500
...
14 SwiftData 0x24fa89700 0x24fa4a000 + 259840
15 _SwiftData_SwiftUI 0x250cd34e4 0x250cce000 + 21732
16 _SwiftData_SwiftUI 0x250cd1364 0x250cce000 + 13156
17 *** 0x10451f7ac closure #1 in closure #2 in closure #1 in PaymentsMonthView.body.getter (in ***) (PaymentsMonthView.swift:119) + 1324972
18 *** 0x10451ea14 closure #1 in PaymentsMonthView.body.getter (in ***) (PaymentsMonthView.swift:99) + 1321492
19 SwiftUICore 0x24fd5d304 specialized ViewBodyAccessor.updateBody(of:changed:) + 1240
20 SwiftUICore 0x24fd5cd4c closure #1 in DynamicBody.updateValue() + 600
21 SwiftUICore 0x24fd5c008 DynamicBody.updateValue() + 928
...
...
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x000000011128b208 x1: 0x0000000200000003 x2: 0x0000000000000001 x3: 0x00000001130be744
x4: 0xfffffffffe1cd413 x5: 0x0000000000000013 x6: 0x0000000000000020 x7: 0x00000000000007fc
x8: 0xfffffffe00000000 x9: 0x0000000200000003 x10: 0x0000000000000003 x11: 0x0000000000000000
x12: 0x00180080004019e0 x13: 0x00100000004017fc x14: 0x00000001046d23e0 x15: 0x00000000000001e0
x16: 0x952d0001130bde00 x17: 0x00000000020007fc x18: 0x0000000000000000 x19: 0x000000024fb661e0
x20: 0x000000011128b200 x21: 0x0000000000000000 x22: 0x000000000000000b x23: 0x000000000000001d
x24: 0x0000000000000040 x25: 0x000000024fb64790 x26: 0xf000000000000977 x27: 0x0000000000000000
x28: 0x000000024fb64750 fp: 0x000000016ba188f0 lr: 0x000000018c100e2c
sp: 0x000000016ba18820 pc: 0x000000018c100e2c cpsr: 0x60001000
far: 0x0000000000000000 esr: 0xf2000001 (Breakpoint) brk 1
Binary Images:
0x1043dc000 - 0x104633fff Locador arm64 <78fc8961d731321ba0c8f9bb051109c5> /private/var/containers/Bundle/Application/FE1C10C5-49C1-4022-860A-6C3515E2F8BB/Locador.app/Locador
0x1047fc000 - 0x104807fff libobjc-trampolines.dylib arm64e <be05652226b13a508ad193ac99fcdc9c> /private/preboot/Cryptexes/OS/usr/lib/libobjc-trampolines.dylib
0x18c0c9000 - 0x18c66afff libswiftCore.dylib arm64e <e9b1dc6b7fef3bbbb083f4e8faaa53df> /usr/lib/swift/libswiftCore.dylib
0x24fa4a000 - 0x24fb88ff7 SwiftData arm64e <90275b26954b349996ff44ada39f0358> /System/Library/Frameworks/SwiftData.framework/SwiftData
0x250cce000 - 0x250cebff8 _SwiftData_SwiftUI arm64e <d250fe30854c3f1c85fc8a89dec5d484> /System/Library/Frameworks/_SwiftData_SwiftUI.framework/_SwiftData_SwiftUI
0x24fcf8000 - 0x2508d4fff SwiftUICore arm64e <647b91f1620d3741bd708f9f26b5674b> /System/Library/Frameworks/SwiftUICore.framework/SwiftUICore
0x1ba831000 - 0x1ba874fff AttributeGraph arm64e <5eeff865ac123665a9dba9d612eb0e9f> /System/Library/PrivateFrameworks/AttributeGraph.framework/AttributeGraph
0x19220e000 - 0x1934d0fff SwiftUI arm64e <0b283f5831ae385f9c8ff128fd0e30b8> /System/Library/Frameworks/SwiftUI.framework/SwiftUI
0x1902f8000 - 0x19220dfff UIKitCore arm64e <f80c6ee450ca346f90ebbb3da9817503> /System/Library/PrivateFrameworks/UIKitCore.framework/UIKitCore
0x18dadc000 - 0x18e01ffff CoreFoundation arm64e <6a60be13e6573beca9acba239ae29862> /System/Library/Frameworks/CoreFoundation.framework/CoreFoundation
0x1dacec000 - 0x1dacf4fff GraphicsServices arm64e <f4e7a885f4913721862dc57403f4d821> /System/Library/PrivateFrameworks/GraphicsServices.framework/GraphicsServices
0x1b3d31000 - 0x1b3db413f dyld arm64e <4eb7459fe23738ce82403f3e2e1ce5ab> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? unknown-arch <00000000000000000000000000000000> ???
0x1df105000 - 0x1df13efe3 libsystem_kernel.dylib arm64e <e3965df1a3a3374a94eaf86739c5cc8e> /usr/lib/system/libsystem_kernel.dylib
0x18c6e1000 - 0x18d411fff Foundation arm64e <7274dde368d634a08e677726e1265e80> /System/Library/Frameworks/Foundation.framework/Foundation
0x2185fc000 - 0x218608ff3 libsystem_pthread.dylib arm64e <b2fe0dfa67de3d7282676c42073e0e8d> /usr/lib/system/libsystem_pthread.dylib
0x1958ce000 - 0x19594dffb libsystem_c.dylib arm64e <8d425c7257c93e54a1e1e243cbdfc446> /usr/lib/system/libsystem_c.dylib
EOF
I find that app connect is really lacking in features. I do understand there is a fair amount of complexity but come on, with the team apple has, the importance of beta testing and real world issue I find app connect very lacking.
Looks like once a tester is added you can't even edit their firstname/lastname - why! I can see changing apple id being a bit (but only a bit) of an issue, but their name?? People get married and change their last name, sometimes we do a typo and get a firstname wrong.
Also having a tester test on two devices is a real pain. If they add testflight and use redeem code and then later on add a new device one is unable to resend invite for them to use new redeem code on new device is an issue.
I have been trying to do a post request on this appstore api endpoint to be able to set availability on USA territory. However even after following the payload body I still get the error of no matching resource was included.
Here is my payload:
payload = {
data: {
attributes: {
availableInNewTerritories: true
},
relationships:{
app:{
data: { type: "apps", id: app_id }
},
territoryAvailabilities: {
data: [{
id: "#{territory_id}",
type: "territoryAvailabilities"
}]
}
},
type: "appAvailabilities"
},
included: [{
id: "#{territory_id}",
type: "territoryAvailabilities"
}]
}
and this is the api error response I get:
{
"errors" : [ {
"id" : "2c42b5cc-4.....",
"status" : "409",
"code" : "ENTITY_ERROR.RELATIONSHIP.INVALID",
"title" : "The provided entity includes a relationship with an invalid value",
"detail" : "The relationship 'territoryAvailabilities' expects an included resource with type 'territoryAvailabilities' and id 'USA' but no matching resource was included.",
"source" : {
"pointer" : "/included"
}
} ]
}
I am confused as to what the error was referring to as I added the included payload as array and the ids and type match with the territoryAvailabilities relationships as well.
Hello,
Our company's software successfully passes the notarization process when exported through Xcode Archive and compressed into a zip file. However, it fails notarization when packaged into a pkg using the Packages software (version 1.2.10), consistently returning the error "The signature of the binary is invalid." We need assistance to resolve this issue.
Here are some specific details on the signature statuses and notarization information:
xcrun stapler validation: Successful
xcrun stapler validate Maxi\ PC\ Suite.app
Processing: /Users/autel/Desktop/test11/files/Maxi PC Suite.app
The validate action worked!
pkgutil signature check: Successful
pkgutil --check-signature Maxi\ PC\ Suite.pkg
Package "Maxi PC Suite.pkg":
Status: signed by a developer certificate issued by Apple for distribution
Signed with a trusted timestamp on: 2025-01-09 08:09:17 +0000
Certificate Chain:
1. Developer ID Installer: Autel Intelligent Technology Co., Ltd. (MEXQ8HADL9)
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
B7 F7 AC 05 19 78 CB 5D 66 C1 11 95 EE C9 2E 31 B9 AA BD F5 32
E4 B6 4D 8D 0D 06 04 EE BC 1B 5A
------------------------------------------------------------------------
2. Developer ID Certification Authority
Expires: 2027-02-01 22:12:15 +0000
SHA256 Fingerprint:
7A FC 9D 01 A6 2F 03 A2 DE 96 37 93 6D 4A FE 68 09 0D 2D E1
8D 03 F2 9C 88 CF B0 B1 BA 63 58 7F
------------------------------------------------------------------------
3. Apple Root CA
Expires: 2035-02-09 21:40:36 +0000
SHA256 Fingerprint:
B0 B1 73 0E CB C7 FF 45 05 14 2C 49 F1 29 5E 6E DA 6B CA ED
7E 2C 68 C5 BE 91 B5 A1 10 01 F0 24
pkg notarization: Failed
xcrun notarytool submit Maxi\ PC\ Suite.pkg --apple-id *** --team-id *** --password *** --wait
Conducting pre-submission checks for Maxi PC Suite.pkg and initiating connection to the Apple notary service...
Submission ID received
id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d
Upload progress: 100.00% (3.42 MB of 3.42 MB)
Successfully uploaded file
id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d
path: /Users/autel/Desktop/test11/build/Maxi PC Suite.pkg
Waiting for processing to complete.
Current status: Invalid.
Processing complete
id: ccbf6330-b64a-4b42-87c0-b5db1fe25b2d
status: Invalid
Detailed notarization failure information:
xcrun notarytool log ccbf6330-b64a-4b42-87c0-b5db1fe25b2d --keychain-profile "PC_Suit_Mac"
{
"logFormatVersion": 1,
"jobId": "ccbf6330-b64a-4b42-87c0-b5db1fe25b2d",
"status": "Invalid",
"statusSummary": "Archive contains critical validation errors",
"statusCode": 4000,
"archiveFilename": "Maxi PC Suite.pkg",
"uploadDate": "2025-01-09T08:18:22.374Z",
"sha256": "0d1bd15e5c30bc890d20086de865739d01e131e34386b73ac20f8a5d52229906",
"ticketContents": null,
"issues": [
{
"severity": "error",
"code": null,
"path": "Maxi PC Suite.pkg/Maxi_PC_Suite.pkg Contents/Payload/Applications/Maxi PC Suite.app/Contents/MacOS/Maxi PC Suite",
"message": "The signature of the binary is invalid.",
"docUrl": "https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/resolving_common_notarization_issues#3087735",
"architecture": "x86_64"
}
]
}
We are looking for advice on how to resolve the error related to the invalid binary signature during the pkg notarization process.
Thank you.
I have tried all of the above options, cleaned cached data, restarted several times, did not work.
The tunnel connection failed while the system tried to connect to the device.
Domain: com.apple.dt.RemotePairingError
Code: 4
System Information
macOS Version 15.2 (Build 24C101)
Xcode 16.2 (23507) (Build 16C5032a)
iOs 18.1.1
Even if I recreate everything and register it, it does not register in xcode as shown below. No matter how many times I regenerate the certificate and profile, the same thing happens.
I have an error when I use Apple Git-154 to clone the repository:
My OS version: Sequoia 15.2
tannguyen@Mys-MacBook-Pro ~ % git -v
git version 2.39.5 (Apple Git-154)
tannguyen@Mys-MacBook-Pro ~ % git clone https://github.com/nestjs/nest.git
Cloning into 'nest'...
remote: Enumerating objects: 187515, done.
remote: Counting objects: 100% (118/118), done.
remote: Compressing objects: 100% (42/42), done.
error: inflate: data stream error (incorrect data check)10 MiB/s
fatal: pack has bad object at offset 212760331: inflate returned -3
fatal: fetch-pack: invalid index-pack output
I'm using navigator.geolocation.getCurrentPosition to retrieve the users coordinates in a PWA built with Nextjs. getCurrentPosition is called by clicking on a button. If getCurrentPosition is called afterwards, the cached value is returned. On Safari, If I refresh the page, or logout, login and call getCurrentPosition again, the getCurrentPosition error callback is called with an error code 2 - POSITION_UNAVAILABLE. After around five minutes, getCurrentPosition can be called again.
Is there some kind of throttling restriction on Safari navigator.geolocation.getCurrentPosition?
In Xcode 16.2, I am trying to add a folder by reference but I can't find the good old option 'reference files in place' in the pull down menu (only the options 'Copy files to destination' and 'Move files to destination' are present.
Is it expected?
Thanks