ts_3156
#1
Hi,
I am grateful for your devoted support.
Question 1:
I was instructed by @IgorBrigadir to contact the help form, but I received a message from the help forum that the bug of Quick Reply is not officially understood. This bug has been reported by several developers, so it seems to exist. How can I get it officially understood as a bug?
Question 2:
The help form says to me that this is not the place for technical reports. So where is the place to file a bug report?
Question 3:
It was also reported that @IgorBrigadir is not an engineer at Twitter and his statements are not official. He certainly does not identify himself as an official staff member. However, he does seem to have editorial privileges for this forum. If he doesn’t mind, I’d like to know about his role.
The help form I contacted:
https://help.twitter.com/ja/forms/help/direct-messages
Previously, I contacted the help form in Japanese. Could the language be the cause of this confusion?
Case Number:
Case# 0252743091: Direct Messages [ ref:_00DA0K0A8._5004w2KpKoy:ref ]
Similar issues:
Thanks
1 Like
ts_3156
#2
@suvpen @machidaino399 @djaneta Could you tell me if you know anything about this issue?
suvpen
#3
Hi @ts_3156! I’ve sent the form to the support team and got the response as the picture below. I don’t know if this case is added to the bug sprint or not. I am just suspicious since the response looks like a bot template.
1 Like
ts_3156
#4
@suvpen Thank you for sharing it. I contacted the Japanese help form, so I may have received a meaningless message. I will try to contact the English help form as well.
1 Like
Yes, very unfortunate - this does seem like a front end bug in iOS. And i’m just guessing, front end people do not pay attention to these forums.
I’d like to know about his role.
Oh, moderator role on Discourse Forums is something that an Admin enables on an account - was enabled on my account just because i’m here a lot: Introducing the Twitter Developer Insider Program
2 Likes
LeBraat
#6
Hey there @ts_3156 -
Regarding the above, Igor is correct. He is one of our Twitter Developer Insiders, which is a community program aimed at recognizing those developers with expertise in a variety of different categories that help build on and support the Twitter Developer Platform. Essentially, they are our BFFs 
The Insider program is still in its infancy. We are actively working on adding badging for our Insiders to different surfaces, including the forums, and more details to our website.
If you have any more questions about this program, feel free to DM me!
2 Likes
Hi! I have some good news on this - the iOS team is aware of the reports that you have raised in the past weeks, and has been looking into it. This should be resolved in a future release of the app, via the App Store. I cannot tell you when that will be delivered, but be assured that this is a known issue.
Unfortunately, we cannot help with Twitter app and website issues on the forums here; using the support form or contacting @TwitterSupport is probably the best way to get attention.
Thank you!
4 Likes
suvpen
#8
Thank you so much for the update and let the iOS team aware of this 
1 Like
ts_3156
#9
@IgorBrigadir @LeBraat Thank you for explaining it to me. I know that you are helping a lot of people in need. Thank you for everything.
@andypiper Thanks for the good news. I will wait for the problem to be solved.
1 Like
djaneta
#10
Thank you so much for the update!
Thanks you much for updates. God bless you
Thank you for the update.
Now it has been 10 days since your message and the bug still. This is affecting the business and I hope it get solved asap
Yes I know, we are sufffering with our customers too!
I cannot say when the build containing the fix will be released from the App Store, but this is coming.
2 Likes
system
Closed
#15
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.