search

unfoldingWord-dev / ts-desktop

translationStudio Desktop App
http://ufw.io/ts
Other
41 stars 29 forks source link

OSX v9.1 - Cannot send feedback #701

Closed cckozie closed 8 years ago

cckozie commented 8 years ago

After receiving an error when attempting to delete a project, I used the Feedback option to report the problem. When I came to Gitthub to add a comment to the feedback issue, I found that it didn't exisit here. The app indicated that the feedback had been successfully sent. I tried again later without having closed the app and it did work. Not sure if this info is related or not: image

da1nerd commented 8 years ago

@tjklemz did you have the private config file?

tjklemz commented 8 years ago

RE: the error. It looks like this is due to the "Developer Tools" button not being updated to use the new (internal) Electron API. It's a bug, but I don't think it's related, although it may have produced side-effects. IOW, it should be its own Github Issue.

@neutrinog yeah, I have the private config file which is up to date.

@cckozie I was able to submit several bug reports (all with the word Koz in them). The very first one I tried did not show up on Github. (It was titled "Koz finds all our problems".) I can't for the life of me find replicate the issue. I deleted the cache and everything.

What I can do is this: When the user submits feedback and it's successful, we get a URL to the Issue back. I can check to see if this exists; if not, I'll display the error.

cckozie commented 8 years ago

I had a second instance of the feedback not appearing on github. This one was also sent immediately after having received another error message in tS.

cckozie commented 8 years ago

9.1 build 23 I uploaded a project with no shared history to force an error message. I then tried to send feedback and got this message. At least now I am warned that it didn't work:) When I tried again, it did work. I then did the same process a second time, and this time the feedback was send on the first try. image

cckozie commented 8 years ago

It looks like I can make it fail consistently by attempting to delete a project from 9.1 build 22 that refuses to be deleted, and then try to send feedback. Here's what the console is showing: image

cckozie commented 8 years ago

I'm going to pass this and create a new issue (732) that references it so we can possibly clean it up later.

tjklemz commented 8 years ago

If a project got locked in build 22, there's no way to unlock it, even from Finder. Build 23 should not lock a project, though. (We tested fairly thoroughly.)

Hope that makes sense.

On Jul 7, 2016, at 1:52 PM, cckozie notifications@github.com wrote:

It looks like I can make it fail consistently by attempting to delete a project from 9.1 build 22 that refuses to be deleted, and then try to send feedback. Here's what the console is showing:

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.