When using AppSheet on a Mac, I experience an issue where, after entering text in a form and pressing Enter, the text I typed is duplicated.
For example, if I type “Hello” and press Enter, it appears as “HelloHello.”
Could this be a bug?
※This issue occurs specifically when entering text in Japanese. When using English, the problem does not happen.
I use Mac and have never seen that problem.
The machine you are running on should not be an issue. These are web apps, designed to run inside of a browser. Try running the app in a different browser on the same Mac. I suspect you will get the same behavior. If not, then clear the cache of the first browser and try again.
I suspect though that there is something within your implementation causing this problem.
Do you have an Initial Value expression inserted? If so can you show that?
Do you have an action attached to the Form Save behavior? If so, please show that.
Any Bots touching the row after the Save? If so, please show.
Thank you for your response.
I have checked the settings, and there are no Initial Value expressions or any custom Form Save behaviors configured. Additionally, there are no Bots interacting with the row after saving.
It seems that this issue only occurs when inputting text in Japanese. When using English, the problem does not happen.
Please contact AppSheet Support for help with this.
I reported this issue to AppSheet Support on June 27th and exchanged 11 emails until September 17th. I received 7 responses from the Support team, but almost all of them were template replies. Throughout this period, I have not received any progress updates or latest information from either the development team or the support team. When I inquired about whether the issue had been successfully reproduced and the timeline for bug resolution, I only received template responses.
While this issue might seem minor or negligible from a global perspective, it has a significant impact on Japanese-speaking macOS users, preventing them from creating applications and conducting actual business operations using AppSheet.
I urgently request a resolution to this issue.
Below, I have detailed the information I reported to the Support team. If anyone is reading this post, I hope it will prompt some action.
Subject:
Bug Related to Japanese Text Conversion
Issue:
A bug has occurred regarding Japanese text conversion. I will provide a specific example in the following images.
Japanese input tools have a character conversion function. When inputting Japanese, this character conversion is always performed.In Japanese, conversion candidates are displayed at word breaks.
image-01:
In image-01, the word is divided into parts 1 and 2. Therefore, character conversion can be performed for both 1 and 2 separately. The word in the image (consisting of 5 kanji characters) is correct, so there’s no need to convert either 1 or 2. In such cases, we skip the character conversion and confirm by pressing the Enter key.
image-02:
As described above, when confirming with the Enter key while conversion candidates remain, a bug occurs as shown in image-02. The unconverted word, part 2, is duplicated in the input.This phenomenon has been occurring since around June 25, 2024.
After careful consideration and further testing, I have reason to believe that this problem is indeed related to AppSheet, specifically its interaction with Chrome on MacOS. Please allow me to provide more detailed information:
Given these observations, I believe the issue likely stems from a compatibility problem between AppSheet and the Chrome browser on MacOS, rather than with the Japanese input tools themselves.
Steps to Reproduce the Bug:
image-03:
image-04:
Example of Text Input and Bug:
Detailed input procedure:
Explanation:
“東京都大学” is not a real university name and is not registered in the Japanese dictionary. It consists of two word segments: “東京都” (Tokyo city) and “大学” (university). When confirmed with the Enter key, “大学” (university) is duplicated in the input.
Please note that this issue occurs consistently in the described environment but does not happen when using Safari on MacOS or when using AppSheet on other operating systems.
I am Japanese.
I am not a Mac user, so I have not actually experienced this, but I have seen this phenomenon posted in a number of X (formerly Twitter) posts.
I also found a video showing this phenomenon and will post it here.
Attn @devingu @AleksiAlkio
Thank you for the detailed explanation.
It seems that the same issue occurs when using Japanese input on a Mac. Since the problem does not occur in Safari, I will use that as a workaround for now.
Your help has been very much appreciated.
Thank you, as always, for your comments.
I’ve also seen posts about this issue on X a few times.
I appreciate you sharing the video as well.
Thank you for your response. However, I respectfully request that you remove the “Solved” status from this thread, as this issue remains unresolved. Let me explain why:
I hope you understand why this issue should remain open until a proper solution is implemented for Chrome, which is AppSheet’s primary supported browser on MacOS.
I am also a MAC user and I use AppSheet in Japanese.
I have been aware of this issue for several months, but it has not been resolved yet.
This issue does not occur when using AppSheet in English.
However, since most of the values I enter in the app are in Japanese, I cannot ignore this bug. This is because if duplicate entries continue to occur when entering values, it will take time and effort to correct them, which is stressful.
I have seen a response before stating that this is not an AppSheet issue, but I believe that this is not OS-dependent. Please consider fixing this. Thank you.
I understand the importance of the issue.
I will remove the “solved” status.
Since I am a Windows user, I might not notice when the problem is resolved. Therefore, I would appreciate it if you could let me know when the issue is fixed so I can mark it as solved.
Thank you.
Thank you for understanding and removing the “solved” status. I truly appreciate your thoughtful response.
When they encounter this text input problem in their first experience with AppSheet, they are likely to abandon the platform immediately, missing out on its powerful capabilities. That’s why keeping this thread open and visible is so important.
I will definitely update this thread when the issue is resolved.
Thank you again for your cooperation in maintaining visibility on this issue.
You are absolutely right.
Neglecting this issue is definitely a negative for Google.
I’m experiencing the same problem.
Even though we’ve developed it, it’s very difficult to use, and we have to ask our clients to use Firefox, Safari, or Edge instead of Chrome, which is a real pain.
It’s so difficult that I think it would be better to implement it using Google Forms. (We’re actually considering this on the client side.)
I think it’s a big minus for Google, which wants to expand Chrome in the future.
Maybe there’s no benefit to improving the convenience for Japanese users because the development team is divided and not involved in the evaluation…
Hi @devingu @AleksiAlkio @lizlynch
I have conducted additional investigation into this issue and would like to share some important findings that might help identify the root cause.
The text duplication issue shows a clear pattern:
Since AppSheet is a web application, I believe the following implementation details are relevant:
<textarea> elements<input type="text"> elementsInterestingly, there was a localization update around June 20, 2024, specifically for iOS date displays:
Before/After Changes:
Dec 10, 20242024/12/20This update is notable for several reasons:
<input type="date">Based on my analysis, the issue might be occurring due to:
For a permanent resolution, the development team might want to consider:
The fact that this issue:
Strongly suggests this is related to either:
I hope this analysis helps in identifying and resolving the issue. Please let me know if you need any clarification or have additional observations to share.
Thanks for these details!
Thanks for reporting this - I’ll be ramping up a fix for this after the holidays so keep an eye out in the release notes.
Is this bug fix?
Hi @amyplin
Thank you very much for looking into this issue and planning to implement a fix. We look forward to seeing the update in the release notes.