cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry Android Clients Not Working on Android 5.0

Former Member
0 Kudos

Hi,

After updating Android devices to Android 5.0 software version, Agentry Android Clients not working. It opens login screen and after login information is entered client shuts down itself without giving any error message. This is very bad situation for us because our applications not working for Android 5.0 devices on our production servers.

Best Regards,

Serkan DEMIR

Accepted Solutions (1)

Accepted Solutions (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos
Serkan,

The Agentry Android client will run on an Android 5.0 device as of SP06. It will also run on SP05 PL02 as long as you are not using an image capture field. There was a fix that was put in for that in SP06.

If after trying these versions you are still having problems you will need to open a ticket with support.

--Bill

Answers (3)

Answers (3)

Former Member
0 Kudos

What is SAP's position on this regard? I can imagine that more and more Android users will update to Lollipop the coming weeks/months. Also consider the fact that Afaria is not able to block an OS update:

Today’s OS updates are distributed over the air by the device owner. To Samsung, Apple and Microsoft the ability of keeping users on the latest OS version is a key element of maintaining the eco system; with users up-to-date the vendors can protect their brand value offer a broader range of (paid) service on the platform. The update process cannot be centrally blocked or managed.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Serkan,

Please open a ticket with support.  That will be the best way to get an answer on support.

--Bill

Former Member
0 Kudos

Also, when a device is tested it is tested with that version of OS that was sent it.  If you want to run a later version of the OS then was tested by QA, it should be retested.

Stephen

Marçal_Oliveras
Active Contributor
0 Kudos

Android 5.0 is not supported for now.

I guess the best you can do is create an incident in SAP support, maybe they will answer you if they have any plans to the client soon.