ProximityContentManager not detecting Beacons when Range of the Beacon is changed


I am developing an application with the concept of Proximity Content (for Multiple Beacons).
According to my requirement, The properties of the beacon will in “pending state” and when I bring a beacon closer to the app, it has to detect the beacon and establish connection.

Difficulties faced in this concept:

  • When just the Range of the beacon is changed, ProximityContentManager fails to detect beacon
  • when range of the beacon is changed along with any other parameter like UUID or Major or Minor, it works good
  • Also, previous beacons cache is causing disturbances

Can anyone help on this ?