🔖 release: mobile@1.1.17

[cruzdanilo]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@exactly/mobile@1.1.17

Patch Changes

• #795 1efacfa Thanks @cruzdanilo! - 🥅 handle biometric check before passkey fallback

• #795 861d30b Thanks @cruzdanilo! - 🥅 fingerprint network errors

• #795 375ea92 Thanks @cruzdanilo! - 🥅 suppress expected network errors

---

Summary by CodeRabbit

• Chores
  • Version bumped to 1.1.17
  • Changelog updated with three patch release entries

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

This PR removes three changeset entries and consolidates them into the CHANGELOG.md as version 1.1.17 for the @exactly/mobile package. It also bumps the package version from 1.1.16 to 1.1.17, completing a standard release workflow.

Changes

Cohort / File(s)	Summary
Removed Changeset Entries .changeset/bright-dogs-handle.md, .changeset/bright-foxes-glow.md, .changeset/loose-geckos-change.md	Deleted three changeset files documenting patch updates for biometric check, fingerprint network errors, and suppression of expected network errors.
Release Metadata CHANGELOG.md, package.json	Added changelog entry for version 1.1.17 with three patch notes (PR #795) and bumped package version from 1.1.16 to 1.1.17.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• 🔖 release: mobile@1.1.16, server@0.2.67 #788: Consecutive version bump release for @exactly/mobile removing changeset entries and updating release metadata.
• 🔖 release: mobile@1.1.6, server@0.2.55 #707: Similar release workflow modifying .changeset entries and updating CHANGELOG/package.json for @exactly/mobile.
• 🔖 release: mobile@1.1.12, server@0.2.62 #762: Related release update removing changeset entries and consolidating them into CHANGELOG with version bump.

Suggested reviewers

• dieguezguille
• franm91

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the package release being published, matching the primary objective of the PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch changeset-release/main

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Summary of Changes

Hello @cruzdanilo, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the release of the @exactly/mobile package to version 1.1.17. It integrates recent bug fixes and enhancements, specifically improving authentication flows by prioritizing biometric checks and refining network error handling through fingerprinting and suppression of anticipated errors.

Highlights

• Mobile Package Release: The @exactly/mobile package has been released as version 1.1.17.
• Biometric Check Handling: Implemented logic to handle biometric checks before falling back to passkey authentication.
• Network Error Fingerprinting: Added functionality to fingerprint network errors for better identification and debugging.
• Suppressing Expected Network Errors: Introduced mechanisms to suppress network errors that are expected and can be safely ignored.
• Changeset Files Removed: The temporary changeset files used for this release have been removed.

Changelog

• .changeset/bright-dogs-handle.md
  • Removed the changeset file for biometric check handling.
• .changeset/bright-foxes-glow.md
  • Removed the changeset file for network error fingerprinting.
• .changeset/loose-geckos-change.md
  • Removed the changeset file for suppressing expected network errors.
• CHANGELOG.md
  • Added new entries for version 1.1.17, detailing updates to biometric authentication and network error management.
• package.json
  • Updated the package version from 1.1.16 to 1.1.17.

Activity

• The pull request was automatically opened by the Changesets release GitHub action to facilitate the release process.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[gemini-code-assist]

Code Review

This pull request is an automated release for version 1.1.17 of the @exactly/mobile package. The changes correctly update package.json and CHANGELOG.md. I've added one comment on the changelog with a suggestion for a minor improvement in the implementation of one of the features included in this release, to be addressed in a follow-up. Otherwise, this PR is good to merge.

[gemini-code-assist]

Regarding the implementation for handle biometric check before passkey fallback, I noticed a potential improvement for type safety in src/utils/useAuth.ts at line 54. The check for error.code on an Error object is not fully type-safe, as code is not a standard property of Error.

To improve robustness and align with TypeScript best practices, I recommend using a type guard to check for the existence and type of the code property before accessing it. For example:

const hasCode = (error: unknown): error is { code: string } => {
  return typeof error === 'object' && error !== null && 'code' in error;
};

// in handleError
if (error instanceof Error && hasCode(error) && error.code === 'ERR_BIOMETRIC') {
  // ...
}

This is a minor point and can be addressed in a follow-up PR, as the file is not part of this diff. It would make the error handling logic more resilient.

References

1. Prefer refactoring for explicit type safety, even if it adds slight verbosity, as it prevents potential runtime errors and maintains type-checking integrity. This suggestion improves type safety when checking for custom error codes.

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.76%. Comparing base (1efacfa) to head (f56d2fa).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #796      +/-   ##
==========================================
+ Coverage   69.21%   69.76%   +0.55%     
==========================================
  Files         208      208              
  Lines        7090     7471     +381     
  Branches     2255     2394     +139     
==========================================
+ Hits         4907     5212     +305     
- Misses       1999     2043      +44     
- Partials      184      216      +32     

Flag	Coverage Δ
e2e	69.73% <ø> (+0.56%)	⬆️

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

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

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.