Release 0.24.0 by predatorx7 · Pull Request #40 · reclaimprotocol/reclaim-inapp-reactnative-sdk

predatorx7 · 2025-11-23T22:49:13Z

Summary by CodeRabbit

New Features
- Added console-logging control and a public API to enable/disable it; session update events now include metadata.
Bug Fixes
- Fixed repository/discussion links and bumped package & SDK versions.
Documentation
- Updated installation, migration, contributing guides, added troubleshooting and a v0.24.0 changelog entry.
Chores
- Upgraded Node/Yarn/tooling, refreshed CI/workflow and caching, simplified Android/iOS example configs, and cleaned ignore/build artifacts.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

coderabbitai · 2025-11-23T22:49:22Z

Caution

Review failed

The pull request is closed.

Walkthrough

This PR updates SDK and tooling to v0.24.0, adds a cross-platform setConsoleLogging API (JS/Android/iOS), consolidates package/namespace names to inapprnsdk, removes new‑architecture conditional logic, overhauls CI/build configs and caching, and updates docs and example workspace files.

Changes

Cohort / File(s)	Summary
Repository & Tooling `.gitattributes`, `.nvmrc`, `.yarnrc.yml`, `package.json`, `tsconfig.json`, `tsconfig.build.json`, `turbo.json`, `.gitignore`, `CHANGELOG.md`, `CONTRIBUTING.md`, `lefthook.yml`	Version/tooling updates (Node/Yarn/Gradle/TS/Turbo), package.json restructure and version bump to 0.24.0, .gitattributes tweak, .gitignore changes, changelog and contributing edits, and removal of lefthook config.
CI / GitHub Actions & Templates `.github/workflows/ci.yml`, `.github/actions/setup/action.yml`, `.github/ISSUE_TEMPLATE/bug_report.yml`, `.github/ISSUE_TEMPLATE/config.yml`	Adds composite setup action and full CI workflow with advanced caching/Turbo logic; minor issue template render addition and URL fixes.
TypeScript / Lint / Babel `eslint.config.mjs`, `babel.config.js`, `user-workspace/babel.config.js`	New Flat ESLint config, Babel presets overridden to handle node_modules differently, removal of some example babel plugins.
JS API Surface `src/NativeInappRnSdk.ts`, `src/index.tsx`	Adds `SetConsoleLoggingOptions` and `setConsoleLogging` to spec and ReclaimVerification, updates emitter typings to CodegenTypes, adds metadata to session update events, and implements PlatformImpl console-logging call with error wrapping.
Android Build & Native `android/build.gradle`, `android/gradle/wrapper/...`, `android/src/main/AndroidManifest.xml`, `android/src/main/java/com/reclaimprotocol/inapprnsdk/*`, `react-native.config.js`	Remove dynamic storage repos and new-arch conditionals, hardcode namespace `com.reclaimprotocol.inapprnsdk`, bump in-app SDK to 0.24.0, gradle wrapper/property updates, package rename, added Kotlin native method `setConsoleLogging`, and deletion of `react-native.config.js` export.
iOS Build & Native `InappRnSdk.podspec`, `ios/InappRnSdk.h`, `ios/InappRnSdk.mm`, `ios/inapp_rn_sdk/Api.swift`, `ios/InappRnSdk-Bridging-Header.h`	Podspec dependency bumped to `~> 0.24.0` and header/path adjustments; migrate to spec-based native interface; add ObjC moduleName and bridge `setConsoleLogging`; add Swift async `setConsoleLogging`; remove bridging header.
Example / User Workspace `user-workspace/package.json`, `user-workspace/src/`, `user-workspace/android/`, `user-workspace/ios/*`, `user-workspace/metro.config.js`	Example rename and dependency upgrades (React/RN), env moves from `@env` to `env.json`, AppDelegate refactor to UIApplicationDelegate + ReactNativeDelegate, Podfile pre_install removal, android namespace/appId updates, added INTERNET permission, Gradle/tooling bumps, removal of demo override app.
Samples & Scripts `samples//android/build.gradle`, `samples//package.json`, `user-workspace/* scripts`	Adds local Maven repo entries in some samples, bumps sample dependency to `^0.21.0`, adds `gen:ios`/`gen:android` scripts and simplifies `build:ios`.
Docs & Migration `documentation/*.md`, `migration.md`, `CHANGELOG.md`	Docs updated for v0.24.0, install/migration docs updated with new pod versions and new iOS XCScheme troubleshooting notes.
Misc `eslint.config.mjs`, `babel.config.js`, `metro.config.js`, various minor files	Misc config reshuffles, Metro config migration for monorepo, removal/addition of small files across workspaces.

