Skip to content

Target SDK should attach response tokens in the retrieveLocationContent data callback#155

Merged
swarna04 merged 7 commits intoadobe:dev-v4.0.3from
swarna04:MOB-20188
Jan 26, 2024
Merged

Target SDK should attach response tokens in the retrieveLocationContent data callback#155
swarna04 merged 7 commits intoadobe:dev-v4.0.3from
swarna04:MOB-20188

Conversation

@swarna04
Copy link
Copy Markdown
Contributor

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@swarna04 swarna04 requested a review from sbenedicadb January 24, 2024 18:09
Copy link
Copy Markdown
Member

@sbenedicadb sbenedicadb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good - couple questions we can chat about on the side.

probably a good idea to run the UpdateVersions GH action to ensure we didn't miss anything

import Foundation

extension NamedCollectionDataStore {
static func clear(appGroup: String? = nil) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is useful across all our extensions - have you talked with @timkimadobe about getting it added to our test-utils framework?

if let appGroup = appGroup,
!appGroup.isEmpty,
let userDefaults = UserDefaults(suiteName: appGroup) {
for _ in 0 ... 5 {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we have a better way to iterate through defaults to clear them? curious as to why we are using a for loop here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code has been around for a bit to ensure the defaults get cleared. You can find it elsewhere too, see https://github.com/adobe/aepsdk-core-ios/blob/main/AEPCore/Mocks/UserDefaults%2BClear.swift.

@swarna04 swarna04 merged commit 4744078 into adobe:dev-v4.0.3 Jan 26, 2024
swarna04 added a commit that referenced this pull request Jan 26, 2024
…nt data callback (#155) (#156)

* Target SDK should attach response tokens in the retrieveLocationContent data callback

* Minor fixes

* • reverted dependency updates
 • updated test constants

* revert podfile.lock

* Fixed tests after migration from UserDefaults to file system.

* minor cleanup

* Additional test + doc update

Co-authored-by: Steve Benedick <sbenedic@adobe.com>
swarna04 added a commit that referenced this pull request Jan 26, 2024
…nt data callback (#155) (#156) (#157)

* Target SDK should attach response tokens in the retrieveLocationContent data callback

* Minor fixes

* • reverted dependency updates
 • updated test constants

* revert podfile.lock

* Fixed tests after migration from UserDefaults to file system.

* minor cleanup

* Additional test + doc update

Co-authored-by: Steve Benedick <sbenedic@adobe.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants