After our upgrade to Xcode 15.3, our app compiles and builds, but when we run it on an iPhone it crashes with EXC_BAD_ACCESS (code=1, address=0x15b) upon starting.
We're using Qt and the crash occurs when we try to access our app's sqlite file with QSqlQuery::exec(). The EXC_BAD_ACCESS occurs when trying to run a SELECT or PRAGMA statement to read from the sqlite. Running an INSERT or DELETE with the exec() method does not result in an exception; we just get an error saying that the table in the command does not exist.
exec() crashes when it gets to sqlite3VdbeMemGrow in the sqlite3VdbeMemStringify call.
We're using a "solid" QSqlQuery object variable in our code, not a pointer to a QSqlQuery object, so it's not like our code is using an uninitialized pointer.
We tried the suggestion in this post that references this project's bug tracker and changed our iOS Minimum Deployment setting in Xcode from 11.0 to 13.0, but this didn't resolve the issue.
I hypothesized that perhaps the Xcode update prohibits the main thread from doing file access, but after preventing our main thread from doing any accessing of the sqlite file, we still get EXC_BAD_ACCESS (code=1, address=0x15b) from a separate thread that tries to access the sqlite file.
I hypothesized that perhaps it was a file access permission issue when I saw the app trying to use the sqlite file out of the "Documents" folder /var/mobile/Containers/Data/Application/AAC50B3C-4DCF-4122-B88A-FC631E6BB9A0/Documents. I changed the app to use a different container sub folder but that gave different errors:
QIODevice::write (QFile, "/var/mobile/Containers/Data/Application/E64A08B4-5F59-433E-9111-D503F190383F/Library/Application Support/ELD/log.txt"): device not open
which would be our app's log file. The sqlite commands all give database not open responses.
Another thread suggested downgrading Xcode, but we also got the EXC_BAD_ACCESS with Xcode 15.0.1.
Thanks for your time!
Post not yet marked as solved
Will you be able to run the full version of Xcode on the new iPad Pro M4 on IPadOS?
Post not yet marked as solved
Hi all! Do you know if there is a sample project in Swift that I can use to detect obstacles using the Ultra Wideband?
Post not yet marked as solved
when using Xcode15, we found that using Xcode 15 to access keychain may fail. Although using Xcode earlier than 15 may have same question, but the probability is higher on Xcode15. Anyone has the same question and how to fix it?
Post not yet marked as solved
I'm trying to use rvictl but here's what I run into
> rvictl
Could not get list of devices
> sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.rpmuxd.plist
Load failed: 5: Input/output error
Try running `launchctl bootstrap` as root for richer errors.
> ls /System/Library/LaunchDaemons/com.apple.rpmuxd.plist
ls: /System/Library/LaunchDaemons/com.apple.rpmuxd.plist: No such file or directory
XCode version 15.3
MacOS Sonoma 14.4.1
Apple M1 Max
Post not yet marked as solved
Hello, I'm experiencing a sad BUG. I am deaf, blind, in a wheelchair. I program in XCode via Braille display. I compile any APP in XCode, including the APP test "Hello world!" and I transfer this APP to my iPhone via USB cable or Wi-Fi. So, when I try to enter the APP, VoiceOver suddenly deactivates itself and no longer activates. I always have to turn off my iPhone and turn it on again. He only reacts with someone he sees as helping. I'm not programming in XCode, because I can't test APPS on my iPhone anymore. Help me.
Software in Mac: XCode 15.4 beta
Software MacOS: latest version;
Software in iPhone:iOS 17.5
Hardware: iPhone 14 Pro Max
The BUG happens always.
Post not yet marked as solved
My application runs smoothly in our local environment. however, we consistently encounter errors upon launch in TestFlight. Despite our efforts to update our libraries and address these issues, the problem still persists. For more detailed insight, I have attached the crash log here.
Post not yet marked as solved
I have chronic problems with the connection between Xcode and my phone.
I plug the phone in and Xcode says "Waiting for phone to unlock", but the phone is already unlocked. I try locking and unlocking it, but nothing happens.
If I can get past this problem by disconnection and reconnecting the phone a couple of times, it gets into the "downloading symbols" phase and never gets out of it.
Finally, even though I have checked the "Connect via network" option, it never works, and I can never connect unless I plug in the phone with a USB cord (yes, the phone and the computer are on the same Wifi network).
Some days this is just an annoyance, but some days (like today) I really need to test something on my phone for a customer who's waiting for it, and I cannot. The thing I'm trying to test involves sending text messages so I can't use the simulator or even an iPad. What can I do to debug this problem?
Post not yet marked as solved
This bundle is invalid. The value for key CFBundleVersion [1.0.1] in the Info.plist file must contain a higher version than that of the previously uploaded version [5]. Please find more information about CFBundleVersion at https://developer.apple.com/documentation/bundleresources/information_property_list/cfbundleversion (ID: 978303b8-eb71-4d71-9169-b0b0860fd8ec)
The issue is an error while uploading macOS version 1.0.1 to the App store. If I want to solve it simply and quickly now, do I have to skip 1.0.1 and upload version 5.0.1 right away?
I made an inquiry to Apple, but they only asked me to ask the forum or provide technical support.
I would appreciate it if you could reply even if it's not accurate. I don't know if the problem is mine or Apple's problem, so I can't solve it for a long time.
Post not yet marked as solved
if I want to document my color asset with DocC to help the development team use colors correctly in app development, how can I do it?
p.s. think about when you have to work in a team but there isn't a graphic repository, like Figma or Zeplin
Post not yet marked as solved
with the latest Xcode that runs with Mac OS 14.5 Developer Beta has messages with a time and date in them There are also some other fields of an indeterminate origin/type.
"2024-05-06 15:37:32.383996-0500 RoomPlanExampleApp[24190:1708576] [CAMetalLayerDrawable texture] should not be called after already presenting this drawable. Get a nextDrawable instead."
specifically I need to know how the string [24190:1708576] relates to a location in my application so I can act on the message. I certainly can't find the text in the "[CAMetalLayerDrawable texture]". field anywhere in the user documentation OR the Development documentation. In order for a diagnostic message to be Actionable and remedied by a user it must identify the module and source line of the initiating code and there must be accessible documentation for users to access to get an explanation of potential remedies.. This interface fails to supply enough information to diagnose the problem. The label in [CAMetalLayerDrawable texture] cannot even be found in a search of the package information attached to the Xcode Release paired with the IOS and Mac OS system releases.
Post not yet marked as solved
No metrics data found for the latest app versions with sufficient usage.
What is sufficient usage ?
Can we define sufficient usage ourself ? if Yes then how ?
https://developer.apple.com/videos/play/wwdc2020/10076/
wwwdc200 does mention factor of 5, but 5 of what ? and when where is the definition ?
Organizer -> Metrics is useless if there is no data.
If someone knows the fix please suggest.
Post not yet marked as solved
I'm trying to get my iOS app ready for distribution, but after running Product->Archive and clicking Validate App, XCode does a few steps of validation and then crashes without finishing.
Here's the top of the crash log, I can reproduce easily and get the full report if needed.
This is a blocker for me and I really need a solution.
Translated Report (Full Report Below)
-------------------------------------
Process: Xcode [93086]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 15.3 (22618)
Build Info: IDEApplication-22618000000000000~2 (15E204a)
App Item ID: 497799835
App External ID: 863955376
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2024-05-07 09:20:28.9493 +0200
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Anonymous UUID: 3BF4943C-9199-C215-F9AB-59223913BAC9
Sleep/Wake UUID: 0AFCFDE1-E734-4B4D-88F6-72BC777F81CB
Time Awake Since Boot: 650000 seconds
Time Since Wake: 2935 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: archive info plist lock
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Xcode [93086]
Application Specific Information:
com.apple.main-thread
abort() called
Application Specific Signatures:
NSInvalidArgumentException
Application Specific Backtrace 0:
0 CoreFoundation 0x000000019d59eccc __exceptionPreprocess + 176
1 DVTFoundation 0x00000001044dcbc4 DVTFailureHintExceptionPreprocessor + 388
2 libobjc.A.dylib 0x000000019d086788 objc_exception_throw + 60
3 CoreFoundation 0x000000019d4b67d0 -[__NSPlaceholderDictionary initWithObjects:forKeys:count:] + 728
4 CoreFoundation 0x000000019d4b64cc +[NSDictionary dictionaryWithObjects:forKeys:count:] + 52
5 IDEFoundation 0x0000000109a58a34 -[IDEArchiveDistributionRecord dictionaryRepresentation] + 296
6 IDEFoundation 0x0000000109a3a21c __31-[IDEArchive setDistributions:]_block_invoke + 16
7 DVTFoundation 0x00000001044d4700 -[NSArray(DVTFoundationClassAdditions) dvt_arrayByApplyingBlock:] + 224
8 IDEFoundation 0x0000000109a3a1ac -[IDEArchive setDistributions:] + 84
9 Foundation 0x000000019e624370 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKeys:count:maybeOldValuesDict:maybeNewValuesDict:usingBlock:] + 608
10 Foundation 0x000000019e64da24 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKey:key:key:usingBlock:] + 64
11 Foundation 0x000000019e667688 _NSSetObjectValueAndNotify + 284
12 IDEFoundation 0x0000000109a39fa4 __36-[IDEArchive addDistribution:error:]_block_invoke + 156
13 libdispatch.dylib 0x000000019d29a3e8 _dispatch_client_callout + 20
14 libdispatch.dylib 0x000000019d2a98d8 _dispatch_lane_barrier_sync_invoke_and_complete + 56
15 DVTFoundation 0x000000010452127c DVTDispatchBarrierSync + 148
16 DVTFoundation 0x00000001044fd024 -[DVTDispatchLock performLockedBlock:] + 60
17 IDEFoundation 0x0000000109a39dcc -[IDEArchive addDistribution:error:] + 200
18 IDEFoundation 0x00000001099e05f4 __41-[IDEDistributionValidationStep validate]_block_invoke + 116
19 DVTFoundation 0x0000000104520598 __DVT_CALLING_CLIENT_BLOCK__ + 16
20 DVTFoundation 0x0000000104520d70 __DVTSyncPerformBlock_block_invoke + 68
21 CoreFoundation 0x000000019d529a48 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28
22 CoreFoundation 0x000000019d52995c __CFRunLoopDoBlocks + 356
23 CoreFoundation 0x000000019d528dec __CFRunLoopRun + 2440
24 CoreFoundation 0x000000019d527e0c CFRunLoopRunSpecific + 608
25 HIToolbox 0x00000001a7cc3000 RunC
Post not yet marked as solved
On Xcode 15, when I launch my app on "Wait for the executable to be lauched" mode, I can't debug because Xcode simply doesn't pause at my breakpoints. They change their look and turn to dotted blue outlined.
When I hover over breakpoint Xcode shows a message:
Xcode won't pause at this breakpoint because it has not been resolved Resolving it requires that:
The line at the breakpoint is compiled.
The compiler generates debug information that is not stripped out (check the Build Settings).
The library for the breakpoint is loaded.
On the other hand, when I launch it on "Automatically" mode, everything works fine.
Does anyone have any ideas how to solve it?
Best regards.
Post not yet marked as solved
Hello, I'll be objective: when I compile any APP in my XCode and transfer the APP to my iPhone, including the test APP "Hello world!", whether via network or USB cable, when I open the APP it simply doesn't work and the iPhone crashes. Only that. My XCode is 15.3, iPhone 14 Pro Max, IOS 17.5, macOS latest version.
Post not yet marked as solved
My device information:
iMac, Apple M1, 16GB, macOS 14.4.1
My software information:
Xcode Version 15.3 (15E204a)
My problem:
I created a new project, and I just printed a line of log.When I run the project for the first time and the second time, the log can be printed correctly.But when I modified the code and ran the project for the third time, the console output was still the log of the old code.
Who has similar experience to help me?
Post not yet marked as solved
I created a prototype app with Reality Composer on an iPad. Now I would like to import the project to a Mac for further development using Xcode/Swift. How can I do this?
I am able to export a .reality or .usdz file. If I open the .reality file in Xcode I just get the playback app/scene but it does not appear to be a project that I can edit.
Post not yet marked as solved
Hi,
After upgrading to Xcode 15.3 (15E204a) AppIntents unexpectedly stopped working on iOS 16.
System error occurs when you try to run AppIntent on device with iOS 16, Shortcuts app just shows error alert.
There are errors in device's logs:
error Could not find an intent with identifier , mangledTypeName: Optional("")
It seems to be an issue with extract.actionsdata file, generated by appintentsmetadataprocessor. "mangledTypeName" parameter is empty for action descriptors, though it was fulfilled when building with Xcode 14.2 and different version of generator.
If I manually set this property in xcarchive and sign it everything works fine.
The issue is reproducible with Xcode 15.4 which is currently in beta.
Have anyone experienced this or have any solution more solid than editing metadata files after build?
Post not yet marked as solved
Hello team,
On Xcode 14.1, After building the project and when the simulator launches, it shows blank black screen. Here steps to reproduce:
build the project with fresh device. Try changing the language to French in device settings
Device should launch in French language. Instead, it loads and goes blank (blank screen)
Quit the simulator (XPC error is displayed) and rebuild the project using the same simulator device.
Build succeeds and simulator launches, but has blank screen on simulator.
Xcode is stuck at "Launching Application"
Is this a known issue?
Has anyone experienced the same? How can I fix this?
Stack (https://stackoverflow.com/questions/74315983/xcode-stuck-on-launching-application) says its a bug, so posting here for recommendations
Xcode version: 15.2, iOS deployment target 15.0
When experimenting with the new Xcode 15/new linker feature "Mergable Libraries" I came across an issue with subproject framework products.
I have a workspace with two projects.
I want to create a group framework named GroupFramework that consists of three other frameworks. FrameworkA, FrameworkB and FrameworkC.
FrameworkA and FrameworkB are in the same project as the group framework I want to create. FrameworkC is a product of another project in my workspace.
GroupFramework has all three frameworks linked in the "link binary with libraries" build phase.
GroupFramework has "Create merged binary" set to manual because I want to control which frameworks are linked. FrameworkA, FrameworkB and FrameworkC all have "Build mergeabe library" set to YES.
The application builds in both RELEASE and DEBUG.
Running in DEBUG and RELEASE
When running the application on a device in DEBUG or RELEASE it crashes with a linker error because FrameworkC can't be found on disk.
When inspecting the app binary in RELEASE I can see that FrameworkA and FrameworkB are both in the ReexportedBinary folder, but FrameworkC is nowhere to be seen.
I have tried embedding FrameworkC explicitly in the settings of the GroupFramework essentially creating an umbrella framework, and that also does not fix the issue.
I have also tried embedding FrameworkC directly into the AppTarget that will consume GroupFramework. This solves the linking issue but a new issue regarding unresolved symbols then crops up.
It appears as though the Reexporting and Merging of subproject frameworks is not working compared to a product that exists in the same project or at least may require a lot more manual configuration which is not currently documented anywhere. If this is the case, it could be very problematic when trying to adopt mergeable libraries in multi-project workspaces.
criegel.