Skip to content

SDKS-5123 ForgeRock Android SDK 4.8.6 Release preparation#522

Merged
spetrov merged 1 commit into
developfrom
SDKS-5123
Jun 16, 2026
Merged

SDKS-5123 ForgeRock Android SDK 4.8.6 Release preparation#522
spetrov merged 1 commit into
developfrom
SDKS-5123

Conversation

@spetrov

@spetrov spetrov commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

JIRA Ticket

SDKS-5123 ForgeRock Android SDK 4.8.6 Release Activities

Description

  • Updated CHANGELOG.md for the 4.8.6 release
  • Updated version numbers to 4.8.6

@spetrov spetrov requested review from rodrigoareis and witrisna June 16, 2026 15:53
@codecov

codecov Bot commented Jun 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 65.85%. Comparing base (63b093b) to head (8f84a5c).

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #522   +/-   ##
==========================================
  Coverage      65.85%   65.85%           
  Complexity      1769     1769           
==========================================
  Files            265      265           
  Lines           8681     8681           
  Branches         972      972           
==========================================
  Hits            5717     5717           
  Misses          2532     2532           
  Partials         432      432           
Flag Coverage Δ
unit-tests 65.85% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@spetrov spetrov merged commit d4fbec6 into develop Jun 16, 2026
10 checks passed
@spetrov spetrov deleted the SDKS-5123 branch June 16, 2026 16:51
spetrov added a commit that referenced this pull request Jun 16, 2026
* SDKS-4658: Set code verifier to null for Apple Sign-In

The `codeVerifier` is explicitly set to `null` in the `AuthorizationRequest.Builder` for the Apple Sign-In handler.

* SDKS-4714: Use empty request body in self-service session endpoint (#510)

* SDKS-4714: Use empty request body in self-service session endpoint

Remove the `EMPTY` constant from OkHttp's `RequestBody` and has been replaced with `"".toRequestBody()`.

* Update Session.kt

Signed-off-by: Andy Witrisna <andy.witrisna@forgerock.com>

---------

Signed-off-by: Andy Witrisna <andy.witrisna@forgerock.com>

* Add migration support for Ping SDK with DefaultStorageClient (#511)

* Increase sleep time in FRUserMockTest to ensure token expiration (#513)

The `Thread.sleep` duration in `FRUserMockTest.kt` is increased from 1000ms to 2000ms to allow sufficient time for tokens to expire before testing the refresh token flow.

* ForgeRock Android SDK 4.8.4 Release preparation (#512)

* Updated  for the ForgeRock 4.8.4 release
* Fixed various e2e test cases.

* SDKS-4947 Updating README with maintenance information (#515)

* Updating README with maintenance information

* Rename contribution file name

* SDKS-5037 - Upgrade bcpkix-jdk18on from 1.81 to 1.84 to address CVE-2026-5588 (#516)

* ForgeRock Android SDK 4.8.5 Release preparation (#517)

* Removed Sonatype OSS Index Scan from the CI (this service has been discontinued)

* Updated version number for the ForgeRock 4.8.5 release

* Fix mend tasks to fail the pipeline if critical or high vulnerabilities are found

* SDKS-5096: Enhance WebAuthn registration by adding optional device name (#519)

* SDKS-5096: Enhance WebAuthn registration by adding optional device name parameter

* SDKS-5120: Add authenticationValidityDuration support to device binding and signing (#520)

* SDKS-5120: Allow configurable authenticationValidityDuration in DeviceBindingCallback and DeviceSigningVerifierCallback

* PR review - guard authentication validity duration.

* [fix] SDKS-5114 Handle AM 400 for Push Number Challenge with distinct exception (#521)

* [fix] SDKS-5114 Handle AM 400 for Push Number Challenge with distinct exception

AM 8.1.0 (OPENAM-24154) returns HTTP 400 when a user selects the wrong number
in a Push Number Challenge. Previously the SDK surfaced a generic
PushMechanismException with no semantic meaning. This fix introduces
PushNumberChallengeException (extends PushMechanismException) so callers can
distinguish a wrong-number rejection from other failures, and leaves the
PushNotification in its pending state so the app can offer a retry.

Phases:
- phase 1: Create PushNumberChallengeException (8804d77c)
- phase 2: Handle 400 for Push Number Challenge in PushResponder (fe17bf07)
- phase 3: Unit tests for 400 number-challenge path (4d57f2ca)
- code review: Remove body logging, fix test builder placement (cc910478)

Refs: SDKS-5114

* Addressing comment from Stoyan

* Updated version number for the ForgeRock 4.8.6 release (#522)

---------

Signed-off-by: Andy Witrisna <andy.witrisna@forgerock.com>
Co-authored-by: Andy Witrisna <witrisna@gmail.com>
Co-authored-by: Andy Witrisna <andy.witrisna@forgerock.com>
Co-authored-by: Vibhor Goswami <vibhor.goswami@gmail.com>
Co-authored-by: Rodrigo Reis <rodrigo.reis@forgerock.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants