Added #

• Introduces the WebviewErrorUseCase class to centralize the logic for determining which WebResourceError cases can be safely ignored during the PortOne payment flow in a WebView.
  • The WebviewErrorUseCase.shouldIgnore method consults a predefined set of rules to determine if an error can be safely ignored based on its type and description. This helps to prevent unnecessary error handling for benign WebView errors that do not affect the payment process, such as cancelled navigations, host lookup failures, and network timeouts.
  • The onReceivedError callback in PortonePaymentState is updated to use the WebviewErrorUseCase.shouldIgnore method to filter out ignorable errors, improving the robustness and clarity of the error handling logic.

Fixed #

• Prevents unnecessary error handling for WebResourceError types with UNKNOWN errors and a description containing 'WebKitErrorDomain'. These errors are often non-critical and can be safely ignored.

Changed #

• Replaced the default Container() in the IndexedStack with a Center widget containing a CircularProgressIndicator. This ensures that a loading indicator is displayed to the user while the WebView is being initialized, providing visual feedback and preventing a perceived delay.

• Introduced a new _handleSuccess method to encapsulate the logic for handling successful payment responses. This method calls the widget.callback with the paymentResponse and clears the _redirectedUrls list.

• Replaced direct calls to widget.callback with calls to _handleSuccess in the app link and URL override handling logic.

Added #

• Added a null check for errorResponse.statusCode to prevent errors when the status code is not available. If the status code is null, the error is logged and ignored.
• Added a check to ignore HTTP errors that occur on subresource requests (i.e., requests that are not for the main frame document). This prevents unnecessary error handling for resources like images or stylesheets that may fail to load. The URL and status code of the ignored error are logged.

Fixed #

• Improved logging messages to provide more context about the type of HTTP error being handled or ignored.
• Ensured that _redirectedUrls is cleared in _handleError to prevent memory leaks and ensure a clean state for subsequent payment attempts.
• Added a check to ignore errors that occur on subresource requests (i.e., requests that are not for the main frame document). This prevents unnecessary error handling for resources like images or stylesheets that may fail to load.
• Added checks to ignore specific WebResourceError types:
  • UNKNOWN errors with a description containing 'WebKitErrorDomain' are ignored, as these are often non-critical.
  • CANCELLED errors with a description containing 'NSURLErrorDomain' are ignored, as these represent cancelled navigations.

Added #

• Introduces the PortoneErrorHandler class to provide a flexible way to handle error callbacks.
• Added _redirectedUrls to track redirected URLs during WebView navigation. This list is used to generate a stack trace if an error occurs, providing a history of navigation events leading to the error.

Changed #

• Modified the onError parameter in the PortonePayment constructor to accept a PortoneErrorHandler instance.
• Ensured that errors originating from the PortOne SDK, WebView errors, and navigation errors include stack traces when invoking the error callback.
• Introduced the _handleError method to centralize error reporting, ensuring that both the error object and a stack trace (either the current stack trace or one generated from _redirectedUrls) are consistently passed to the widget.onError callback.
• Added null safety check for url in shouldOverrideUrlLoading to prevent errors when the URL is null.

Added #

• Added onReceivedError callback to capture and propagate WebResourceError objects via the widget.onError handler.
• Added onReceivedHttpError callback to capture and propagate WebResourceResponse objects via the widget.onError handler.

Changed #

• Modified payment data processing to directly include the appScheme in the payment data map.
• Removed the conditional logic for setting retAppScheme specifically for Toss Payments, as it's no longer required.
• Updated paymentData to be a mutable map to allow modification.

• Added portone_flutter_v2.podspec for CocoaPods integration.
• Created PrivacyInfo.xcprivacy to declare the app's privacy practices.
• Added ios/Runner.xcodeproj/project.pbxproj to unmanaged files in .metadata to prevent template overwrites.

Added #

• Updated the supported payment methods section in the README to reflect the new PG Company specific support.
• Enable the Android plugin so that the app has the schema without modifying the manifest separately, and declare the external app schema (including <queries> for package visibility) in the plugin manifest.

Added #

• Added pg field to the PaymentRequest model, accepting a PGCompany enum to specify the payment gateway.
• Updated the PaymentRequest.fromJson factory method to handle the new pg field.
• Added PGCompany enum to represent supported PG companies.
• Added conditional logic to include the retAppScheme parameter when using the Tosspayments PG for redirect handling.

Changed #

• Introduced validation in the PaymentRequest constructor to ensure the selected payMethod is supported by the specified PGCompany.
• Throws an ArgumentError when an unsupported payMethod is provided, with a clear error message listing the supported methods.
• Added unit tests verifying that an ArgumentError is thrown for unsupported payMethod cases and that object creation succeeds for supported cases.
• Removed includeToJson: false annotation from the pg field in the PaymentRequest model. (If still present, please remove.)

Added #

• Added unit tests for most of model classes

Changed #

• Exposes the PortonePaymentState class as public and adds comprehensive documentation to facilitate testing and improve understanding of the payment process.
• Sets a default redirectUrl in the paymentData if it is null.
• Adds retAppScheme to the paymentData for compatibility with Tosspayments' TossPay, as it requires this parameter.

Added #

• Added PaymentCurrency enum with support for a wide range of currencies based on ISO 4217.
• Added Missing documentation for all public members to improve code readability and maintainability.

Changed #

• Translated the CHANGELOG from Korean to English.
• Converted enum values in CashReceiptTradeOption to snake case for consistency.

Added #

• Initial integration of PortOne V2 payment service
• Implementation of payment process using the PortonePayment widget
• Support for multiple payment methods (credit card, virtual account, easy-pay, etc.)
• Implementation of payment request model (PaymentRequest) and payment response model (PaymentResponse)
• Added PGCompany enumeration to support various PG companies
• Added PaymentSupportedMethods extension for checking supported payment methods per PG company
• Functionality for handling payment callbacks via app schemes
• Option to configure payment window type (iframe, popup)
• Multilingual support (Korean, English)
• Localization support for PG company names
• Support for multiple currencies (according to the ISO 4217 standard)
• Support for country information (according to the ISO 3166-1 alpha-2 standard)
• Added bypass parameter support for each PG company:
  • e.g., KakaoPay, Toss Payments, Toss Pay V2, KSNET, Smartro V2, Naver Pay, etc.
• Support for transmitting additional information such as custom data, store information, and shipping address
• Error handling and logging functionality

Changed #

• Renamed class from PortOnePayment to PortonePayment for consistency

Fixed #

• Improved handling of intent URL processing
• Improved payment response processing via app scheme
• Modified field type in PaymentRequest model (changed isEscrow to nullable)
• Changed paypal to convenienceStore in the PaymentPayMethod enumeration