On Oct 27, 2020, at 00:54:40, Rob Petrovec wrote:
>
> While I agree this would be a good thing to have, I don’t see how Xcode
> could find the dSYM to use given that they are typically ephemeral. The dSYM
> is tied to the build. So if you build your project twice you will have two
> di
If you upload your build (iOS) to the iTunes connect, I do believe that the
dSym goes up as well.
Look at the build script for Crashlytics. It makes sure to upload your dSyms
and does the symbolicating for iOS apps.
The process already exists with these and other crash tracking tools.
It’s pr
> On Oct 26, 2020, at 10:00 PM, Steven Mills via Cocoa-dev
> wrote:
>
>
>> On Oct 26, 2020, at 17:49:59, James Walker via Cocoa-dev
>> wrote:
>>
>> I don't see any "Download Debug Symbols" in the Organizer. I don't think it
>> exists for macOS apps.
>>
>> However, one can right-click on
> On Oct 26, 2020, at 17:49:59, James Walker via Cocoa-dev
> wrote:
>
> I don't see any "Download Debug Symbols" in the Organizer. I don't think it
> exists for macOS apps.
>
> However, one can right-click on an archive and select "Show In Finder", then
> once in Finder right-click again a
On 10/26/20 3:31 PM, Alex Zavatone via Cocoa-dev wrote:
As a note to Jens’s tip, it’s important to keep the .dSWM files for your
releases so that you can symbolicate your crash logs. Crashlytics does this
for you, but the debug symbols are stripped from released builds to try and
prevent peop
As a note to Jens’s tip, it’s important to keep the .dSWM files for your
releases so that you can symbolicate your crash logs. Crashlytics does this
for you, but the debug symbols are stripped from released builds to try and
prevent people from reverse engineering your code and to make the exec
Starting with Gabriel’s comment.
We can see that at line 2, we have this.
NSCFString characterAtIndex:
And on line 1, we have the thrown exception.
If I’m correct, the assumption here is thatthe operation is trying to get the
first character of a a string at index 0 and there isn’t any, so the
> On Oct 26, 2020, at 3:01 PM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> Is it possible to determine the exact line in the source code where the error
> occurred?
The "+ " thing in each stack line is the byte offset from the start of the
function, in the machine code. Not super useful
Line 7 appears to show your app allocating an array with one of its objects
being nil.
--
Gary L. Wade
http://www.garywade.com/
> On Oct 26, 2020, at 3:02 PM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
> From a user, I received a log file that contains an error (see below)
> and a stack trace
From a user, I received a log file that contains an error (see below)
and a stack trace of my macOS app.
Is it possible to determine the exact line in the source code where the error
occurred?
Best regards, Gabriel
Encl:
excerpt from log.
"ArtSaverApp" is my macOS app.
2020-10-23 10:47:30.4
10 matches
Mail list logo
