chwastek
commented
6 years ago Hey @vasquezdennisalon can you be more specific? I downloaded your project, but it is an empty one and I'm not sure what is the issue here exactly?
Open vasquezdennisalon opened 6 years ago
chwastek
commented
6 years ago Hey @vasquezdennisalon can you be more specific? I downloaded your project, but it is an empty one and I'm not sure what is the issue here exactly?
vasquezdennisalon
commented
6 years ago Hi @chwastek Thank you. Sorry you're right the code was not there but I already updated it so you can review it and additionally I share an image where I run the application and just having the Estimote code in the viewController makes the work of the CPU rise too high
vasquezdennisalon
commented
6 years ago Hi @chwastek
I have migrated the Estimote version to the previous one and I have tried the proximity example found in this repository: https://github.com/Estimote/iOS-SDK/blob/master/Examples/swift/Proximity/Proximity/ViewController.swift
Then I create my own project that is in this repository https://github.com/vasquezdennisalon/EstimoteSDKProximity/tree/master/aupar/aupar/EstimoteProximity
then compiling the project gives me the same overhead of the cpu in this project that I create, create several zones and the cpu increases too much
I have tested on the following devices:
There is a problem with the new version of estimote, it makes the use of the cpu is very high can reach 60%.
I have tested on the following devices:
I have created a repository and I have uploaded the code that I used to demonstrate the high use of the cpu https://github.com/vasquezdennisalon/EstimoteProximityExample.