Solved

File with accent rejected on tablet

  • 28 October 2021
  • 6 replies
  • 75 views
B
Rank
Userlevel 1
Badge

In Production (and UAT), on Tablet (it's OK in BO), in a service order or a quote, technician add a file whose title contains an accent and he can see this file in attachment. If he changes something in the service order or in the quote and if he checks attachment again, file has disappeared.

This problem is solved if we change name of this file and delete accent (ex : e instead of é).

How do we make sure that all characters can be accepted in the file labels?

icon

Best answer by Eisha Hasnain 28 October 2021, 17:12

View original

6 replies

E
Rank
Userlevel 6
Badge +10

Hi Bharat, This issue is fixed in V3.3.1 of the Astea Mobile Native Application. So the fix will come directly from the Play Store. Please update from native app.

U
Rank
Userlevel 4
Badge +6

Please note that the latest Astea Mobile Native app, 3.3.1 is also now available on the App Store for iOS devices.

K
Rank
Badge

Is a listing available of what all the changes/fixes are in Astea Mobile 3.3.1?

Reid Gilbert
Rank
Userlevel 7
Badge +15

For iOS 3.3.1 there was only one fix (Android 3.3.1 is still undergoing QA at this time):

Fix application crash when communicating with Baidu services while running on AT&T network

Reid Gilbert
Rank
Userlevel 7
Badge +15

The Astea Mobile Android Native App V3.3.1 has now been submitted to the Play Store for review by Google.  The release notes for this update are as follows:

- Android 10 & 11 will no longer save attachments in the Documents/Astea directory and will store attachments as part of App Data.

- Fix issues with uploading attachment files with accent characters in the file name

- Baidu Service notification will no longer appear when rebooting device

- Added back support for Android 5.0.0

- Fix Open Database Issue Android 11

 

U
Rank
Userlevel 4
Badge +6

I believe that the Astea Mobile Android Native App V3.3.1 also addresses an issue whereby the URL is being cleared when the app is launched. The current workaround is to re-enter the URL manually and the app will then function as per normal.

 

 

 

 

Reply


Terms & ConditionsCookie settings