adobe / places-monitor-ios Goto Github PK

Handles native location monitoring in your app and integrates with Places extension in the Adobe Experience Platform iOS SDK

License: Apache License 2.0

Ruby 0.83% Objective-C 90.29% Makefile 6.80% C 2.09%

places-monitor-ios's Introduction

Notice of deprecation

On August 31, 2021, the Places Monitor extension for the Adobe Experience Platform Mobile SDKs will be deprecated. The Places Monitor extension will not receive further updates or support beyond August 31st.

Customers that currently use the Places Monitor extension can continue usage of this extension with the understanding that no additional updates or support will be available through Adobe.

The deprecation of the Places Monitor extension has no bearing or negative impact on the Places Service extension which will continue to be supported with enhancements and updates.

Customers that are looking to transition away from the Places Monitor extension to their own monitoring solution should review the documentation for: Use Places Service with your own monitoring solution. This document explains how to interact with the Places Service by implementing Core Location services on iOS or Location Services from Google Play.

Getting started with ACPPlacesMonitor for iOS

Table of Contents

About this project
Current version
Contributing to the project
Environment setup
- Open the Xcode workspace
- Command line integration

About this project

The ACPPlacesMonitor for iOS is used to manage the integration between iOS's CLLocationManager and the ACPPlaces extension for the Adobe Experience Platform SDK.

Current version

Contributing to the project

Looking to contribute to this project? Please review our Contributing guidelines prior to opening a pull request.

We look forward to working with you!

Environment setup

The first time you clone or download the project, you should run the following from the root directory to setup the environment:

make setup

Subsequently, you can make sure your environment is updated by running the following:

make update

Open the Xcode workspace

Open the workspace in Xcode by running the following command from the root directory of the repository:

open ACPPlacesMonitor.xcworkspace

Command line integration

From command line you can build the project by running the following command:

make build

You can also run the unit test suite from command line:

make test

To create an XCFramework, run the following:

make xcframeworks

The resulting XCFramework can be found at bin/iOS/ACPPlacesMonitor.xcframework

Licensing

This project is licensed under the Apache V2 License. See LICENSE for more information.

places-monitor-ios's People

Contributors

Stargazers

Watchers

Forkers

sbenedicadb iewilliam pravinpk gapandpc chawatvish nporter-adbe spoorthipujariadobe isabella232 mojodelicious classicvalues ghas-results

places-monitor-ios's Issues

Found a problem when we install nested dependency by Cocoapods

Dear all,
We found a problem we can't build your lib when we use it on nested dependency.
It showed ACPCore.h, ACPExtensionEvent.h etc. not found.
And that we solved this issue by using import lib with namespace syntax.
So, we try to change your code on Cocoapods and it works!.
Actually, I would like to open a pull request but your rule makes me create an issue first. 🤔

Please review this issue because we are blocked.

Ref: https://github.com/chawatvish/places-monitor-ios/commit/ed7e4fae1b8be5865cdd22828ca0d71302098b72

need improvment in README file

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Test Jira integration

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Better unit test coverage

Expected Behaviour

Unit test coverage should be at 90% or higher

Investigate use of CLVisit APIs

Primarily looking to handle use cases where dwell time plays a factor, either in:

Triggering the initial entry event, or
Triggering some other rule after a determined amount of time has passed

Report CLAuthorizationStatus to Places

A new API is being developed to collect the authorization status of the device WRT access to location.

This issue is to properly update the Places Extension when the Auth Status of the device changes.

Get CI running to validate pull requests

Expected Behaviour

Upon opening a PR, CI should run unit tests and validate that the changes will not break the build.

Monitor cannot differentiate between network error or no POIs around the user

Expected Behaviour

Monitor extension should not deregister previously registered geofences if we failed to fetch new list of POIs due to network error

Actual Behaviour

The current POI fetch API does not return any error code. If it returns no POIs, monitor automatically deregistered all monitored geofences.

Reproduce Scenario (including but not limited to)

Have the monitor running and tracking POIs. turn off network, move a significant distance. All tracked POIs will now be deregistered.

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

should provide an option to purge client-side places data when stopping monitoring

should not continue monitoring regions when server-side configuration is inactive

Expected Behaviour

When the Places extension gets a configuration related error from a getNearbyPointsOfInterest:limit:callback:errorCallback, the Places Monitor should stop monitoring any regions it was currently monitoring.

Actual Behaviour

The Places Monitor continues to do region monitoring for regions it was previously monitoring even if the Places extension has been removed from Launch configuration.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Update logs to be more meaningful

Expected Behaviour

Places Monitor should provide more helpful logs when:

locationManager:didFailWithError: is called
The listener hears an event
Processing a new list of POIs results in a non-entry due to the monitor already knowing that the device is within a region

adobe / places-monitor-ios Goto Github PK

places-monitor-ios's Introduction

Notice of deprecation

Getting started with ACPPlacesMonitor for iOS

About this project

Current version

Contributing to the project

Environment setup

Open the Xcode workspace

Command line integration

Licensing

places-monitor-ios's People

Contributors

Stargazers

Watchers

Forkers

places-monitor-ios's Issues

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Expected Behaviour

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Actual Behaviour

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Platform and Version

Sample Code that illustrates the problem

Logs taken while reproducing problem

Expected Behaviour

Recommend Projects

Recommend Topics

Recommend Org