So I don't think you are experiencing AGDROID-270.
I've used the Android N network security tooling and still get the same
error. Additionally I have successfully registered with a different
instance of UPS using the sample code.
Which version of the UPS server are you running?
On Thu, Jun 2, 2016 at 7:13 AM, Summers Pittman <supittma(a)redhat.com> wrote:
On Thu, Jun 2, 2016 at 1:53 AM, Ramona.Cristea <Ramona.Cristea(a)mvise.de>
wrote:
> Unfortunately the client wants to support API 16 and up, so we have to
> find a
> solution also for the older android versions. I sent you yesterday evening
> the sample app through email, hope you received it.
>
> Could you test the workaround in an Android N emulator? If the app works
in that situation we know you are facing
https://issues.jboss.org/browse/AGDROID-270 and we can work out a better
work around which works for Android 16 (and fixes this for everyone else).
I'm taking a look at the sample today.
>
> --
> View this message in context:
>
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Device-registr...
> Sent from the aerogear-users mailing list archive at
Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/aerogear-users
>