I am trying to upload my app to AppStore using Xcode. The app uses widgets, and after archiving the app, I run the validation. It reports two errors.
Invalid directory. The bundle Payload/……/…WidgetExtension.appex is not contained in a correctly named directory. It should be under "Plugins".
CFBundleIdentifier Collision. There is more than one bundle with the CFBundleIdentifier value '…widget' under the iOS application.
I suspect that the two are linked issues, and that whilst trying to debug the widget in a simulator I may have duplicated any entry somewhere in the settings, but I am not clear where to look, as widget appears in several places, to fix the issue - info.plist, Build settings, General tab, other?
The widget also appears in the 'Products' list along with the app. I am not sure if the widget should be there, and if not how to remove it from the 'Products' list, but still make it available in the app.
Post not yet marked as solved
Hey there,
My XCode project keeps crashing (I'm still learning how to use it, literally crashes after I make the simulator run a text on the screen).
It just says my mac isn't compatible with the program.
I tried everything: I have downloaded the XCode version that's compatible with my Mac, I updated the Mac to the latest version, reinstalled XCode, deleted the project, and started a new one. I don't know what I should do by now.
I have a project to hand in late May and I need it to run :(
Please help!!
Post not yet marked as solved
I'm trying to debug a couple of crash reports for a Mac Catalyst app and seem to be unable to symbolicate my crash reports. In the Xcode Organizer, I see unsymbolicated lines for my app, despite having the original archive for the build in question. A search for the relevant dSYM (using the process from https://developer.apple.com/documentation/xcode/adding-identifiable-symbol-names-to-a-crash-report#Locate-a-dSYM-Using-Spotlight) yields no results.
Unlike iOS builds, the "Download dSYMs" button isn't present in the organizer, nor is the option to download dSYMs from App Store Connect. I assume this is because macOS apps don't use bitcode.
The app's Debug Information Format is set to DWARF with dSYM File.
Has anyone else run into this issue? Any ideas about how I can symbolicate the crash logs?
Post not yet marked as solved
I created a new app in the App Store and when i upload a new build it doesnt appear in the testFlight tab (see image).
But when i tried to upload the same bundle it shows me an error that a bundle was allready uploaded.
Post not yet marked as solved
I am a Window user, I don't have MacOS. So to participate in the challenge, which tool (IDE, etc) is recommended for Window to build the app? Thanks!
Post not yet marked as solved
Hi,
In Xcode organiser we are seeing below crash as the top most crash. We could not conclude anything with the call stack that is available. This crash is bumping our crash rates in app store connect significantly. Can someone help to figure out the root cause for this crash?
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001fc4e9b78 __pthread_kill + 8
1 libsystem_pthread.dylib 0x0000000235b083bc pthread_kill + 268 (pthread.c:1668)
2 libsystem_c.dylib 0x00000001cfcb444c __abort + 128 (abort.c:155)
3 libsystem_c.dylib 0x00000001cfc5c528 abort + 180 (abort.c:126)
4 libc++abi.dylib 0x00000001dd8e9b7c abort_message + 132 (abort_message.cpp:78)
5 libc++abi.dylib 0x00000001dd8d99c4 demangling_terminate_handler() + 336 (cxa_default_handlers.cpp:71)
6 libobjc.A.dylib 0x00000001dd7e4c98 _objc_terminate() + 160 (objc-exception.mm:704)
7 UnityFramework 0x00000001077acab0 CPPExceptionTerminate() + 496 (BSG_KSCrashSentry_CPPException.mm:192)
8 libc++abi.dylib 0x00000001dd8e8f18 std::__terminate(void (*)()) + 20 (cxa_handlers.cpp:59)
9 libc++abi.dylib 0x00000001dd8e8eb4 std::terminate() + 64 (cxa_handlers.cpp:88)
10 libdispatch.dylib 0x00000001c47e0a40 _dispatch_client_callout + 40 (object.m:563)
11 libdispatch.dylib 0x00000001c47e44e0 _dispatch_block_invoke_direct + 264 (queue.c:501)
12 FrontBoardServices 0x00000001d6cdac70 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 48 (FBSSerialQueue.m:157)
13 FrontBoardServices 0x00000001d6cda040 -[FBSSerialQueue _targetQueue_performNextIfPossible] + 220 (FBSSerialQueue.m:181)
14 FrontBoardServices 0x00000001d6cde700 -[FBSSerialQueue _performNextFromRunLoopSource] + 28 (FBSSerialQueue.m:194)
15 CoreFoundation 0x00000001c4b9bf04 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1972)
16 CoreFoundation 0x00000001c4bacc90 __CFRunLoopDoSource0 + 208 (CFRunLoop.c:2016)
17 CoreFoundation 0x00000001c4ae6184 __CFRunLoopDoSources0 + 268 (CFRunLoop.c:2053)
18 CoreFoundation 0x00000001c4aebb4c __CFRunLoopRun + 828 (CFRunLoop.c:2951)
19 CoreFoundation 0x00000001c4aff6b8 CFRunLoopRunSpecific + 600 (CFRunLoop.c:3268)
20 GraphicsServices 0x00000001e0b99374 GSEventRunModal + 164 (GSEvent.c:2200)
21 UIKitCore 0x00000001c7464e88 -[UIApplication _run] + 1100 (UIApplication.m:3511)
22 UIKitCore 0x00000001c71e65ec UIApplicationMain + 364 (UIApplication.m:5064)
23 UnityFramework 0x0000000106054c9c -[UnityFramework runUIApplicationMainWithArgc:argv:] + 108 (main.mm:124)
24 MyGame 0x0000000104c916a0 main + 22176 (main.mm:28)
25 dyld 0x000000010567dce4 start + 520 (dyldMain.cpp:879)
[2022-03-29_20-00-15.8116_-0700-583a4bdd5502a8b86aae9cb5839c125273fdb427.crash](https://developer.apple.com/forums/content/attachment/eccc16fc-dc3b-4c62-962b-e3aa27e91418)
Post not yet marked as solved
I spent many hours to figure out why my app is now other item not the iOS app
you will see the Distribute Content instead of Distribute App
Version and Identifier are now gone
I test it on Xcode 13.3
the last archive you will see in the image is the one that Creation Date is 3 Apr 2022 17:55
I try to build with the previous version (Xcode 13.2.1)
The error appears Package.resolved file is corrupted or malformed
I delete the Package.resolved
Then the error is gone
I try to archive again and it works
Creation Date is 3 Apr 2022 18:30
The problem seems to occur when using an older Xcode project opened with the current version of Xcode (13.3).
Post not yet marked as solved
sudo python3 /Applications/Xcode.app/Contents/SharedFrameworks/CoreSymbolicationDT.framework/Versions/A/Resources/CrashSymbolicator.py 38.json -d 38.app.dSYM -o result.txt
Run this command, i got the error: Crash log is missing bug_type field. Stopping symbolication.
Thanks.
Post not yet marked as solved
Hello world!
It's my first post. I'm learning to develop by myself and now I face to an app crash with Thread 1: "must pass a class of kind UITableViewCell".
I don't know what I have to do.
I also face some problems in the log in and log out with the simulator it didn't go to to the desired page. I shared the codes below. I can't go further before fixing this. Thanks a lot!. I'll be very reactive to your answers. Have a nice day!
import UIKit
@main
# class AppDelegate: UIResponder, UIApplicationDelegate { **Thread 1: "must pass a class of kind UITableViewCell" **
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
FirebaseApp.configure()
return true
}
// MARK: UISceneSession Lifecycle
func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration {
return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
}
func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>) {
}
}
I'm almost sure that the problem is in the SettingsViewController but with my level it's not obvious yet.
struct SettingCellModel {
let title: String
let handler: (() -> Void)
}
/// View Controller to show user settings
final class SettingsViewController: UIViewController {
private let tableView: UITableView = {
let tableView = UITableView(frame: .zero,
style: .grouped)
tableView.register(UITableViewCell.self,
forCellReuseIdentifier: "cell")
return tableView
}()
private var data = [[SettingCellModel]]()
override func viewDidLoad() {
super.viewDidLoad()
configureModels()
view.backgroundColor = .systemBackground
view.addSubview(tableView)
self.tableView.dataSource = self
self.tableView.delegate = self
}
override func viewDidLayoutSubviews() {
super.viewDidLayoutSubviews()
tableView.frame = view.bounds
}
private func configureModels() {
let section = [
SettingCellModel(title: "Log Out") { [weak self] in
self?.didTaplogOut()
}
]
data.append(section)
}
private func didTaplogOut() {
let actionSheet = UIAlertController(title: "Log Out",
message: "Are you sure you want to log out?",
preferredStyle: .actionSheet)
actionSheet.addAction(UIAlertAction(title: "Cancel",
style: .cancel,
handler: nil))
actionSheet.addAction(UIAlertAction(title: "Log Out",
style: .destructive,
handler: { _ in
AuthManager.shared.logOut(completion: { success in
DispatchQueue.main.async {
if success {
// present log in
let loginVC = LoginViewController()
loginVC.modalPresentationStyle = .fullScreen
self.present(loginVC, animated: true) {
self.navigationController?.popToRootViewController(animated: false)
self.tabBarController?.selectedIndex = 0
}
}
else {
// error occured
fatalError("Could not log Out user")
}
}
})
}))
actionSheet.popoverPresentationController?.sourceView = tableView
actionSheet.popoverPresentationController?.sourceRect = tableView.bounds
present(actionSheet, animated: true)
}
}
extension SettingsViewController: UITableViewDelegate, UITableViewDataSource {
func numberOfSections(in tableView: UITableView) -> Int {
return data.count
}
func tableView(_ tableView: UITableView, numberOfRowsInSection section: Int) -> Int {
return data[section].count
}
func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
let cell = tableView.dequeueReusableCell(withIdentifier: "cell", for: indexPath)
cell.textLabel?.text = data[indexPath.section][indexPath.row].title
return UITableViewCell()
}
func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
tableView.deselectRow(at: indexPath, animated: true)
// handle cell selection
}
}
Post not yet marked as solved
Currently working on a project these past couple of days but today when I opened Xcode and selected my project it would not display my stimulater phone and would keep refreshing showing the last successful build was sometime yesterday.
Post not yet marked as solved
This is a Unity APP that uses the Apple Lidar camera to record 3D Human movement. Was looking for an extra set of eyes to review the logs.
When running the App we have about 300 MB of free memory on the IPAD Pro 8 GB. The Crash logs are consistent. Is this a memory resource issue? Could we extend the memory to beyond 5 GB to help with this issue?
Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
VM - pmap_enter failed with resource shortage
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000104 x1: 0x0000000000000000 x2: 0x0000000000008400 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x00000000000000a0 x6: 0x0000000000000000 x7: 0x0000000000000000
x8: 0x000000016f064098 x9: 0x0000000000008401 x10: 0x0000000130421820 x11: 0x0000000000000002
x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000001
x16: 0x0000000000000131 x17: 0x0000000000000000 x18: 0x000000013dd2486c x19: 0x0000000130421808
x20: 0x0000000130421848 x21: 0x00000001010b4660 x22: 0x0000000000000000 x23: 0x0000000000000000
x24: 0x0000000000008400 x25: 0x0000000000008401 x26: 0x0000000000008500 x27: 0x00000000000003e8
x28: 0x00000000000f4240 fp: 0x000000016f064110 lr: 0x00000001f2e3a254
sp: 0x000000016f064080 pc: 0x00000001b973df90 cpsr: 0x60001000
esr: 0x56000080 Address size fault
crashlog.crash
Post not yet marked as solved
When an application is frequently killed and restarted, it may crash without display its launchScreen page. This situation only exit on iOS 15 or above system device.
I have try to delete all the code but the appDelegate, only show "Hello World" in a blank viewController. But the app still crash again.
The probability of this situation is not hight, maybe once in a dozen, maybe happen every few times.
Anybody can help me solve this problem, many thanks!
Post not yet marked as solved
I am getting this crash from crash report some times "pmap_enter failed with resource shortage". and there's no description about error.
It happens on main with "SIGKILL"
Here is crash log. Can you help me with this?
Hardware Model: iPhone11,6
Process: avie-ios [14566]
Path: /private/var/containers/Bundle/Application/avie-ios.app/avie-ios
Identifier: AvieAIApp
Version: 2.0 (4)
AppStoreTools: 13C90b
AppVariant: 1:iPhone11,6:15
Beta: YES
Code Type: ARM-64 (Native)
Role: Non UI
Parent Process: launchd [1]
Coalition: AvieAIApp [1470]
Date/Time: 2021-12-31 17:00:50.1259 +0100
Launch Time: 2021-12-31 17:00:46.3168 +0100
OS Version: iPhone OS 15.0.2 (19A404)
Release Type: User
Baseband Version: 4.00.00
Report Version: 104
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Kernel Triage:
VM - pmap_enter failed with resource shortage
VM - Fault was interrupted
VM - Fault was interrupted
Thread 0 name:
Thread 0 Crashed:
0 avie-ios 0x000000010243c598 type metadata accessor for SuggestionSettings + 0 (<compiler-generated>:0)
1 libswiftCore.dylib 0x000000018700a190 (anonymous namespace)::DecodedMetadataBuilder::createBoundGenericType(swift::TargetContextDescriptor<swift::InProcess> const*, __swift::__runtime::llvm::ArrayRef<swift::TargetMetadata<swift::InProc... + 332 (Metadata.h:3806)
2 libswiftCore.dylib 0x0000000187005070 swift::Demangle::__runtime::TypeDecoder<(anonymous namespace)::DecodedMetadataBuilder>::decodeMangledType(swift::Demangle::__runtime::Node*) + 2072 (MetadataLookup.cpp:1391)
3 libswiftCore.dylib 0x000000018700534c swift::Demangle::__runtime::TypeDecoder<(anonymous namespace)::DecodedMetadataBuilder>::decodeMangledType(swift::Demangle::__runtime::Node*) + 2804 (TypeDecoder.h:976)
Post not yet marked as solved
I have tried everything. Unplug, plug, connect, forget connection, resetting iPhone, re-installing Xcode.
Tried everything listed in this stack overflow question
Let it alone for 24 hours and nothing.
Tried with an Iphone se 2020 and it runs perfectly, but on my iPhone 7 nothing happens besides being stuck on "making iPhone ready for development"
Ios version = 15.4
Xcode version = 13.3
Mac version = monterey 12.3
Notes:
On Xcode it shows 2 equal messages "Making iPhone de Gustavo ready for development" every time that I connect
iPhone 7 doesn't show "developer" option on settings, but iPhone SE shows.
Stack overflow question
Post not yet marked as solved
We have some crash which we cannot reproduce in our builds.
I can see the one of this crashes in TestFlight and want to research it.
I click "open in Xcode" in TestFlight. The crash is supposed to be opened in Xcode's organizer. But the crash opened by Xcode has another build number.
I know I can list crashes by the small control on the bottom of the organizer. There is no one crash with the same build number that noted in TestFlight. So it's look like crash never downloaded to the Xcode.
It looks like for some reason Xcode does not see crashes listed in TestFlight.
I've also check all crashes Xcode knows about. It looks like Xcode does not see the big part of crashes listed in TestFlight.
What could it be?
Post not yet marked as solved
crashlog.crash
feedback.json
Post not yet marked as solved
Hey all,
So I've built my game in Unity, exported to Xcode, built, tested, archived and sent to Apple. Goes through all the processes and most importantly; Xcode shows the success screen and says it was sent to Apple for distribution.
After this step, nothing. Just nothing. No e-mail received about processing, build does not show up in Appstore Connect (including test flight) or anywhere frankly. Checked the Identifier, account and everything multiple times already.
I tried to send the build again both through Xcode and Transporter but both of them give the error saying redundant binary has been sent and the build is already in there.
Also tried different build codes to just see if it was a one time thing but no, 5 different builds sent, none of them show up anywhere.
Any ideas that I can follow to solve this? :)
Post not yet marked as solved
Hi. my friends iphone is in a constant loop ive looked into some of the stuff about panic codes just wondering if someone could tell me the best way to fix it
Hi
We're trying to publish an app build to Testflight. We've successfully done the build, but when we archive the build, we get this error: error itms-90168 null.
We are able to upload the build, it then SEEMS like the build is successfully archived. Then we validate the app, which is successful, but then when we click distribute, it gives an error: "error itms-90168 null"
We've been struggling with this for quite a while and have tried things to solve the issue, but we haven't been successful this far. It's difficult to try figure out what is wrong, as the error message merely says "Null" instead of giving specific details.
Post not yet marked as solved
I want to download the organizer data and upload it to my own platform. Is there any relevant data interface?