![]() * fix(Analytics): Fixing issue when dirty/events that exceeded the retry count were not deleted when an error was thrown. * fix(Analytics): Updating Pinpoint event quotas and exposing them as public constants. * fix(Analytics): Stopping batch submission if all events in a batch are rejected by Pinpoint. * chore(Analytics): Updating unit and integration tests. |
||
---|---|---|
.. | ||
AWSPinpointAnalyticsPluginIntegrationTests.swift | ||
README.md | ||
TestConfigHelper.swift |
README.md
Analytics Integration Tests
The following steps demonstrate how to set up Analytics. Auth category is also required for signing with AWS Pinpoint service and requesting with IAM credentials to allow unauthenticated and authenticated access.
Set-up
-
amplify init
-
amplify add analytics
? Select an Analytics provider: Amazon Pinpoint`
? Provide your pinpoint resource name `yourPinpointResourceName`
? Apps need autorization to send analytics events. Do you want to allow guests and unauthenticated users to send analytics events? (we recommend you allow this when getting started) `Yes`
-
amplify push
-
Copy
amplifyconfiguration.json
asAWSPinpointAnalyticsPluginIntegrationTests-amplifyconfiguration.json
inside~/.aws-amplify/amplify-ios/testconfiguration/
cp amplifyconfiguration.json ~/.aws-amplify/amplify-ios/testconfiguration/AWSPinpointAnalyticsPluginIntegrationTests-amplifyconfiguration.json
-
You can now run all of the integration tests.
-
You can run
amplify console analytics
to check what happens at the backend.