Currently the AssuranceClientInfo.getDeviceType() uses the UIDevice.current.userInterfaceIdiom which maps to an enum of all platforms. This means that whenever a new platform is added like so we need to update the enum even if Assurance doesn't support the platform.

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

Limited retries with extended delays for connection retries to an Assurance session. No retries for unrecoverable errors.

Actual Behaviour

Frequent unlimited retries trying to connect to the deleted Assurance session.

Reproduce Scenario (including but not limited to)

Steps to Reproduce

Connect to deleted assurance session

Platform and Version

iOS

"com.adobe.assurance" : {
      "version" : "3.0.1",
      "friendlyName" : "Assurance"
    }

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

Provide a text input field for configuring appId in the test app allowing getting rid of hardcoding the test app. This will be beneficial for Assurance E2E tests to be more configurable.

Actual Behaviour

AppId is hardcoded in the Test App. E2E tests will not be able to override it if needed later without an app update.

Currently it is possible for stateManager variables fetched by QuickConnect classes to change throughout the QuickConnect flow. Look into potentially restarting quickConnect flow internally when relevant state changes, or keeping it in sync using other mechanisms.

Hi Team,

I have added AEPAssurace.xcframework in the iOS project. Project have other adobe frameworks also like "AEPCore", "AEPAnalytics". When i write following code in Appdelegate then i got error.
Code Snippet:

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    MobileCore.setLogLevel(.debug)
    
    let appState = application.applicationState
    let extensions = [AEPMobileServices.self,
                      Assurance.self,
                      Analytics.self,
                      Identity.self,
                      Lifecycle.self,
                      Signal.self,
                      UserProfile.self]
    MobileCore.registerExtensions(extensions) {
        MobileCore.configureWith(appId: "<appID>")
        if appState != .background {
            MobileCore.lifecycleStart(additionalContextData: ["contextDataKey":"contextDataVal"])
        }
    }
    return true
}`

Error:
dyld: lazy symbol binding failed: Symbol not found: _$s7AEPCore5EventC10responseID10Foundation4UUIDVSgvg
Referenced from: /Users/kumariritupal/Library/Developer/Xcode/DerivedData/AdobeSample-chrkcqnvpzrflseznqedbbxtqkir/Build/Products/Debug-iphonesimulator/AEPAssurance.framework/AEPAssurance
Expected in: /Users/kumariritupal/Library/Developer/Xcode/DerivedData/AdobeSample-chrkcqnvpzrflseznqedbbxtqkir/Build/Products/Debug-iphonesimulator/AEPCore.framework/AEPCore

dyld: Symbol not found: _$s7AEPCore5EventC10responseID10Foundation4UUIDVSgvg
Referenced from: /Users/kumariritupal/Library/Developer/Xcode/DerivedData/AdobeSample-chrkcqnvpzrflseznqedbbxtqkir/Build/Products/Debug-iphonesimulator/AEPAssurance.framework/AEPAssurance
Expected in: /Users/kumariritupal/Library/Developer/Xcode/DerivedData/AdobeSample-chrkcqnvpzrflseznqedbbxtqkir/Build/Products/Debug-iphonesimulator/AEPCore.framework/AEPCore

OtherFrameworks:

I am facing a problem AEPAssurance.modulemap not found. I problem comes up suddenly, it was working fine but suddenly this issue comes, I have been tried all the solutions but not able to fix it, kindly help me to fix this issue.

Xcode version 15.2, I have been tried on older version as well but not able to fix it.
ruby version: 2.7.6
pod version: 1.12.1
node version: 18.5.0
React Native Version: 0.71.4

• iOS 10 has been deprecated as the minimum deployment version on Xcode 14, we need to update it to iOS 11
• SwiftLint build phase dependency analysis warning

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

I have found that if we get into a weird state where the socket connection either can't be established or errors out AFTER we have created a Session object in the AssuranceSessionOrchestrator, then we get into a weird state because the session isn't terminated properly on cancel or when we hit an error from the socket layer.

Expected Behaviour

SDK initialization should be near-instantaneous

Actual Behaviour

SDK initialization blocks the main thread for 50+ms as it creates a WKWebView.

There's commented-out code in the codebase to use URLSession's native WebSocket support. Presuming that code works, you can probably just uncomment it and use if #available to use it at runtime on iOS 13+.

Platform and Version

iOS, 3.1.2

@addb reported that it is often difficult to identify the Assurance session that the app is connected to, especially when the session auto connects. Add functionality that displays friendly session name and orgId in the Assurance log screen.

Currently we don't limit the number of retries for the getDeviceStatus polling. We should limit it by time or tries.

Once the new parentId field is added to MobileCore Event class, update the AssuranceEvent to read and pass the new field to the Assurance UI.