Robertos wrote: ↑Tue Jul 30, 2019 3:02 pm
my issue was posting tweets loop using media token and I did post logs for that issue. But now everything is mumble jumble and I can't isolate the problem that's why I don't want upload logs (I actually can but that will not help you I guarantee).
You did, and I thought I found the issue, could replicate and it was fixed (and is fixed). However you report it is not. Thus I misidentified the issue but fixed something else. With logs again of the latest update, we have closed a possible avenue of where your actual issue is being caused from, so perhaps the next fix will resolve the base issue.
Sometimes issues are not single but a chain. This fails which causes this and causes this. Until each step is found and fixed the root cause remains hidden.
But if I were you ill start from here ( you don't need logs for this) make new acc import in TD try to do anything and you'll be blocked/captcha phone in no time. than important part when you try to open acc in session browser you'll get something like this
https://prnt.sc/om1j8u
Respectfully, you are not me and I have infinite more experience debugging, fixing, identifying issues than anyone. No one knows the software more thoroughly than me. Not trying to be cocky, this is just a fact (and probably goes without saying as it would be worrying if this was not the cause)
When I ask for specific information, even if you (customer) doesn't understand why, there are good reasons. I don't mean to be rude here, just trying to be absolutely clear. For example, when you go to a mechanic with a problem with a car, you would not expect the mechanic to listen to some ones opinion who doesn't know about engines. Or if they ask for information refuse to provide it because in your less knowledgeable opinion they don't need it. They do. That is why they asked.
Additionally, if an issue is effecting just a single user and that user alone seems capable of generating the issue, we have a choice. The user can perform the action to generate me the logs in 2 minutes. Or I can spend 1-2 hours GUESSING how to replicate their issue, because I am not performing things in the exact way as the user (or more often than not, the user forgets to tell me a crucial part of what they are doing that is causing it).
If the user is not prepared to provide the information, I am not wasting my time to look. Fact is, I do not have time to spend 1-2 hours hunting for a random issue effecting one user if the user cannot be bothered to provide the requested information when it is trivial for them to replicate.
Fact is, I have spent quite a lot of time now, trying to explain to you why the information I request is required. Which is the very definition of time wasted. If you had just submitted the logs, these 10-15 minutes probably would have allowed me to find the bug and get you an update out.
tldr;
Just provide me with the information I require please. I can stop wasting time. You can get your fix. It is win win. Otherwise, we can wait for someone else at some point to cause the same issue, hopefully they provide the information and the fix gets incorporated to a future build
