@dynatrace/cordova-plugin 2.321.1 → 2.325.1

package/README.md

@@ -24,15 +24,15 @@ For information as to why this is necessary, read more [here](#migration-from-ma
   * Java 11
 * For iOS users: Minimum iOS 12
 * For JavaScript Agent: access to API of cluster
-* Node: >= 18.x
+* Node: >= 20.x
 * Cordova: 10+
 
 ## Agent Versions
 
-This agent versions are configured in this plugin:
+These agent versions are configured in this plugin:
 
-* Android Agent: 8.321.1.1009
-* iOS Agent: 8.321.1.1007
+* Android Agent: 8.325.1.1007
+* iOS Agent: 8.325.1.1012
 
 ## Quick Setup
 
@@ -218,7 +218,7 @@ There is flag for updating the CSP (Content Security Policy). By default this va
 
 ### Cookie Proxy
 
-Issues with cookies are somehow a persistent companion in Ionic or Capacitor applications. Therefor we provide a proxy script which is wrapping the document.cookie API and are storing the cookies which are important for the Dynatrace Agents in the session storage. Of course this wrapping is still calling the original API. Please see the [Capacitor Cookie Proxy](#capacitor-cookie-proxy) section below if you are using `CapacitorCookies` in your application. If not, please see the configuration below.
+Issues with cookies are somehow a persistent companion in Ionic or Capacitor applications. Therefore we provide a proxy script which is wrapping the document.cookie API and are storing the cookies which are important for the Dynatrace Agents in the session storage. Of course this wrapping is still calling the original API. Please see the [Capacitor Cookie Proxy](#capacitor-cookie-proxy) section below if you are using `CapacitorCookies` in your application. If not, please see the configuration below.
 
 Per default the cookie proxy is turned off. To make use of this proxy you need to enable it in the cordova configuration in the dynatrace.config.js:
 
@@ -278,7 +278,7 @@ module.exports = {
 }
 ```
 
-The native configuration contain all the settings which are necessary for the Mobile Agent(s). You can find all the available properties in the [documentation](#official-documentation) of the mobile agent.
+The native configuration contains all the settings which are necessary for the Mobile Agent(s). You can find all the available properties in the [documentation](#official-documentation) of the mobile agent.
 
 The content of the `ios.config` property will be directly copied to the plist file. The content of the `android.config` property will be directly copied to the gradle file.
 
@@ -389,7 +389,7 @@ If you are having an issue retrieving the JavaScript Agent and see an error mess
 Could not retrieve the JavaScript Agent! - Could not retrieve agent optionsError: unable to verify the first certificate
 ```
 
-You are able to bypass those errors at your **OWN RISK** by using `allowanycert: true` within the `js` property. This will ignore the fact that the SSL connection is not secure (e.g. because of invalid certificate) and will retrieve the JavaScript Agent snippet anyways. An example would look like this:
+You are able to bypass those errors at your **OWN RISK** by using `allowanycert: true` within the `js` property. This will ignore the fact that the SSL connection is not secure (e.g. because of an invalid certificate) and will retrieve the JavaScript Agent snippet anyways. An example would look like this:
 
 ```js
 module.exports = {
@@ -604,7 +604,7 @@ Within Cordova it is also possible to use libraries that are executing native we
 
 Those libraries are not executing the request within the JS scope but will rather call a JavaScript<->Native interface and will trigger the request natively. This means that our JavaScript OneAgent will not be able to detect the request. Additionally a resulting user action can be dropped as well. To prevent this behaviour you need to manually apply headers to your request. 
 
-Before using this feature you need to turn of web request instrumentation on iOS. You can do this by adding the following configuration to the dynatrace.config.js:
+Before using this feature you need to turn off web request instrumentation on iOS. You can do this by adding the following configuration to the dynatrace.config.js:
 
 ```js
 ios: {
@@ -623,7 +623,7 @@ MyTestRequest request = new MyTestRequest("MY_URL");
 
 let interceptorUtils = dynatraceMobile.getNativeNetworkInterceptorUtils();
 
-// Creation of a user action with automated dection of the user action - e.g. click on
+// Creation of a user action with automated detection of the user action - e.g. click on
 let actionId = interceptorUtils.enterNativeRequestAction("MY_URL", "Name of HTTP Framework", "Optional Action Fallbackname");
 
 // Adding headers to your request - Take a look into typings.d.ts for the format of DynatraceNativeRequestHeaders
@@ -639,11 +639,11 @@ interceptorUtils.leaveNativeRequestAction(actionId);
 
 **Attention:** This feature requires a instrumented webserver with version 1.211.x running at your Mobile First server. Also, only version >= 8.x.x is supported.
 
-If you are using IBM Mobile First you might take a look at our `dynatraceMobile.getMobileFirstNetworkInterceptor()`. This interceptor gives you the option to make the request going to Mobile First more visible. The Mobile First library is doing native mobile web requests, that's why those request can't be linked with user actions happening in the web part. 
+If you are using IBM Mobile First you might take a look at our `dynatraceMobile.getMobileFirstNetworkInterceptor()`. This interceptor gives you the option to make the request going to Mobile First more visible. The Mobile First library is doing native mobile web requests, that's why those requests can't be linked with user actions happening in the web part. 
 
 This interceptor is creating wrapping actions according to the user input that happened right before the request. By this modification you will be able to see the request in the user session linked with user actions.
 
-Before using this feature you need to turn of web request instrumentation on iOS. You can do this by adding the following configuration to the dynatrace.config.js:
+Before using this feature you need to turn off web request instrumentation on iOS. You can do this by adding the following configuration to the dynatrace.config.js:
 
 After Mobile First has been initialized make the following call:
 
@@ -714,7 +714,7 @@ This will download the version `1.191.1` of our plugin. In general we recommend
 * If both custom CLI arguments and [custom configuration arguments](#cordova-configuration) are used, custom CLI arguments will be used.
 * Custom arguments will only work with Capacitor based projects if you directly modify the "capacitor:sync:after" command. (See example below)
 
-Our scripts assumes that the usual cordova project structure is given. The following arguments can be specified for our instrumentation script if the project structure is different.
+Our script assumes that the usual cordova project structure is given. The following arguments can be specified for our instrumentation script if the project structure is different.
 
 * `--gradle=C:\MyCordovaAndroidProject\platforms\android\build.gradle` - the location of the root build.gradle file. We will assume that the other gradle file resides in `/app/build.gradle`. This will add all agent dependencies automatically for you and will update the configuration.
 * `--plist=C:\MyCordovaIOSProject\platforms\ios\projectName\projectName-Info.plist` - Tell the script where your Info.plist file is. The plist file is used for updating the configuration for the agent. 
@@ -750,7 +750,7 @@ For the local script file, we copy the specified file 1:1. It is best to downloa
 
 ## Migration from major version 1 to 2
 
-The id has now changed for the plugin from `dynatrace-cordova-plugin` to `@dyntrace/cordova-plugin`. Because of this, there can be some issues with the upgrading of the plugin from major version `1.xxx.x` to `2.xxx.x`. You will likely see the following error if you are just trying to install the newest version of the plugin:
+The id has now changed for the plugin from `dynatrace-cordova-plugin` to `@dynatrace/cordova-plugin`. Because of this, there can be some issues with the upgrading of the plugin from major version `1.xxx.x` to `2.xxx.x`. You will likely see the following error if you are just trying to install the newest version of the plugin:
 
 ```
 Error during processing of action! Attempting to revert...
@@ -784,7 +784,7 @@ make sure you insert some other version like `7.6.4` here:
 var distributionUrl = process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] || 'https\\://services.gradle.org/distributions/gradle-7.6.4-all.zip';
 ```
 
-If you having trouble with this option you can always set the global process property `CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL` :
+If you are having trouble with this option you can always set the global process property `CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL` :
 
 ```
 process.env['CORDOVA_ANDROID_GRADLE_DISTRIBUTION_URL'] = 'https\\://services.gradle.org/distributions/gradle-7.6.4-all.zip';
@@ -862,7 +862,7 @@ The log file will also include a list of your `package.json` *dependencies* and
 
 ## Instrumentation Overhead
 
-When using auto-instrumenation through our plugin, here are some examples of the size differences before and after instrumentation for release builds:
+When using auto-instrumentation through our plugin, here are some examples of the size differences before and after instrumentation for release builds:
 
 | Built with           | App template            | Version     | Size Before     | Size After     | Difference     |
 |----------------------|-------------------------|-------------|-----------------|----------------|----------------|
@@ -881,7 +881,7 @@ Basically if you have problems with the plugin please have a look into the logs.
 
 * If you see a message like "Error: Could not retrieve the JSAgent! Error: self signed certificate in certificate chain" try to switch the JavaScript Agent configuration from HTTPS to HTTP.
 * If you use live reload (e.g. ionic cordova run android -l) be aware that Ionic/Cordova doesn't use files from the platform folder, so the JavaScript Agent injection will not take place, as we only instrument the temporary platform folder. You are still able to add the copied JS Agent code snippet from the WebUI manually to your index.html (in the source directory). To get to this page, go to your **Web Application** settings and then select **Setup**. Auto-Instrumentation with the Mobile Agent still takes place.
-* If you have problems retrieving the JavaScript Agent and you get error messages that the JavaScript Agent can not be retrieved, you probably don't have access to the API or there is a certificate issue. If this is the certificate use the [allowanycert feature](#allow-any-certification). In any other case a workaround is possible to use the cli and add the `--jsagent=` custom parameter and download the full Javascript Agent and add the path to the downloaded JS Agent file to the custom parameter value - With this the plugin will not retrieve the JS agent and will use the one that is specified.
+* If you have problems retrieving the JavaScript Agent and you get error messages that the JavaScript Agent can not be retrieved, you probably don't have access to the API or there is a certificate issue. If this is the certificate use the [allow any certificate](#allow-any-certificate) feature. In any other case a workaround is possible to use the cli and add the `--jsagent=` custom parameter and download the full Javascript Agent and add the path to the downloaded JS Agent file to the custom parameter value - With this the plugin will not retrieve the JS agent and will use the one that is specified.
 * If you are not seeing data when using Capacitor 3+, please make sure you follow the steps in the [Capacitor Instrumentation](#capacitor-instrumentation) section (more specifically step 4 for the proper commands). Please read the note at the bottom of that section for more information.
 * For Android, if you see an error like "Gradle sync failed: Could not find com.dynatrace.tools.android:gradle-plugin:8.221.1.1005.", please see the [MavenCentral](#mavencentral-in-top-level-gradle-file) section for an example and more information.
 
@@ -904,6 +904,13 @@ When using Apple Pay with WKWebView, there are specific checks that WebKit (Appl
 
 ## Changelog
 
+2.325.1
+* Updated Android (8.325.1.1007) & iOS Agent (8.325.1.1012)
+
+2.323.1
+* Deprecation of Node 18
+* Updated Android (8.323.2.1002) & iOS Agent (8.323.1.1009)
+
 2.321.1
 * Updated Android (8.321.2.1009) & iOS Agent (8.321.1.1007)
 

package/files/iOS/Dynatrace.xcframework/Info.plist

@@ -8,18 +8,15 @@
 			<key>BinaryPath</key>
 			<string>Dynatrace.framework/Dynatrace</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64_x86_64-simulator</string>
+			<string>tvos-arm64</string>
 			<key>LibraryPath</key>
 			<string>Dynatrace.framework</string>
 			<key>SupportedArchitectures</key>
 			<array>
 				<string>arm64</string>
-				<string>x86_64</string>
 			</array>
 			<key>SupportedPlatform</key>
-			<string>ios</string>
-			<key>SupportedPlatformVariant</key>
-			<string>simulator</string>
+			<string>tvos</string>
 		</dict>
 		<dict>
 			<key>BinaryPath</key>
@@ -42,21 +39,24 @@
 			<key>BinaryPath</key>
 			<string>Dynatrace.framework/Dynatrace</string>
 			<key>LibraryIdentifier</key>
-			<string>ios-arm64</string>
+			<string>ios-arm64_x86_64-simulator</string>
 			<key>LibraryPath</key>
 			<string>Dynatrace.framework</string>
 			<key>SupportedArchitectures</key>
 			<array>
 				<string>arm64</string>
+				<string>x86_64</string>
 			</array>
 			<key>SupportedPlatform</key>
 			<string>ios</string>
+			<key>SupportedPlatformVariant</key>
+			<string>simulator</string>
 		</dict>
 		<dict>
 			<key>BinaryPath</key>
 			<string>Dynatrace.framework/Dynatrace</string>
 			<key>LibraryIdentifier</key>
-			<string>tvos-arm64</string>
+			<string>ios-arm64</string>
 			<key>LibraryPath</key>
 			<string>Dynatrace.framework</string>
 			<key>SupportedArchitectures</key>
@@ -64,7 +64,7 @@
 				<string>arm64</string>
 			</array>
 			<key>SupportedPlatform</key>
-			<string>tvos</string>
+			<string>ios</string>
 		</dict>
 	</array>
 	<key>CFBundlePackageType</key>