Agentry Android Client Error

Question

Hi,
I'm working on SMP 2.3 SP02 and using 6.1.2 Agentry Server, 6.1.2 Android Client. If Android device system language is English, Agentry Client works correctly. But when i change device system language, client gives error during transmit and shuts down.
I've tried SP03 and SP04 but they both did not work.
Thanks,
Serkan Demir

Answer 1

Hi Serkan,
I have analyzed the issue of the problem.
The problem of your error is as follows.
When you transmitted your client or Android Agentry client (whatever version you use: 4.4, 4.4.2, 7.0.5.7, 7.0.6.2.48) is failing due to the client saw an updated definition from the server. The application is trying to download the new set of definition but your localized files are not properly loading.
Your localizations/<overrideFiles>.tr.ini stated that you are not using any locale values ''. This means you are only using the named Country language - "tr".
With this statement, you need to provide the needed override files for all the localization ini files.
This includes the Enable.ini. You need to get Enable.tr.ini. In short, you need to make sure the Agentry system loads all the localizations properly. You need to make sure that nothing gets skipped.
The main issue with skipping is that your timeStamp listed in your system showed that the definition is newer than your <OverrideFiles>.tr.ini.  This causes the application to try to load the application but due to your localization is not loading it is getting confuse and is failing on conversion.
The technique is to play with the timeStamp of your application definition versus the override base files. The check Style is in Turkish but your localization files is not loaded so the conversion fails and you get the error (11).
Potential actions:
1. So you have to somehow work the system where you may try to load the application in English first (no conversion).
2. So the application Check Style gets loaded without conversion.
3. Then try to turn on your localization so that the application will start converting without downloading the application anymore.
Another option:
1) It could also be that your overrideFiles.tr.ini timeStamp has a time older than your application definition.
2) You need to check the timeStamp of your overrideFiles.tr.ini and compare this to your Application/Development/<yourApplication> timeStamp.
3) Check which one is newer.
4) From the timeStamp determine why would the application load first before the override.
5) As stated in my potential action above, we have to work the system to see how the application gets loaded so that conversion happens after the application update (probably on 2nd sync).
Remember your error is that all your overrideFiles.tr.ini needs to be successfully loaded and not skipped. If you can do this it will work. Then you have to worry about other stuff that you need to do:
A) Like making sure you have enabled the SAP language to sync with your SMP server. See http://service.sap.com/sap/support/notes/2116194 (for how to sync SAP timeZone with SMP test case).
B) Setup your timeZoneAlias for your Android client to match SMP or SAP http://service.sap.com/sap/support/notes/1813025
A and B step required in most time zone setup.
Hope this helps.
Mark Pe
SAP Senior Support Engineer