Sequence Diagram(s)

sequenceDiagram
    participant JS as JavaScript
    participant Platform as PlatformImpl
    participant Native as NativeModule (Bridge/JSI)
    participant SDK as ReclaimInAppSdk (native)

    JS->>Platform: setConsoleLogging({ enabled })
    activate Platform
    Platform->>Native: setConsoleLogging({ enabled: boolean })
    activate Native
    Native->>SDK: ReclaimVerification.setConsoleLogging(enabled)
    activate SDK
    SDK-->>Native: success / error
    deactivate SDK
    alt success
        Native-->>Platform: resolve
    else error
        Native-->>Platform: reject (wrapped as ReclaimPlatformException)
    end
    deactivate Native
    Platform-->>JS: Promise<void> resolved/rejected
    deactivate Platform

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Focus review on:

CI workflow and Turbo/cache conditional logic across Android/iOS jobs.
Cross-platform implementation of setConsoleLogging (JS typings, Android Kotlin, iOS ObjC/Swift) and error mapping.
Android/iOS package/namespace renames and build config removals (new-arch conditionals, generated sources).
Example AppDelegate refactor and removed Podfile pre_install/codegen step.
package.json and tooling upgrades (Yarn 4, Node pin, ESLint/Babel changes).

Possibly related PRs

Updates inapp module dependency to 0.10.7 #26 — overlapping dependency bumps for InappRnSdk/inapp_sdk in podspec and Android build files.
Update inapp sdk #31 — related Android native bridge changes (InappRnSdkModule) that intersect with setConsoleLogging additions.
Update bug_report.yml #5 — edits to .github/ISSUE_TEMPLATE/bug_report.yml (same textarea render change).

Suggested reviewers

Karam19
Sajjad21990
ChinmayMhatre

"🐰 Hop, skip, and refactor—I've leapt with cheer,
From 0.18 to 0.24, the logs appear;
Names aligned and CI now sings,
Console set, new builds take wing. ✨"

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run `@coderabbitai generate docstrings` to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title 'Release 0.24.0' directly reflects the main objective, which is to release version 0.24.0 of the SDK as evident from comprehensive version bumps throughout the changeset.

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f81aabf and 184edfd.

📒 Files selected for processing (1)

samples/example_new_arch/package.json (1 hunks)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai

Actionable comments posted: 6

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

user-workspace/src/App.tsx (1)
55-88: Replace console.assert() with early validation to prevent SDK errors with missing credentials

The code at lines 66-67 of user-workspace/src/App.tsx uses console.assert() which does not prevent execution in production—it only logs in development. The code then proceeds to call reclaimVerification.startVerification() with potentially empty credentials (lines 80-81 use ?? '' fallback), which will trigger an SDK error instead of providing clear feedback to the user.

Implement the suggested fix to validate config values before proceeding:
case 'providerId':
  if (!config.REACT_APP_RECLAIM_APP_ID || !config.REACT_APP_RECLAIM_APP_SECRET) {
    Snackbar.show({
      text: 'Configure REACT_APP_RECLAIM_APP_ID and REACT_APP_RECLAIM_APP_SECRET in .env.json',
      duration: Snackbar.LENGTH_LONG,
    });
    return;
  }
  break;
