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?
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?
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?
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.