Agentry Android Client - Device Language Problem

[Former Member]

Hi all,

We are using SMP 2.3 SP04 and Agentry 6.1.4 versions both for client and server.

There is no problem when the client's device system language is English. But when it is a diferent language, gives an error.

Check the screenshot below,

Previous client versions are worse, because they all just crash after "Checking Style Definition" step.

Thanks in advance.

[Former Member · Accepted solution]

Hi Murat,

we have fixed this problem, see this document for details:

Hope it works for you as well!

[Former Member]

Hi Murat, Is your backend system configured to handle the logon and display masterdata in other languages than English?

It seems that the Android's device language is used to define the logon language on the backend to pull reference and transaction data. This will crash if not enabled or fully maintained. We are facing this problem and I am also looking for a solution, using the same versions of SMP and client.

Regards, Merten

[Former Member]

Are there any errors on the server side?

[Former Member]

Hi Steve, there is no server errors in log files.

[mark_pe]

Murat,

One idea for non-English language is that all the localization files or configuration files (*.ini) or any edited files were saved in encoding type: Unicode.  If you are using Notepad to save your changes, when you press save or save as there is an Encoding type selection next to the "Save" button. Make sure it is Unicode (not Aschii).

Here is the definition of Unicode Wiki: http://en.wikipedia.org/wiki/Unicode

If you look at the Wiki Unicode characters support Non-English or character type better.

The above is just a trick we use in support. Also when Agentry implemented multilingual support the code supported Unicode encoding.

This is one idea.

Another idea is to dive in the log files just before the failure occurred for Replacing Definition for EditFieldStyle. Check which file it used.  Try opening it in Notepad and click Save As - See what encoding it is using (The Encoding will be displayed next to the Save button).

Regards,

Mark Pe

SAP Senior Support Engineer (Mobility)