Crash:
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Subtype: KERNINVALIDADDRESS
Termination Reason: Namespace SIGNAL, Code 0xb
In spite of the copious amounts of logging I'm performing here, I am still running into issues with this constantly.
At least tell me the line of code where the crash began or something remotely related to my own code, as the watchOS logs from these crashes, are about as useful, as a miniature umbrella in monsoon.
There is a vague reference to AVAudioSession Notify Thread inside the error message, but as far as the available examples I have been able to find from
copious amounts of research, I am using the
setActive functions correctly.
Do they need to be run on the main thread only or am I missing anything else?? Please update your docs, if this isn’t the case.
This ultimately and inevitably crashes the app, and due to this issue, it causes your already barely usable installer for watch OS, which has now plagued watchOS since its inception, with no improvement in site, to somehow perform even more unreliably than it already does.
Building for watchOS, had quickly become an exercise in insanity, as I have to spend so much of my day, waiting for your broken watch OS compiler to fail.
Out of every successful install of a watch OS update pushed from XCode, there are 5-10, and several device restarts required in between on most days. This is really bad, to put it, as nicely as I can.
If you wish to pay for all the development time I’m wasting here, I will begin sending you bills, as I have reported this specific issue, dozens of times now, to never get a single response in relation to it.
Either that, or I can sue you, for ***** negligence and false advertisement, but as I would much prefer not to waste anyone’s time here, as I want to keep building apps to
make our world better, just fix your software please. Thank you!
I don’t have any desire to make this a legal issue, but I am so tired, of having to make excuses, for your teams piss poor work.
I am more than happy to work with them, if they decide to get off their butts here. But asking for logs, and never responding, or only with, could not replicate issue, is opposite of that.
I could write emails saying, could not replicate issue to all my customers too, and nothing will ever get fixed, but this is not the type of person I am, and not how problems are ever resolved. Do something!!!
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Subtype: KERNINVALIDADDRESS
Termination Reason: Namespace SIGNAL, Code 0xb
In spite of the copious amounts of logging I'm performing here, I am still running into issues with this constantly.
At least tell me the line of code where the crash began or something remotely related to my own code, as the watchOS logs from these crashes, are about as useful, as a miniature umbrella in monsoon.
There is a vague reference to AVAudioSession Notify Thread inside the error message, but as far as the available examples I have been able to find from
copious amounts of research, I am using the
setActive functions correctly.
Do they need to be run on the main thread only or am I missing anything else?? Please update your docs, if this isn’t the case.
This ultimately and inevitably crashes the app, and due to this issue, it causes your already barely usable installer for watch OS, which has now plagued watchOS since its inception, with no improvement in site, to somehow perform even more unreliably than it already does.
Building for watchOS, had quickly become an exercise in insanity, as I have to spend so much of my day, waiting for your broken watch OS compiler to fail.
Out of every successful install of a watch OS update pushed from XCode, there are 5-10, and several device restarts required in between on most days. This is really bad, to put it, as nicely as I can.
If you wish to pay for all the development time I’m wasting here, I will begin sending you bills, as I have reported this specific issue, dozens of times now, to never get a single response in relation to it.
Either that, or I can sue you, for ***** negligence and false advertisement, but as I would much prefer not to waste anyone’s time here, as I want to keep building apps to
make our world better, just fix your software please. Thank you!
I don’t have any desire to make this a legal issue, but I am so tired, of having to make excuses, for your teams piss poor work.
I am more than happy to work with them, if they decide to get off their butts here. But asking for logs, and never responding, or only with, could not replicate issue, is opposite of that.
I could write emails saying, could not replicate issue to all my customers too, and nothing will ever get fixed, but this is not the type of person I am, and not how problems are ever resolved. Do something!!!