This matches the error-handling pattern used elsewhere in the file (e.g., inputText validation at lines 56-62) and prevents confusing runtime errors from the SDK.

Note: The same pattern exists in samples/example_expo/app/(home)/_layout.tsx, samples/example_new_arch/src/App.tsx, and samples/example_new_arch/src/App.overrides.tsx—consider applying the fix consistently across all example files as well.
ios/inapp_rn_sdk/Api.swift (1)
588-618: Missing metadata forwarding and unsafe force-unwrap.

Two issues to consider:

The metadata parameter (line 591) is received but not forwarded to _updateSession. If the SDK provides session metadata, it won't reach the React Native callback.

The force-unwrap of statusString! on line 618 will crash if a future SDK version adds a new enum case that isn't handled in the switch.

Consider adding a default case and forwarding metadata:
       case .AI_PROOF_SUBMITTED:
         statusString = "AI_PROOF_SUBMITTED"
+      @unknown default:
+        statusString = "UNKNOWN"
       }
       let replyId = Api.setReplyCallback(completion)
-      self._updateSession(sessionId, statusString!, replyId)
+      self._updateSession(sessionId, statusString ?? "UNKNOWN", replyId)

🧹 Nitpick comments (17)

user-workspace/Gemfile (1)
4-4: Ruby 3.4 compatibility update looks good; address gem ordering convention.

The Ruby version bump to >= 3.4.7 and the addition of stdlib replacement gems (bigdecimal, logger, benchmark, mutex_m, nkf) are appropriate for Ruby 3.4 compatibility. The explanatory comment on line 12 clearly documents the reason.

However, RuboCop's Bundler/OrderedGems rule flags alphabetical ordering violations in the gem entries. Per coding conventions, reorder the gems alphabetically within their sections.

Apply this diff to sort gems alphabetically:
-gem 'cocoapods', '>= 1.13', '!= 1.15.0', '!= 1.15.1'
-gem 'activesupport', '>= 6.1.7.5', '!= 7.1.0'
-gem 'xcodeproj', '< 1.26.0'
-gem 'concurrent-ruby', '< 1.3.4'
+gem 'activesupport', '>= 6.1.7.5', '!= 7.1.0'
+gem 'cocoapods', '>= 1.13', '!= 1.15.0', '!= 1.15.1'
+gem 'concurrent-ruby', '< 1.3.4'
+gem 'xcodeproj', '< 1.26.0'

 # Ruby 3.4.0 has removed some libraries from the standard library.
-gem 'bigdecimal'
-gem 'logger'
 gem 'benchmark'
+gem 'bigdecimal'
+gem 'logger'
 gem 'mutex_m'
 # Added gem 'nkf' to provide kconv functionality which was removed from Ruby 3.4 standard library.
 gem 'nkf'
As per coding guidelines and RuboCop's Bundler/OrderedGems rule.

Also applies to: 12-18
samples/example_expo/package.json (1)

16-46: Confirm sample depends on the intended SDK version

The sample now pins @reclaimprotocol/inapp-rn-sdk to ^0.21.0, while this repo is preparing a 0.24.0 release. If the NPM package will also be 0.24.x, you may want the sample to track that (^0.24.0) so users test against the latest public SDK.

If 0.21.x is intentionally the latest published NPM version for now, consider leaving a short comment in the README or sample to avoid confusion.

samples/example_new_arch/package.json (1)

13-18: Align new‑arch sample SDK version with the main release

This sample also targets @reclaimprotocol/inapp-rn-sdk ^0.21.0. Given the repo is releasing 0.24.0, consider whether these examples should instead track ^0.24.0 so both samples and docs line up with the advertised release.

If 0.21.x is intentionally the latest published NPM version for now, keeping both samples on ^0.21.0 is fine—just worth confirming.

tsconfig.build.json (1)

