Update test app (#304)

* chore(deps): update y18n from 3.2.1 to 4.0.1

* chore(deps): update react-native in test-app from 0.62.2 to 0.64

* chore(deps): update react-core dependency and deployment ios

* chore(deps); update podfile in test app to reflect react native update

* force run ci

* ci: force run

* ci: force run

* chore(deps): update podfile to match test app names

* chore(deps): update top-level package.json bump react-native from 0.62.2 to 0.64 and babel from 7.4 to 7,12,9

* chore(deps): correct babel version

* chore(deps): bump jest and detox to get around node 14 build error

* chore(deps): update babel-core and ts-tests

* ci: force run

* chore(deps): downgrade typescript

* chore(deps): downgrade jest-mock-console

* chore(deps): change version in analytics.spec.ts

* test: fix jest no input calls

* ci: force run

* fix: fix lint issue with array type

* test: change test-app minSdkVersion to 21

* test: try ios podfile fix

* ci: bump xcode version

* test: update test app detox config

* fix: remove mocha and remove cirleCi config in e2e setup

* fix: deleted vanilla config fix lint

* fix: re-add jest config to core package.json

* fix: revert devDependencies in core package.json

* fix: remove jest Config from core

Co-authored-by: Alan Charles <alan.charles@Alans-MacBook-Pro.local>
Co-authored-by: Prayansh Srivastava <prayansh@gmail.com>

Author: 3 people

.circleci/config.yml

@@ -97,25 +97,10 @@ jobs:
       - *attach
       - run: yarn test-app test:android
 
-  test-ios-vanilla:
-    <<: *job
-    macos:
-      xcode: '11.5.0'
-    steps:
-      - checkout
-      # macOS VMs doesn't support Docker based caches
-      - run: yarn install --frozen-lockfile
-      - *attach
-      - run: brew update-reset
-      - run: brew tap wix/brew
-      - run: brew install wix/brew/applesimutils
-
-      - run: yarn test-app test:ios:vanilla
-
   test-ios-cocoapods:
     <<: *job
     macos:
-      xcode: '11.5.0'
+      xcode: '12.4.0'
     steps:
       - checkout
       # macOS VMs doesn't support Docker based caches
@@ -181,12 +166,6 @@ workflows:
           filters:
             tags:
               only: /.*/
-      - test-ios-vanilla:
-          requires:
-            - build-test-app
-          filters:
-            tags:
-              only: /.*/
       - test-ios-cocoapods:
           requires:
             - build-test-app
@@ -204,7 +183,6 @@ workflows:
           requires:
             - build-test-app
             - test-android
-            - test-ios-vanilla
             - test-ios-cocoapods
             - test-core
             - lint

README.md

@@ -177,6 +177,7 @@ In Xcode:
 | [Facebook App Events](https://www.npmjs.com/package/@segment/analytics-react-native-facebook-app-events-ios) | :white_check_mark: | :x:                | `@segment/analytics-react-native-facebook-app-events-ios` |
 | [Firebase](https://www.npmjs.com/package/@segment/analytics-react-native-firebase)                           | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-firebase`                |
 | [Flurry](https://www.npmjs.com/package/@segment/analytics-react-native-flurry)                               | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-flurry`                  |
+| [Google Analytics](https://www.npmjs.com/package/@segment/analytics-react-native-google-analytics)           | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-google-analytics`        |
 | [Intercom](https://www.npmjs.com/package/@segment/analytics-react-native-intercom)                           | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-intercom`                |
 | [Localytics](https://www.npmjs.com/package/@segment/analytics-react-native-localytics)                       | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-localytics`              |
 | [Mixpanel](https://www.npmjs.com/package/@segment/analytics-react-native-mixpanel)                           | :white_check_mark: | :white_check_mark: | `@segment/analytics-react-native-mixpanel`                |

package.json

@@ -58,7 +58,7 @@
     ]
   },
   "devDependencies": {
-    "@babel/core": "^7.4.0",
+    "@babel/core": "^7.12.9",
     "@commitlint/cli": "^7.0.0",
     "@commitlint/config-conventional": "^7.0.1",
     "codecov": "^3.0.4",
@@ -69,8 +69,8 @@
     "lint-staged": "^7.2.0",
     "npm-run-all": "^4.1.3",
     "prettier": "^1.14.2",
-    "react": "16.8.3",
-    "react-native": "0.62.2",
+    "react": "17.0.1",
+    "react-native": "0.64",
     "rimraf": "^2.6.2"
   },
   "dependencies": {

packages/core/docs/classes/analytics.client.md

@@ -42,10 +42,6 @@
 
 *Defined in [analytics.ts:152](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L152)*
 
-Whether the client is ready to send events to Segment.
-
-This becomes `true` when `.setup()` succeeds. All calls will be queued until it becomes `true`.
-
 ___
 
 ## Methods
@@ -58,10 +54,6 @@ ___
 
 *Defined in [analytics.ts:330](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L330)*
 
-Merge two user identities, effectively connecting two sets of user data as one. This may not be supported by all integrations.
-
-When you learn more about who the group is, you can record that information with group.
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
@@ -80,10 +72,6 @@ ___
 
 *Defined in [analytics.ts:167](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L167)*
 
-Catch React-Native bridge errors
-
-These errors are emitted when calling the native counterpart. This only applies to methods with no return value (`Promise<void>`), methods like `getAnonymousId` do reject promises.
-
 **Parameters:**
 
 | Name | Type |
@@ -101,10 +89,6 @@ ___
 
 *Defined in [analytics.ts:369](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L369)*
 
-Completely disable the sending of any analytics data.
-
-If you have a way for users to actively or passively (sometimes based on location) opt-out of analytics data collection, you can use this method to turn off all data collection.
-
 **Returns:** `Promise`<`void`>
 
 ___
@@ -116,10 +100,6 @@ ___
 
 *Defined in [analytics.ts:359](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L359)*
 
-Enable the sending of analytics data. Enabled by default.
-
-Occasionally used in conjunction with disable user opt-out handling.
-
 **Returns:** `Promise`<`void`>
 
 ___
@@ -131,10 +111,6 @@ ___
 
 *Defined in [analytics.ts:350](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L350)*
 
-Trigger an upload of all queued events.
-
-This is useful when you want to force all messages queued on the device to be uploaded. Please note that not all integrations respond to this method.
-
 **Returns:** `Promise`<`void`>
 
 ___
@@ -146,8 +122,6 @@ ___
 
 *Defined in [analytics.ts:374](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L374)*
 
-Retrieve the anonymousId.
-
 **Returns:** `Promise`<`string`>
 
 ___
@@ -159,10 +133,6 @@ ___
 
 *Defined in [analytics.ts:317](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L317)*
 
-Associate a user with a group, organization, company, project, or w/e _you_ call them.
-
-When you learn more about who the group is, you can record that information with group.
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
@@ -178,19 +148,15 @@ ___
 
 ###  identify
 
-▸ **identify**(user: *`string`*, traits?: *[JsonMap]()*, options?: *[Options]()*): `Promise`<`void`>
+▸ **identify**(user: *`string` \| `null`*, traits?: *[JsonMap]()*, options?: *[Options]()*): `Promise`<`void`>
 
 *Defined in [analytics.ts:304](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L304)*
 
-Associate a user with their unique ID and record traits about them.
-
-When you learn more about who your user is, you can record that information with identify.
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
 | ------ | ------ | ------ | ------ |
-| user | `string` | - |  database ID (or email address) for this user. If you don't have a userId but want to record traits, you should pass nil. For more information on how we generate the UUID and Apple's policies on IDs, see [https://segment.io/libraries/ios#ids](https://segment.io/libraries/ios#ids) |
+| user | `string` \| `null` | - |  database ID (or email address) for this user. If you don't have a userId but want to record traits, you should pass nil. For more information on how we generate the UUID and Apple's policies on IDs, see [https://segment.io/libraries/ios#ids](https://segment.io/libraries/ios#ids) |
 | `Default value` traits | [JsonMap]() |  {} |  A dictionary of traits you know about the user. Things like: email, name, plan, etc. |
 | `Default value` options | [Options]() |  {} |  A dictionary of options, e.g. integrations (thigh analytics integration to forward the event to) |
 
@@ -205,27 +171,6 @@ ___
 
 *Defined in [analytics.ts:213](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L213)*
 
-Append a new middleware to the middleware chain.
-
-Middlewares are a powerful mechanism that can augment the events collected by the SDK. A middleware is a simple function that is invoked by the Segment SDK and can be used to monitor, modify or reject events.
-
-Middlewares are invoked for all events, including automatically tracked events, and external event sources like Adjust and Optimizely. This offers you the ability the customize those messages to fit your use case even if the event was sent outside your source code.
-
-The key thing to observe here is that the output produced by the first middleware feeds into the second. This allows you to chain and compose independent middlewares!
-
-For example, you might want to record the device year class with your events. Previously, you would have to do this everywhere you trigger an event with the Segment SDK. With middlewares, you can do this in a single place :
-
-```js
-import DeviceYearClass from 'react-native-device-year-class'
-
-analytics.middleware(async ({next, context}) =>
-  next({
-    ...context,
-    device_year_class: await DeviceYearClass()
-  })
-)
-```
-
 **Parameters:**
 
 | Name | Type | Description |
@@ -243,10 +188,6 @@ ___
 
 *Defined in [analytics.ts:340](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L340)*
 
-Reset any user state that is cached on the device.
-
-This is useful when a user logs out and you want to clear the identity. It will clear any traits or userId's cached on the device.
-
 **Returns:** `Promise`<`void`>
 
 ___
@@ -258,10 +199,6 @@ ___
 
 *Defined in [analytics.ts:289](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L289)*
 
-Record the screens or views your users see.
-
-When a user views a screen in your app, you'll want to record that here. For some tools like Google Analytics and Flurry, screen views are treated specially, and are different from "events" kind of like "page views" on the web. For services that don't treat "screen views" specially, we map "screen" straight to "track" with the same parameters. For example, Mixpanel doesn't treat "screen views" any differently. So a call to "screen" will be tracked as a normal event in Mixpanel, but get sent to Google Analytics and Flurry as a "screen".
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
@@ -281,8 +218,6 @@ ___
 
 *Defined in [analytics.ts:177](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L177)*
 
-Sets the IDFA value on iOS. Customers are now responsible for collecting IDFA on their own.
-
 **Parameters:**
 
 | Name | Type |
@@ -300,18 +235,6 @@ ___
 
 *Defined in [analytics.ts:252](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L252)*
 
-Setup the Analytics module. All calls made before are queued and only executed if the configuration was successful.
-
-```js
-await analytics.setup('YOUR_WRITE_KEY', {
-  using: [Mixpanel, GoogleAnalytics],
-  trackAppLifecycleEvents: true,
-  ios: {
-    trackDeepLinks: true
-  }
-})
-```
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
@@ -330,10 +253,6 @@ ___
 
 *Defined in [analytics.ts:271](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L271)*
 
-Record the actions your users perform.
-
-When a user performs an action in your app, you'll want to track that action for later analysis. Use the event name to say what the user did, and properties to specify any interesting details of the action.
-
 **Parameters:**
 
 | Name | Type | Default value | Description |
@@ -353,10 +272,6 @@ ___
 
 *Defined in [analytics.ts:225](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L225)*
 
-Use the native configuration.
-
-You'll need to call this method when you configure Analytics's singleton using the native API.
-
 **Returns:** `this`
 
 ___

packages/core/docs/interfaces/analytics.configuration.md

@@ -33,8 +33,6 @@
 
 *Defined in [analytics.ts:119](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L119)*
 
-Android specific settings.
-
 ___
 <a id="debug"></a>
 
@@ -53,8 +51,6 @@ ___
 
 *Defined in [analytics.ts:45](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L45)*
 
-Default project settings to use, if Segment.com cannot be reached. An example configuration can be found here, using your write key: [](https://cdn-settings.segment.com/v1/projects/YOUR_WRITE_KEY/settings)[https://cdn-settings.segment.com/v1/projects/YOUR\_WRITE\_KEY/settings](https://cdn-settings.segment.com/v1/projects/YOUR_WRITE_KEY/settings)
-
 ___
 <a id="flushat"></a>
 
@@ -64,10 +60,6 @@ ___
 
 *Defined in [analytics.ts:53](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L53)*
 
-The number of queued events that the analytics client should flush at. Setting this to `1` will not queue any events and will use more battery.
-
-`20` by default.
-
 ___
 <a id="ios"></a>
 
@@ -77,8 +69,6 @@ ___
 
 *Defined in [analytics.ts:101](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L101)*
 
-iOS specific settings.
-
 ___
 <a id="proxy"></a>
 
@@ -88,10 +78,6 @@ ___
 
 *Defined in [analytics.ts:71](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L71)*
 
-Whether the analytics client should send all requests through your own hosted proxy rather than directly to Segment. See: iOS: [https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#proxy-http-calls](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#proxy-http-calls) android: [https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#proxy-http-calls](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#proxy-http-calls)
-
-Ex. For a desired proxy through `http://localhost:64000/segment` the configuration would look like such { scheme: 'http', host: 'localhost', port: 64000, path: '/segment' }
-
 ___
 <a id="recordscreenviews"></a>
 
@@ -101,10 +87,6 @@ ___
 
 *Defined in [analytics.ts:19](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L19)*
 
-Whether the analytics client should automatically make a screen call when a view controller is added to a view hierarchy. Because the iOS underlying implementation uses method swizzling, we recommend initializing the analytics client as early as possible.
-
-Disabled by default.
-
 ___
 <a id="trackapplifecycleevents"></a>
 
@@ -114,10 +96,6 @@ ___
 
 *Defined in [analytics.ts:26](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L26)*
 
-Whether the analytics client should automatically track application lifecycle events, such as "Application Installed", "Application Updated" and "Application Opened".
-
-Disabled by default.
-
 ___
 <a id="trackattributiondata"></a>
 
@@ -127,8 +105,6 @@ ___
 
 *Defined in [analytics.ts:31](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L31)*
 
-*__deprecated__*: The property should not be used
-
 ___
 <a id="using"></a>
 
@@ -138,7 +114,5 @@ ___
 
 *Defined in [analytics.ts:36](https://github.com/segmentio/analytics-react-native/blob/master/packages/core/src/analytics.ts#L36)*
 
-Register a set of integrations to be used with this Analytics instance.
-
 ___
 

packages/core/package.json

@@ -35,14 +35,14 @@
   },
   "devDependencies": {
     "@types/jest": "^23.3.1",
-    "babel-core": "^6.26.3",
-    "babel-jest": "^23.4.2",
-    "jest": "^23.4.2",
+    "@babel/core": "^7.12.9",
+    "babel-jest": "^26.6.3",
+    "jest": "^26.6.3",
     "jest-mock-console": "^0.4.0",
     "standard-version": "^4.4.0",
-    "ts-jest": "^23.1.3",
-    "ts-node": "^7.0.1",
-    "tslint": "^5.11.0",
+    "ts-jest": "^26.5.5",
+    "ts-node": "^9.1.1",
+    "tslint": "^6.1.3",
     "tslint-config-prettier": "^1.14.0",
     "tslint-plugin-prettier": "^2.0.0",
     "typedoc": "^0.12.0",