4 ms·

I think Linux users will try to help themselves, will check for the application output, find the logs, ask for help and help each other to troubleshoot. I made

I think Linux users will try to help themselves, will check for the application output, find the logs, ask for help and help each other to troubleshoot. I made an app for Windows, and it was hard to explain the user how to find the log file in %appdata% , after a few support cases I just made a wizard for the users to use it and send the logs to us because it was to hard for them to find and submit a log file.

lawlessone 3y ago
>after a few support cases I just made a wizard for the users to use it and send the logs to us because it was to hard for them to find and submit a log file. There must generic libraries for this? Whats the standard way to do it? Do they get sent as email? as Post request to a server? or does it create a ticket or github report?
- simion314 3y ago
  It was an old app using AdobeAIR, it worked like this 1 I collect the logs data, soem are generated by the app like OS, app version, app logs but I think there was a runtime log file 2 I would show the user in a big text area what data will be sent, so the user can see exactly what will be sent, and redact something if he wishes, maybe say a username or string in a file path 3 I had a single PHP file on a server that would receive the data and create a new ticket and attach the data to it. The app can't make the ticket directly because we did not want to put our secret API keys for the ticket service in the app. We already had a server with PHP on it for our blog so we just added a single , super simple PHP file, no dependencies, no frameworks, no tools. 4 I get the notification from the ticket /bugs system and fix the bug if possible. AdobeAIR was a managed runtime similar with Java JVM so there were not many crashes and when they were the stack traces were clear and point to the source of the problem. The only problem we had was with the embedded webkit component, that could crash sometime and produce the usual c/C++ type of errors and there was nothing we can do about those sicne it was not our code.
jwells89 3y ago
In my mind that’s a good feature to build in anyway. Even as a technically capable individual and software dev, I’m more likely to send in bug reports if I don’t have to go digging for logs. Path of least resistance and all that…
- simion314 3y ago
  >In my mind that’s a good feature to build in anyway. Even as a technically capable individual and software dev, I’m more likely to send in bug reports if I don’t have to go digging for logs. Path of least resistance and all that… I agree , and to get nice features like this IMO is to have the developers work on tech support , have the devs chat with the suer, then they see how hard it is for them to find the logs , or even tell you the version of the OS or the app- then the "lazy" devs will want toa void wasting the tiem explaining the user again how to find the info and make a GUI for it.

lawlessone 3y ago

>after a few support cases I just made a wizard for the users to use it and send the logs to us because it was to hard for them to find and submit a log file. There must generic libraries for this? Whats the standard way to do it? Do they get sent as email? as Post request to a server? or does it create a ticket or github report?

simion314 3y ago
It was an old app using AdobeAIR, it worked like this 1 I collect the logs data, soem are generated by the app like OS, app version, app logs but I think there was a runtime log file 2 I would show the user in a big text area what data will be sent, so the user can see exactly what will be sent, and redact something if he wishes, maybe say a username or string in a file path 3 I had a single PHP file on a server that would receive the data and create a new ticket and attach the data to it. The app can't make the ticket directly because we did not want to put our secret API keys for the ticket service in the app. We already had a server with PHP on it for our blog so we just added a single , super simple PHP file, no dependencies, no frameworks, no tools. 4 I get the notification from the ticket /bugs system and fix the bug if possible. AdobeAIR was a managed runtime similar with Java JVM so there were not many crashes and when they were the stack traces were clear and point to the source of the problem. The only problem we had was with the embedded webkit component, that could crash sometime and produce the usual c/C++ type of errors and there was nothing we can do about those sicne it was not our code.

jwells89 3y ago

In my mind that’s a good feature to build in anyway. Even as a technically capable individual and software dev, I’m more likely to send in bug reports if I don’t have to go digging for logs. Path of least resistance and all that…

simion314 3y ago
>In my mind that’s a good feature to build in anyway. Even as a technically capable individual and software dev, I’m more likely to send in bug reports if I don’t have to go digging for logs. Path of least resistance and all that… I agree , and to get nice features like this IMO is to have the developers work on tech support , have the devs chat with the suer, then they see how hard it is for them to find the logs , or even tell you the version of the OS or the app- then the "lazy" devs will want toa void wasting the tiem explaining the user again how to find the info and make a GUI for it.