Multiple instances of hyperservices - #97
Draft
yuvrajjsingh0 wants to merge 8 commits into
Draft
Conversation
Yaswanth0606
force-pushed
the
multiple-instances-of-hyperservices
branch
from
August 23, 2026 18:23
75e7263 to
82874ea
Compare
Android: - restore legacy API parity (instance field, terminate/re-create, isNull) - key ProcessActivity callbacks per instance; per-instance back-press routing - per-instance merchant view registration with process-wide fallback - forward permission/activity results to every live instance - instance-aware HyperFragmentView with per-view props; invalidate() cleanup - thread-safe keyed maps; reserved/duplicate key guards - resolve ReactHost reflectively so the module compiles on RN < 0.74 - fix rnVersion Groovy scoping crash in isNewArchitectureEnabled (ext.rnVersion) iOS: - fix compile errors in keyed methods; per-key SdkDelegate lifecycle - keyed event channels registered in supportedEvents; dict access synchronized - terminateWithKey/invalidate cleanup; no legacy-delegate hijack - accept PKCS#8 keys and PEM armor in podspec-built merchant view path - podspec: fix RN version detection for dev layouts; apply folly compiler flags JS: - lazy linking error (no import-time throw); platform guards for iOS-only gaps - HyperFragmentView instance prop; per-instance merchant view APIs - document multi-instance integration in README Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- upgrade to React Native 0.79.7 (react 19), AGP 8.9 via RNGP, Gradle 8.13 - Android: compileSdk 36, targetSdk 35, minSdk 24, NDK 27.1, Kotlin 2.0.21 - re-enable Jetifier (Juspay micro-SDKs still reference android.support.*) with react-android/hermes-android on the ignorelist - iOS: RN 0.79 Podfile, bundleURL AppDelegate, folly flags, min iOS 15.1 - generateSign accepts PKCS#8/PKCS#1 and PEM armor on both platforms with descriptive errors surfaced in the UI - demo flows fully instance-aware: doProcess routing, instance back-press, fragment view binding, merchant views via activeInstance, picker UX - remove Flipper (dropped by React Native itself) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
All early returns that skip processing (null key, null activity, missing instance, duplicate/reserved key) now emit a Log.w under the HyperSdkReact tag alongside the existing SdkTracker telemetry, so silent no-ops are visible while debugging. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
React method calls arrive on a single NativeModules thread, so the initiate/terminate race the outer synchronized blocks guarded against cannot occur in practice; the shared helpers still synchronize the work. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Creates are serialized by the NativeModules thread and the map is a ConcurrentHashMap, so the guard-then-put needs no additional locking. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.