Japanese here
Home > Products > Wrix


(for Android)

Known Issues

File creation date and update date are the same

Java of programming language is used for the development of this app, but because Java can only get the same value for creation date and update date, it works like this.
We'd like to fix it, but we going to postpone it because it seems to take a lot of trouble.

When save a file to Google Drive via the "Files" app, multiple files with the same name appear

Google Drive is a specification that can have multiple files with the same name.
Therefore, if you save a file to Google Drive via the "Files" app, multiple files with the same name will appear.

To avoid this problem, it is necessary to add a function to edit Google Drive files directly in this application, and it may be difficult to respond immediately.

In version 1.1, a function to directly edit Google Drive files has been added, so please use that.

It is hard to scroll if there is a Launcher type button on the Toolbar

This problem occurs because it is difficult to determine whether the touch operation is scrolling or pressing a button.
When scrolling to the toolbar depending on the screen size, change the button size or switch to the Popup menu.

There are times when the position of the converted character cannot be changed by tapping during character conversion input

When input that requires conversion such as Japanese input, the conversion position can be changed by touch operation. However, even if you try to move to the last position after changing the position, you may not be able to move.
In the app, the position change is notified to the soft keyboard, but there are times when it can and cannot be done.
Since this problem is the same in Android's standard Text Editing UI, it is judged as an OS problem.

You may be able to move the position by swiping backward from the front of the conversion character.

The Delete key on the "Google Voice Input" keyboard does not work

This problem seems to occur only with "Google Voice Input" keyboard. The problem is unexpectedly deep and unclear due to lack of explanation in the document.

Currently, Android's standard keyboard "Gboard" is easier to use and can be used instead, so please use "Gboard".
Or, you can use the Delete function by displaying and using the "Voice Input Assist bar" of this app.

Similarly, there are some keys that do not work in the text editing function of "Gboard".
In order to solve these problems, it is necessary to frequently pass the whole text to the soft keyboard, which is a wasteful process and inefficient, so the response is postponed.
Since useless processing is required, it may not be supported.

There may be times when no touch operation is accepted

In this app, UI such as Popup menu is displayed in a special way, and it is judged that this problem occurs because UI non-display processing such as Popup menu is not processed until the end when some timing overlaps.

The investigation is ongoing, but the timing of the occurrence is unknown, so if there is any information, please let us know from the "Contact Us".

Popup menus may not be hidden

Pop-up menu, SideView, and Toast (which displays a message) may not be hidden.
It seems to occur especially when the following operations are performed on the gesture bar provided by the OS at the bottom of the screen when using Android 10 gesture navigation or 2-button navigation.

  • Swipe up on the gesture bar and put it back without releasing your finger
  • Swipe the gesture bar left or right to return it without releasing your finger

As a cause, these UIs use PopupWindow UI provided by Android, but this UI seems to be displayed incorrectly if the operation of the gesture bar is stopped halfway. Moreover, since there is no notification in the app, we have determined that it is difficult to respond.
While operating the gesture bar, Toast (displaying a message) is hidden by the timer, but it has been confirmed that it will be ignored and remain. (Android10 environment)
In very rare cases, the Popup menu and SideView continue to be displayed, but the touch event goes to the lower view, and it is confirmed that it continues to obstruct like a blindfold. (Android10 environment)

As a workaround, you can end the process by releasing your finger without stopping the operation of the gesture bar.

In order to return to the original when it occurs, I think that it will be improved by operating the gesture bar again, releasing the finger without stopping halfway to end the process, and then returning to the app.

Input with some soft keyboards does not work well

This has been fixed in version 1.0.7.

Wnn-based soft keyboards (such as "S-Shoin" pre-installed on SHARP terminals) have a problem that input cannot be performed properly.
The cause seems to be caused by the difference between the processing of this app or Wnn.

Similar problems do not occur with other soft keyboards such as Gboard and ATOK, so I think that using other soft keyboards can avoid it.

Even if you use a monospace font, it may not be monospaced-width depending on the character size.

This has been fixed in version 1.1.5.

Due to Android limitation, full-width character width may not be twice as wide as half-width character width even if a monospaced font is used.
This problem is because the function provided by Android rounds up the decimal point of the half-width character internally, so instead of the originally expected "full-width character width = half-width character width x2", because the full-width character width is treated a little smaller like "full-width character width = half-width character width x2 -1".
In reality, half-width characters are rounded up to the nearest whole number and are processed to an little bigger size.

We tried to absorb this problem in the application and try to deal with it, but I decided that it would significantly slow down the processing and stopped it.
I submitted a bug report for Android and registered a bug, but I do not know when it will be fixed.
Currently, there is no problem depending on the character size, so if you want to display in monospace, the only workaround is to specify the character size that does not cause a problem.
In version 1.1.3 or later, a caution message will be displayed when you specify a size that does not become monospace when you use a monospace font on the "Text Size" setting screen.

Please feed back.
Copyright(C) 1997-2020 All Rights Reserved.