UNFORTUNATELY… it just happened again, with an entirely different project. I tried the “trick” of replacing the app, and it still happens.
I get the same error message I typed in months ago, and the same lockup of the problem reported.
AAron is a nice guy, but I’ve spent 38 years in the computer industry, and the old “just reinstall the software” routine is virtually always trotted out… and some times it works, and sometimes it doesn’t.
I’m STILL asking for WHERE the crash info is kept, so I can delete the trigger. (Aaron: that means that, programmatically, when an app crashes, and has a reporter feature, the issue of the crash, and the user notes about it are stored in a file on the hard drive. That way it can all be bundled up and set to you, the developer.
But if the app that does the sending ITSELF IS BUGGY, then 1) the file is never sent, and 2) because of that, the next time the software starts, the file is still there, and the buggy reporter launches itself all over again.
If that file that contains the report of the crash, and the uses “what happened” text, is NEVER removed, there is no way out of this.
I’ve written literally millions of lines of application code. I know exactly how hard (or NOT hard) it is to stick in a bit to TURN OFF bug reporters, and just simply ignore any problems. That -should- be a user preference.
If not then perhaps you have a terminal command that will turn it off?
I’ve asked and asked for a resolution to this. I’ve pleaded for SOME way to get past the bug reporter and get on with my work.
It’s not important whose fault this is. It’s not important or even relevant if it’s something in my system. NONE of that has anything to do with bypassing the bug reporter on a fresh install and fresh start of the RW software.
I’d be willing to bet $100 that one of the programmers there knows -exactly- what I’m talking about and how to get around the problem.
I’m happy playing around in the terminal; I’m happy wiht invisible files and package contents. Hell, I even know how to use (and own several hex-editors.)
I’d be -delighted- if someone there would just ASK for my help in debugging this.
There are obviously several of us with the same problem here. Can’t we do better from you folks than “It’s your fault; reinstall the software?”
[sorry for the rant, but this is getting to be not only -really- frustrating, but it’s costing me $$$ and time.]