Codecov Report

Merging #243 (1639757) into dev (f0e978d) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##              dev     #243      +/-   ##
==========================================
+ Coverage   94.48%   94.52%   +0.03%     
==========================================
  Files          27       27              
  Lines         979      985       +6     
==========================================
+ Hits          925      931       +6     
  Misses         54       54              

@kevinlind thanks for reviewing.
The build was failing and I made a small change - reverted the pod updates. It looks like the latest AEPEdgeConsent brings AEPEdge as a dependency and once installed it shows as a new scheme in Xcode so the xcodebuild gets confused to which one to pick.
We have couple options for this:

• We clean up the test apps and tests in this repo to not bring external dependencies other than AEPCore so we can continue using AEPEdge from source code. Any integration tests with Consent + Edge will be moved to Consent extension. Any manual integration tests will be executed using the sample app.
• We define a test podspec for AEPEdgeConsent and exclude the AEPEdge dependency so we can continue using it.

I am inclined towards the first one, let me know your thoughts.

@kevinlind thanks for reviewing. The build was failing and I made a small change - reverted the pod updates. It looks like the latest AEPEdgeConsent brings AEPEdge as a dependency and once installed it shows as a new scheme in Xcode so the xcodebuild gets confused to which one to pick. We have couple options for this:

• We clean up the test apps and tests in this repo to not bring external dependencies other than AEPCore so we can continue using AEPEdge from source code. Any integration tests with Consent + Edge will be moved to Consent extension. Any manual integration tests will be executed using the sample app.
• We define a test podspec for AEPEdgeConsent and exclude the AEPEdge dependency so we can continue using it.

I am inclined towards the first one, let me know your thoughts.

I'm inclined to the first option as well. However, I'd like to know more about change adobe/aepsdk-edgeconsent-ios#43 to see if we can simply remove the AEPEdge dependency from the AEPEdgeConsent podspec.

Even though there is no hard dependency on the Edge extension APIs, the Consent extension relies on the Edge functionality for handling the consent updates. Any new feature or improvement to support the Consent workflows will require a bump in this dependency, and I think the dependency link is still required for better version management.
I created a new task for the clean-up.