Posts

Post not yet marked as solved
12 Replies
I've reached out to our WWDC contact to see if there's any possibility to revert this server-side change to the list from before June 7. We're calling font loading code on initialize so this issue results in a crash-on-launch for products using our SDK that have been using the downloadable fonts feature in the past. To repeat: This is a regression Apple introduced server-side onto existing, working code. This should be reverted.
Post not yet marked as solved
18 Replies
I ran into this error while working on CI automation. Read steipete.com/posts/apple-silicon-mac-mini-for-ci for details. The main fix was that the user you're using here for must be LOGGED IN. Just ssh'ing into won't be enough and you run into either this error or error 125.
Post marked as solved
6 Replies
I wrote a workaround to increase the default autosave timer: https://gist.github.com/steipete/dbb6b26c9c6bc5d67d5c1baa44e00b5f
Post marked as solved
13 Replies
If you are looking for a solution that disables keyboard avoidance for UIHostingController and you're cool with shipping something slightly terrible, here you go: https://gist.github.com/steipete/da72299613dcc91e8d729e48b4bb582c
Post not yet marked as solved
37 Replies
The warning pops up in the linking stage. if we use LTO, it's printed once, else it's printed about 30 times.There's no info as to what file it is being referenced to. Is there any logging available where we could get more data out of it?The error is part of the PSPDFKit SDK - it's a huge project, sharing would be difficult. If there's anything else I can do to help, let me know.Core definitely uses goto if you mean that as named labels.
Post not yet marked as solved
37 Replies
We see a similar issue. Reported as FB7644250'++crypto' is not a recognized feature for this target (ignoring feature) '++crypto' is not a recognized feature for this target (ignoring feature) '++crypto' is not a recognized feature for this target (ignoring feature) '++crypto' is not a recognized feature for this target (ignoring feature) !dbg attachment points at wrong subprogram for function !55928 = distinct !DISubprogram(name: "__hidden#4184_", scope: !55112, file: !55112, line: 388, type: !19444, scopeLine: 388, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !16201) %823* (%825*, i8*, i64)* @"\01__hidden#4184_" br i1 %36, label %41, label %37, !dbg !55955, !llvm.loop !55957 !55958 = !DILocation(line: 918, column: 5, scope: !55959, inlinedAt: !55961) !55962 = distinct !DISubprogram(name: "__hidden#4184_", scope: !55112, file: !55112, line: 388, type: !19444, scopeLine: 388, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !55960) !55962 = distinct !DISubprogram(name: "__hidden#4184_", scope: !55112, file: !55112, line: 388, type: !19444, scopeLine: 388, flags: DIFlagPrototyped | DIFlagAllCallsDescribed, spFlags: DISPFlagLocalToUnit | DISPFlagDefinition | DISPFlagOptimized, unit: !55960) ld: warning: Invalid debug info found, debug info will be stripped