You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Reproducing the problem is literally 2 cmds and all the required info was in the bug summary. The dev didn't need more data. They weren't even the dev tasked with fixing the problem. The dev didn't read my bug report, they saw I didn't attach logs and immediately closed NEEDINFO.
But hey, keep assuming I don't know what I'm talking about and there was a legitimate reason to ask for logs when I already made it clear there wasn't.
I was not making any such assumption and I'll thank you to not think that I was. I was merely pontificating on the hypothetical possibility on why more info may be needed. I would expect much better communications from the dev than you are saying was provided.
If I received a bug report that gave step by step directions (two commands to run in a predefined scenario) I would try the two commands and confirm the result.
If, and only if, that did not provide the purported result, then I would ask for more details -and- (this is important) state that I was not able to reproduce the purported results. I would include the differing results that I did get.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