3-3: Verify build scope after relaxing exclude.

tsconfig.build.json now only excludes example and lib, so any TS files under samples or user-workspace (if present) will be part of the build. That may be desired for type coverage, but it can also pull consumer/sample code into the library build or surface unrelated TS errors.

Consider re‑excluding those directories if they are meant to stay out of the library build, or confirm that your build and CI behave as expected with the broader scope.

user-workspace/android/gradlew.bat (1)

1-4: Wrapper changes look fine; -classpath is redundant with -jar.

Adding the MIT header and explicitly clearing CLASSPATH before launching Java both look good.

Invoking the wrapper via -jar "%APP_HOME%\gradle\wrapper\gradle-wrapper.jar" is a standard pattern; the extra -classpath "%CLASSPATH%" is unnecessary but not harmful because java -jar ignores the classpath.

If you want to simplify, you can drop the -classpath portion and just rely on -jar.

Also applies to: 78-82

.gitignore (1)

46-52: Ignore patterns align with pods, vendor, and codegen outputs.

The new entries for example/*/Pods and example/vendor/, the global *.tgz ignore, and the ios/generated / android/generated ignores are consistent with keeping dependency artifacts and generated code out of version control.

Just ensure that any generated folders you rely on in published packages are not among these ignored paths; otherwise, this looks good.

Also applies to: 82-86
user-workspace/android/gradlew (1)
90-90: Wrapper -jar usage is fine; CLASSPATH handling is now mostly redundant.

The changes to compute APP_HOME, initialize CLASSPATH, and invoke:
-jar "$APP_HOME/gradle/wrapper/gradle-wrapper.jar"
are a valid way to start the Gradle wrapper and should work across supported environments.

Given that java -jar ignores the classpath, both the CLASSPATH variable and the -classpath "$CLASSPATH" argument are effectively unused now. You can keep them (harmless) or simplify the script later by removing the classpath bits to stay closer to Gradle’s stock template.

Also applies to: 117-117, 207-217
babel.config.js (1)
2-11: Make node_modules regex robust across OSes

/\/node_modules\// depends on forward slashes; on Windows paths using backslashes it may not match as intended. Consider a cross‑platform pattern instead:
-      exclude: /\/node_modules\//,
+      exclude: /node_modules[\\/]/,
...
-      include: /\/node_modules\//,
+      include: /node_modules[\\/]/,
This should behave the same on macOS/Linux while also covering Windows path separators.
documentation/install-expo.md (1)
70-92: Minor iOS section wording/capitalization tweaks

A couple of small polish items:

Prefer the platform’s spelling iOS instead of IOS in the heading.

Consider clarifying that this XCScheme env var change is only needed when you hit the specific performance issue, to avoid users thinking it’s always required.

For example:
-### IOS XCScheme Configuration
+### iOS XCScheme configuration
android/src/main/java/com/reclaimprotocol/inapprnsdk/InappRnSdkModule.kt (1)
234-252: Clarify behavior when enabled is missing or args is null

Implementation is consistent with other bridge methods and uses runOnUiQueueThread + onPlatformException, which is good. The only subtle point is how missing input is handled:
val enabled = if (args != null) (getBoolean(args, "enabled") == true) else false
If args is null or doesn’t contain enabled, this silently disables console logging (enabled = false) and still resolves successfully. If the JS/TS API is meant to require enabled, you may want to fail fast instead of defaulting to false.

For example:
-  ) {
-    val enabled = if (args != null) (getBoolean(args, "enabled") == true) else false
+  ) {
+    if (args == null || getBoolean(args, "enabled") == null) {
+      promise?.reject(IllegalArgumentException("Missing 'enabled' flag for setConsoleLogging"))
+      return
+    }
+    val enabled = getBoolean(args, "enabled") == true
This makes incorrect usage visible to callers instead of silently changing logging behavior.
.github/actions/setup/action.yml (1)
1-36: Consider running yarn install --immutable even on cache hits

The composite action is well structured (pinned actions, sensible cache key, restore/save split). One potential improvement: you currently skip yarn install --immutable entirely on any cache hit:
- if: steps.yarn-cache.outputs.cache-hit != 'true'
Even with a cache hit, a fast yarn install --immutable helps guarantee that node_modules exactly matches yarn.lock and catches drift early. You could remove the if (or relax it) on the install step and keep the if only on the cache/save step.

This trades a bit of runtime for stronger reproducibility and fewer “works with stale cache” surprises.
user-workspace/src/App.tsx (1)
22-25: Clarify .env.json usage and avoid accidentally shipping secrets

Switching to a JSON config for the example makes local setup straightforward, but the comments could better emphasize scope and location, and you should ensure this file isn’t checked in with real secrets.

Consider tightening the comments and clarifying it’s for local/testing only:
-// Duplicate ./.env.example.json to ./.env.json and enter your reclaim app id & secrets
-// Note: reclaim app id & secrets is not needed if you start verification at backend 
+// Duplicate `.env.example.json` to `.env.json` in this directory and enter your Reclaim app id & secret for local testing only.
+// Note: For production, prefer backend-initiated verification and avoid shipping app secrets in the bundled app.
Also, make sure your TypeScript/Metro config supports JSON imports (e.g. resolveJsonModule in tsconfig.json) so import config from './.env.json'; type‑checks cleanly.
ios/InappRnSdk.mm (1)
416-428: setConsoleLogging bridge wiring looks correct; consider aligning error code naming

The new setConsoleLogging bridge cleanly forwards the enabled flag to the API and mirrors the completion‑handler pattern used elsewhere; that part looks good.

For consistency with other methods (VERIFICATION_ERROR, OVERRIDE_ERROR, VERIFICATION_OPTIONS_ERROR), you might want to standardize the error code string, e.g.:
-                      reject(@"SET_CONSOLE_LOGGING",
-                             @"Error on setting console logging", error);
+                      reject(@"SET_CONSOLE_LOGGING_ERROR",
+                             @"Error on setting console logging", error);
Also worth double‑checking that the spec type SetConsoleLoggingOptions always provides a non‑optional enabled so args.enabled() can’t be absent.
.github/workflows/ci.yml (1)
81-87: Turbo cache detection is clever but fragile.

The approach works, but parsing Turbo's JSON output with node -p is fragile. If the output structure changes in a Turbo upgrade, the detection will silently fail (returning undefined instead of "HIT"), causing unnecessary rebuilds rather than errors.

Consider adding error handling or a fallback:
      - name: Check turborepo cache for Android
        run: |
-         TURBO_CACHE_STATUS=$(node -p "($(yarn turbo run build:android --cache-dir="${{ env.TURBO_CACHE_DIR }}" --dry=json)).tasks.find(t => t.task === 'build:android').cache.status")
+         TURBO_CACHE_STATUS=$(node -p "($(yarn turbo run build:android --cache-dir="${{ env.TURBO_CACHE_DIR }}" --dry=json)).tasks.find(t => t.task === 'build:android')?.cache?.status || 'MISS'")

          if [[ $TURBO_CACHE_STATUS == "HIT" ]]; then
            echo "turbo_cache_hit=1" >> $GITHUB_ENV
          fi
src/index.tsx (1)
63-70: Redundant boolean coercion.

The enabled == true coercion is applied in the public API (line 68) even though enabled is already typed as boolean. This is defensive but redundant. The same pattern is repeated in PlatformImpl.setConsoleLogging (line 670).

Consider simplifying since the parameter is already typed:
  public setConsoleLogging(
    enabled: boolean
  ) {
    return this.platform.setConsoleLogging({
-     enabled: enabled == true,
+     enabled,
    });
  }
src/NativeInappRnSdk.ts (2)

300-317: Re‑evaluate SessionUpdateRequestEvent.metadata nullability

metadata is now a required string on SessionUpdateRequestEvent. If some update events don’t include metadata (or older native SDKs don’t populate it), this will be undefined at runtime despite the non‑nullable type. Consider making it optional/nullable (e.g. metadata?: string | null) or ensuring the native layer always sends a non‑empty JSON string, and document that guarantee.

365-367: setConsoleLogging API shape looks consistent; optional arg would be a small DX win

The SetConsoleLoggingOptions shape and setConsoleLogging(args: SetConsoleLoggingOptions): Promise<void> signature are coherent and align with the public wrapper API. If you foresee calls without explicit options (or want symmetry with other …Options patterns that allow null/undefined), you could relax this to args?: SetConsoleLoggingOptions | null, but that’s a nice‑to‑have, not a blocker.

Also applies to: 384-384

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e876efb and d89e017.

⛔ Files ignored due to path filters (19)

.yarn/plugins/@yarnpkg/plugin-interactive-tools.cjs is excluded by !**/.yarn/**
.yarn/plugins/@yarnpkg/plugin-workspace-tools.cjs is excluded by !**/.yarn/**
.yarn/releases/yarn-3.6.1.cjs is excluded by !**/.yarn/**
.yarn/releases/yarn-4.11.0.cjs is excluded by !**/.yarn/**
android/generated/java/com/reclaimprotocol/inapp_rn_sdk/NativeInappRnSdkSpec.java is excluded by !**/generated/**
android/generated/jni/CMakeLists.txt is excluded by !**/generated/**
android/generated/jni/RNInappRnSdkSpec-generated.cpp is excluded by !**/generated/**
android/generated/jni/RNInappRnSdkSpec.h is excluded by !**/generated/**
android/generated/jni/react/renderer/components/RNInappRnSdkSpec/RNInappRnSdkSpecJSI-generated.cpp is excluded by !**/generated/**
android/generated/jni/react/renderer/components/RNInappRnSdkSpec/RNInappRnSdkSpecJSI.h is excluded by !**/generated/**
android/gradle/wrapper/gradle-wrapper.jar is excluded by !**/*.jar
ios/generated/RNInappRnSdkSpec/RNInappRnSdkSpec-generated.mm is excluded by !**/generated/**
ios/generated/RNInappRnSdkSpec/RNInappRnSdkSpec.h is excluded by !**/generated/**
ios/generated/RNInappRnSdkSpecJSI-generated.cpp is excluded by !**/generated/**
ios/generated/RNInappRnSdkSpecJSI.h is excluded by !**/generated/**
user-workspace/Gemfile.lock is excluded by !**/*.lock
user-workspace/android/gradle/wrapper/gradle-wrapper.jar is excluded by !**/*.jar
user-workspace/ios/Podfile.lock is excluded by !**/*.lock
yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (69)

