ExitExipirationPeriod seem not settable

BLE Beacons
1

Hi,
I’m tryng to test some featurs of beacons but when I tryed to tweak the setRegionExitExpiration the result was that the region exit event is triggered after about 20s while I had set 1s.
I’m using com.estimote:sdk:1.0.1:release@aar.
What could I wrong about?

Thaks

2

Hi @Silvio,

maybe this could be usefull.

3

Thanks for the reply. I’m using Android 6.0.1. The other settings like wait background period works fine also with 1s.

4

After some testing I tried with sdk version 0.16.0 and the setRegionExitExpiration works fine. However with verion 1.0.1 and 1.0.3 the exit period is blocked at about 20s. Has someone else the same problem?

5

Hey,
maybe this is the reason.

6

Ok, but I’m using Android 6. Is there any way to set smaller period?

7

It seems to me that the Android restriction is above 7.0 but the SDK does not verify the version and always imposes the 6s.

8

Hi @Ximun,
Regarding to Android setRegionExitExpiration problem. have you found an answer?

9

I have the same issue and I’m using SDK 1.0.12 on Android 5.1.

I set RegionExitExpiration to 1s, but it seems, that it set to 20s.
with 0.16.0 all work fine, but not in 1.0.12.
I also tried to set it to 60s, but it’s always 20s.

Is there an older version (no .0.16.0), where setRegionExitExpiration works?

10

Hi,

I can confirm it’s a bug in 1.+ SDK versions. It enforces SDK to always use default 20s expiration timeout before triggering exit event. We’re working on fix for this bug - it should be available in upcoming SDK version.

Regards
Wojtek

1 Like