Odoo Changelog — 2026-06-28

Sunday, June 28, 2026

2 changes · saas-19.3

Bug Fixes(2)

Resolved issues and error corrections

[FIX] auth_passkey: add support for Android

Coresaas-19.3auth_passkeyMedium

This update enables Odoo to work with Android devices for passkey-based sign-in and registration. It adds the required web link between Odoo and the Android app, so users can authenticate more smoothly from mobile.

Original PR description

This commit adds a route for Digital Asset Links (`assetlinks.json`)
that link the domain with the Android Mobile App.

Also we adapt some functions authentication/registration so Odoo accept
request origin from the mobile App.
The origin should be `android:apk-key-hash:BASE64(SHA256(APP_SIGNATURE))`

Note: the `/.well-known/assetlinks.json` file should be serve on port
HTTPS (443) without that the Android Digital Asset Links will fail.

Url for debugging Digital Asset Links
https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https://MY-DOMAIN.local&relation=delegate_permission/common.get_login_creds&target.android_app.package_name=com.odoo.mobile&target.android_app.certificate.sha256_fingerprint=D6:73:20:02:CA:2D:01:C9:FD:FC:94:73:5A:D0:73:CF:2C:36:10:29:1F:4B:F7:5D:91:C2:1D:37:B2:18:E8:91

https://developers.google.com/digital-asset-links
https://developer.android.com/identity/passkeys/create-passkeys
https://developer.android.com/identity/credential-manager/prerequisites

opw-6279212

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#270551

#android#passkeys#mobile#authentication

[FIX] l10n_it_stock_ddt: link only DDT covered by invoiced quantity

PR #272668

Coresaas-19.3l10n_it_stock_ddtaccountMedium

The invoicing process now links only the delivery documents that match the quantity actually invoiced. This prevents extra delivery references from appearing on invoices and keeps the generated export files consistent and accurate.

Original PR description

### Issue: When invoicing partial quantities from a sale order, more DDTs than necessary are linked to the invoice Since `l10n_it_ddt_ids` is computed and not stored, the incorrect links persist…

### Issue:
When invoicing partial quantities from a sale order, more DDTs than necessary are linked to the invoice

Since `l10n_it_ddt_ids` is computed and not stored, the incorrect links persist until the remaining quantities are invoiced, at which point the extra DDTs are moved to the new invoice

This creates inconsistencies in the generated XML, which references DDTs not actually covered by the invoice

### Cause:
The quantity allocation loop only checked whether there was remaining `move_qty` to consume, but never checked whether the invoiced quantity (`inv[0]`) had already been fully consumed

As a result, once all invoiced quantity was allocated, the loop kept iterating and linking additional DDTs from the sale order

### Steps to reproduce:
- Install `l10n_it_stock_ddt` with demo data
- Switch to the IT company
- Create a Warehouse
- Create a Product (Invoicing Policy: Delivered Quantities)
- Create and confirm a Sale Order (qty: 5) for that product
- Validate 3 partial deliveries of qty 1, creating a backorder each time
- Create the invoice, set the quantity to 2 and confirm

Before the fix, 3 DDTs were linked instead of 2

opw-6294035

Forward-Port-Of: odoo/odoo#272582
Forward-Port-Of: odoo/odoo#270235

This commit adds a route for Digital Asset Links (`assetlinks.json`) that link the domain with the Android Mobile App. Also we adapt some functions authentication/registration so Odoo accept request origin from the mobile App. The origin should be `android:apk-key-hash:BASE64(SHA256(APP_SIGNATURE))` Note: the `/.well-known/assetlinks.json` file should be serve on port HTTPS (443) without that the Android Digital Asset Links will fail. Url for debugging Digital Asset Links https://digitalassetlinks.googleapis.com/v1/assetlinks:check?source.web.site=https://MY-DOMAIN.local&relation=delegate_permission/common.get_login_creds&target.android_app.package_name=com.odoo.mobile&target.android_app.certificate.sha256_fingerprint=D6:73:20:02:CA:2D:01:C9:FD:FC:94:73:5A:D0:73:CF:2C:36:10:29:1F:4B:F7:5D:91:C2:1D:37:B2:18:E8:91 https://developers.google.com/digital-asset-links https://developer.android.com/identity/passkeys/create-passkeys https://developer.android.com/identity/credential-manager/prerequisites opw-6279212 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#270551

### Issue: When invoicing partial quantities from a sale order, more DDTs than necessary are linked to the invoice Since `l10n_it_ddt_ids` is computed and not stored, the incorrect links persist until the remaining quantities are invoiced, at which point the extra DDTs are moved to the new invoice This creates inconsistencies in the generated XML, which references DDTs not actually covered by the invoice ### Cause: The quantity allocation loop only checked whether there was remaining `move_qty` to consume, but never checked whether the invoiced quantity (`inv[0]`) had already been fully consumed As a result, once all invoiced quantity was allocated, the loop kept iterating and linking additional DDTs from the sale order ### Steps to reproduce: - Install `l10n_it_stock_ddt` with demo data - Switch to the IT company - Create a Warehouse - Create a Product (Invoicing Policy: Delivered Quantities) - Create and confirm a Sale Order (qty: 5) for that product - Validate 3 partial deliveries of qty 1, creating a backorder each time - Create the invoice, set the quantity to 2 and confirm Before the fix, 3 DDTs were linked instead of 2 opw-6294035 Forward-Port-Of: odoo/odoo#272582 Forward-Port-Of: odoo/odoo#270235