.gitattributes (1 hunks)
.github/ISSUE_TEMPLATE/bug_report.yml (1 hunks)
.github/ISSUE_TEMPLATE/config.yml (1 hunks)
.github/actions/setup/action.yml (1 hunks)
.github/workflows/ci.yml (1 hunks)
.gitignore (2 hunks)
.nvmrc (1 hunks)
.yarnrc.yml (1 hunks)
CHANGELOG.md (1 hunks)
CONTRIBUTING.md (3 hunks)
InappRnSdk.podspec (1 hunks)
android/build.gradle (4 hunks)
android/gradle/wrapper/gradle-wrapper.properties (0 hunks)
android/gradlew (0 hunks)
android/gradlew.bat (0 hunks)
android/src/main/AndroidManifest.xml (1 hunks)
android/src/main/AndroidManifestNew.xml (0 hunks)
android/src/main/java/com/reclaimprotocol/inapprnsdk/InappRnSdkModule.kt (2 hunks)
android/src/main/java/com/reclaimprotocol/inapprnsdk/InappRnSdkPackage.kt (1 hunks)
android/src/main/java/com/reclaimprotocol/inapprnsdk/JsonExtension.kt (1 hunks)
babel.config.js (1 hunks)
documentation/install-expo.md (2 hunks)
documentation/install-no-framework.md (3 hunks)
documentation/migration.md (3 hunks)
eslint.config.mjs (1 hunks)
ios/InappRnSdk-Bridging-Header.h (0 hunks)
ios/InappRnSdk.h (1 hunks)
ios/InappRnSdk.mm (2 hunks)
ios/inapp_rn_sdk/Api.swift (3 hunks)
lefthook.yml (0 hunks)
package.json (5 hunks)
react-native.config.js (0 hunks)
samples/example_expo/android/build.gradle (1 hunks)
samples/example_expo/package.json (1 hunks)
samples/example_new_arch/android/build.gradle (1 hunks)
samples/example_new_arch/android/settings.gradle (1 hunks)
samples/example_new_arch/package.json (1 hunks)
src/NativeInappRnSdk.ts (4 hunks)
src/index.tsx (5 hunks)
tsconfig.build.json (1 hunks)
tsconfig.json (2 hunks)
turbo.json (2 hunks)
user-workspace/.env.example (0 hunks)
user-workspace/.gitignore (1 hunks)
user-workspace/Gemfile (1 hunks)
user-workspace/__mocks__/react-native-snackbar.js (0 hunks)
user-workspace/android/.gitignore (0 hunks)
user-workspace/android/app/build.gradle (1 hunks)
user-workspace/android/app/src/main/AndroidManifest.xml (1 hunks)
user-workspace/android/app/src/main/java/reclaimprotocol/inapprnsdk/example/MainActivity.kt (1 hunks)
user-workspace/android/app/src/main/java/reclaimprotocol/inapprnsdk/example/MainApplication.kt (2 hunks)
user-workspace/android/build.gradle (1 hunks)
user-workspace/android/gradle.properties (1 hunks)
user-workspace/android/gradle/wrapper/gradle-wrapper.properties (1 hunks)
user-workspace/android/gradlew (3 hunks)
user-workspace/android/gradlew.bat (2 hunks)
user-workspace/android/settings.gradle (1 hunks)
user-workspace/babel.config.js (0 hunks)
user-workspace/ios/InappRnSdkExample.xcodeproj/project.pbxproj (11 hunks)
user-workspace/ios/InappRnSdkExample.xcodeproj/xcshareddata/xcschemes/InappRnSdkExample.xcscheme (0 hunks)
user-workspace/ios/InappRnSdkExample/AppDelegate.swift (1 hunks)
user-workspace/ios/InappRnSdkExample/Info.plist (1 hunks)
user-workspace/ios/Podfile (0 hunks)
user-workspace/metro.config.js (2 hunks)
user-workspace/package.json (1 hunks)
user-workspace/src/.env.example.json (1 hunks)
user-workspace/src/App.overrides.tsx (0 hunks)
user-workspace/src/App.tsx (1 hunks)
user-workspace/src/env.d.ts (0 hunks)

