guavasure_flutter 0.1.8

Embed GuavaSure pet insurance in Flutter via WebView.

0.1.8

Added

• onGoBack on GuavaSureEmbed — called when the embed mobile nav back button is tapped on the home screen ({ "type": "go-back" }). Requires partner customization uiStyle.mobileNav: enabled on the hosted embed.
• isGoBackBridgeMessage / handleGoBackBridgeMessage exported for custom WebView hosts.

Migration from 0.1.7

1. Bump guavasure_flutter to ^0.1.8.
2. Run flutter pub get and pod install (iOS).
3. If mobile nav is enabled for your partner, wire onGoBack on GuavaSureEmbed (e.g. Navigator.of(context).maybePop()).

0.1.7

Fixed

• Bumped permission_handler to ^12.0.1 so the plugin resolves alongside host apps that already depend on permission_handler 12.x (e.g. ^12.0.1). Versions 0.1.5–0.1.6 pinned ^11.3.1, which blocked flutter pub get when a partner app required a newer major.

Requirements

• Android: compileSdkVersion 35 or higher (required by permission_handler 12.x). Most Flutter 3.24+ templates already satisfy this.

Migration from 0.1.6

1. Bump guavasure_flutter to ^0.1.7.
2. Run flutter pub get and pod install (iOS).
3. If Android build fails on SDK version, set compileSdk = 35 in android/app/build.gradle (or android { compileSdk = 35 } in android/app/build.gradle.kts).

0.1.6

Added

• GuavaSureEmbedConfig.partnerExternalId — when set, embed URLs include partner-external-id so the hosted embed can lock to a single matching pet (same stable ID used in customer-auth-token pet upserts). If no Guava ID matches, multi-pet behavior is unchanged.

Migration from 0.1.5

1. Bump guavasure_flutter to ^0.1.6.
2. Optionally pass partnerExternalId on GuavaSureEmbedConfig when opening the embed for a specific pet.

0.1.5

Added

• Native Razorpay Checkout via razorpay_flutter when open-payment includes key + orderId / subscriptionId (plus optional amountPaise, currency, name, description, prefill).
• Payment cascade: native SDK → Custom Tab / Safari → external browser.
• launchGuavaSurePayment exported for first-party and custom WebView hosts.
• Unit tests for native payload parsing (canOpenNativeCheckout, bridge fields).
• Native camera capture bridge for nose photos on Flutter WebView hosts: capture-photo, camera-permission, and open-camera-settings.
• Just-in-time camera permission prompts, Settings deep-link on permanent deny, and chunked base64 delivery of captured images back to the embed.
• Unit tests for camera bridge message parsing.

Changed

• Native cancel/failure no longer auto-opens a payment URL (avoids double checkout).
• Embed reload after native success (same as browser-return path).
• OpenPaymentRequest extended with Razorpay native checkout fields.

Requirements

• Hosted embed must send key + orderId/subscriptionId on open-payment (current GuavaSure embed; no app-side change beyond upgrading the plugin).
• Host app must declare camera usage:
  • Android: CAMERA permission in AndroidManifest.xml
  • iOS: NSCameraUsageDescription in Info.plist and PERMISSION_CAMERA=1 in the Podfile preprocessor definitions
• Hosted embed must include the Flutter WebView camera capture path (platform=flutter-webview + GuavasureBridge).
• iOS: run pod install after upgrading.
• Android: Custom Tabs <queries> entry still required for URL fallback only.

Migration from 0.1.4

1. Bump guavasure_flutter to ^0.1.5 in pubspec.yaml.
2. Run flutter pub get and pod install (iOS).
3. Add camera permission strings / manifest entries / Podfile macro (see README).
4. Cold-start the app; verify debug logs show native=true on Pay and nose capture opens the native camera.
5. No API or backend changes required for standard Razorpay checkout.

0.1.4

• Re-authenticate with a fresh partner JWT when reloading the embed after Razorpay return (re-resolves via partnerAuthTokenProvider).
• Ignore spurious app lifecycle resume events within 2s of opening a payment link.
• Open Razorpay links in the external browser on desktop (macOS, Windows, Linux) to avoid spurious reloads from in-app browser sheets.