v62.0.0 (2020-07-13)

Full Changelog

FxA Client

⚠️ Breaking changes ⚠️

• Adds support for entrypoint in oauth flow APIs: consumers of beginOAuthFlow and beginPairingFlow (beginAuthentication and beginPairingAuthentication in ios) are now required to pass an entrypoint argument that would be used for metrics. This puts the beginOAuthFlow and beginPairingFlow APIs inline with other existing APIs, like getManageAccountUrl. (#3265)
• Changes the authorizeOAuthCode API to now accept an AuthorizationParams object instead of the individual parameters. The AuthorizationParams also includes optional AuthorizationPKCEParams that contain the codeChallenge, codeChallengeMethod. AuthorizationParams also includes an optional keysJwk for requesting keys (#3264)

What's new

• Consumers can now optionally include parameters for metrics in beginOAuthFlow and beginPairingFlow (beginAuthentication and beginPairingAuthentication in ios). Those parameters can be passed in using a MetricsParams struct/class. MetricsParams is defined in both the Kotlin and Swift bindings. The parameters are the following (#3328):
  • flow_id
  • flow_begin_time
  • device_id
  • utm_source
  • utm_content
  • utm_medium
  • utm_term
  • utm_campaign
  • entrypoint_experiment
  • entrypoint_variation

Logins

What's fixed

• Fixed a bug where attempting to edit a login with an empty form_submit_url would incorrectly
  reject the entry as invalid (#3331).

Tabs

What's new

• Tab records now have an explicit TTL set when storing on the server, to match the behaviour
  of Firefox Desktop clients (#3322).