💤 Files with no reviewable changes (15)

android/gradle/wrapper/gradle-wrapper.properties
lefthook.yml
android/gradlew
user-workspace/mocks/react-native-snackbar.js
user-workspace/src/env.d.ts
android/src/main/AndroidManifestNew.xml
user-workspace/.env.example
android/gradlew.bat
react-native.config.js
user-workspace/src/App.overrides.tsx
user-workspace/android/.gitignore
user-workspace/ios/InappRnSdkExample.xcodeproj/xcshareddata/xcschemes/InappRnSdkExample.xcscheme
user-workspace/ios/Podfile
ios/InappRnSdk-Bridging-Header.h
user-workspace/babel.config.js

🧰 Additional context used

🧬 Code graph analysis (4)

eslint.config.mjs (2)

user-workspace/metro.config.js (1)

path (1-1)

user-workspace/babel.config.js (1)

path (1-1)

src/NativeInappRnSdk.ts (3)

src/index.tsx (1)

SetConsoleLoggingOptions (179-180)

android/src/main/java/com/reclaimprotocol/inapprnsdk/InappRnSdkModule.kt (1)

reply (420-433)

ios/inapp_rn_sdk/Api.swift (1)

reply (21-35)

src/index.tsx (1)

src/NativeInappRnSdk.ts (1)

