Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is a continuation of issue 1020 in which we were putting a bound on the number of entries that can be stored under a specific key in the local storage. The iOS change is now finished, I essentially copied the same code I used from the Android change and just implemented it here. For testing I did the same thing that I did in the Android version. I added
BOUND+1
entries of dummy data to"CURR_GEOFENCE_LOCATION"
, and then I ran the code, making sure that we were left with onlyBOUND-1
number of previous entries, and then the current entry. I attached a log file below that demonstrates theBOUND+1
test that I did, given thatBOUND = 3
. At the very start you can see that I added 4 fillerNSDictionary
values to the local storage, and then at the end of the file we end up with only 2 of those fillerNSDictionary
objects, and the 1 actualCURR_GEOFENCE_LOCATION
value.bounding_local_storage_ios.pdf