SetConsoleLoggingOptions (365-367)

ios/inapp_rn_sdk/Api.swift (2)

android/src/main/java/com/reclaimprotocol/inapprnsdk/InappRnSdkModule.kt (1)

setConsoleLogging (234-252)

src/index.tsx (3)

setConsoleLogging (64-70)

setConsoleLogging (665-678)

ReclaimVerification (12-71)

🪛 actionlint (1.7.8)

.github/workflows/ci.yml

157-157: property "cocoapods-cache" is not defined in object type {}

(expression)

🪛 Clang (14.0.6)

ios/InappRnSdk.h

[error] 1-1: 'Foundation/Foundation.h' file not found

(clang-diagnostic-error)

🪛 dotenv-linter (4.0.0)

user-workspace/src/.env.example.json

[warning] 1-1: [KeyWithoutValue] The { key should be with a value or have an equal sign

(KeyWithoutValue)

[warning] 1-1: [LeadingCharacter] Invalid leading character detected

(LeadingCharacter)

[warning] 2-2: [IncorrectDelimiter] The "REACT_APP_RECLAIM_APP_ID": "", key has incorrect delimiter

(IncorrectDelimiter)

[warning] 2-2: [KeyWithoutValue] The "REACT_APP_RECLAIM_APP_ID": "", key should be with a value or have an equal sign

(KeyWithoutValue)

[warning] 2-2: [LeadingCharacter] Invalid leading character detected

(LeadingCharacter)

[warning] 2-2: [UnorderedKey] The "REACT_APP_RECLAIM_APP_ID": "", key should go before the { key

(UnorderedKey)

[warning] 3-3: [IncorrectDelimiter] The "REACT_APP_RECLAIM_APP_SECRET": "", key has incorrect delimiter

(IncorrectDelimiter)

[warning] 3-3: [KeyWithoutValue] The "REACT_APP_RECLAIM_APP_SECRET": "", key should be with a value or have an equal sign

(KeyWithoutValue)

[warning] 3-3: [LeadingCharacter] Invalid leading character detected

(LeadingCharacter)

[warning] 3-3: [UnorderedKey] The "REACT_APP_RECLAIM_APP_SECRET": "", key should go before the { key

(UnorderedKey)

[warning] 4-4: [IncorrectDelimiter] The "REACT_APP_RECLAIM_CAPABILITY_ACCESS_TOKEN": "" key has incorrect delimiter

(IncorrectDelimiter)

[warning] 4-4: [KeyWithoutValue] The "REACT_APP_RECLAIM_CAPABILITY_ACCESS_TOKEN": "" key should be with a value or have an equal sign

(KeyWithoutValue)

[warning] 4-4: [LeadingCharacter] Invalid leading character detected

(LeadingCharacter)

[warning] 4-4: [UnorderedKey] The "REACT_APP_RECLAIM_CAPABILITY_ACCESS_TOKEN": "" key should go before the { key

(UnorderedKey)

[warning] 5-5: [EndingBlankLine] No blank line at the end of the file

(EndingBlankLine)

[warning] 5-5: [KeyWithoutValue] The } key should be with a value or have an equal sign

(KeyWithoutValue)

[warning] 5-5: [LeadingCharacter] Invalid leading character detected

(LeadingCharacter)

🪛 LanguageTool

documentation/migration.md

[grammar] ~5-~5: Ensure spelling is correct
Context: ... ReclaimInAppSdk cocoapod if you have overriden this dependency in your Podfile. Late...