Daily updates from Odoo
Sunday, May 3, 2026
10 changes
3 changes
Resolved issues and error corrections
This update fixes a previous issue where users wouldn't receive notifications when their phone number country wasn't supported for SMS verification. Now, users will receive an email notification if their country isn't supported, improving the overall user experience for expense report setup. The fix also includes enhanced error handling for future flows.
Original PR description
When a user request the card details, if the country of the phone number of the user isn't supported by IAP, it would silently fail. Now, we are sending an email in case the phone number isn't supported. In case some flow don't/can't have any email fallback, we will add the a generic error and a more detailed one for the country not being supported. task-6065232 Forward-Port-Of: odoo/enterprise#112701
This update corrects a technical issue that could cause problems with voice message tests. By ensuring asynchronous code waits for the voice player to load, we've eliminated a potential race condition and improved test reliability. This ensures voice message functionality works consistently.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/163783 Forward-Port-Of: odoo/odoo#261910 Forward-Port-Of: odoo/odoo#261795
This update resolves a potential issue where voice message tests were failing due to race conditions. The fix ensures that asynchronous operations complete before promises are resolved, improving the reliability of our voice messaging functionality. This prevents errors and ensures consistent test results.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/242411 Community: https://github.com/odoo/odoo/pull/261910 Forward-Port-Of: odoo/enterprise#115587
2 changes
Resolved issues and error corrections
This update addresses a technical issue that could cause problems with voice message testing. The change ensures that asynchronous operations related to voice playback complete before promises are resolved, preventing race conditions. This improves the stability and reliability of voice message functionality.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/163783 Forward-Port-Of: odoo/odoo#261910 Forward-Port-Of: odoo/odoo#261795
This update resolves a potential issue where voice message tests were failing due to race conditions. The fix ensures that asynchronous code waits for the voice player to fully load before resolving promises, improving the reliability of testing and preventing errors.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/242411 Community: https://github.com/odoo/odoo/pull/261910 Forward-Port-Of: odoo/enterprise#115587
2 changes
Resolved issues and error corrections
This update addresses a technical issue that could cause problems with voice message tests. The fix ensures that asynchronous operations complete before promises are resolved, preventing race conditions and improving test reliability. This enhances the stability of our voice messaging functionality.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/163783 Forward-Port-Of: odoo/odoo#261910 Forward-Port-Of: odoo/odoo#261795
This update resolves a technical issue that could cause instability in voice message testing within the Odoo Enterprise system. By ensuring asynchronous code waits for the voice player to load, the fix prevents race conditions and improves the reliability of these tests. This contributes to a more stable and dependable user experience.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/242411 Community: https://github.com/odoo/odoo/pull/261910 Forward-Port-Of: odoo/enterprise#115587
2 changes
Resolved issues and error corrections
This update fixes a previous issue where users wouldn't receive notifications when their phone number country wasn't supported for SMS verification within the expense reporting feature. Now, users will receive an email notification if their country isn't supported, ensuring a smoother and more reliable experience. The system also includes enhanced error messaging for better troubleshooting.
Original PR description
When a user request the card details, if the country of the phone number of the user isn't supported by IAP, it would silently fail. Now, we are sending an email in case the phone number isn't supported. In case some flow don't/can't have any email fallback, we will add the a generic error and a more detailed one for the country not being supported. task-6065232 Forward-Port-Of: odoo/enterprise#115908 Forward-Port-Of: odoo/enterprise#112701
This update corrects a previous issue where expense cards were rejecting payments from certain merchant categories (airlines, car rentals, and hotels). The team added the necessary Merchant Category Codes (MCCs) to the system, ensuring broader acceptance of expenses. This improves the usability of the expense card for users making payments from these common types of merchants.
Original PR description
In the expense card, when a payment is made. The card can be filtered to only allow certains category of merchant. However, the 3 ranges of MCC we not added: - Airlines, air carriers: MCC's from 3000 to 3350 - Car Rental Agencies: MCC's from 3351 to 3500 - Lodging, hotels, motels and resorts: MCC's from 3501 to 3999 And since the MCC are not present in the list, they are rejected by default even the card is set to accept all MCCs. task-5486945 Forward-Port-Of: odoo/enterprise#115379 Forward-Port-Of: odoo/enterprise#114154
1 change
Resolved issues and error corrections
This update resolves a potential issue where voice message tests were failing due to race conditions. The fix ensures that asynchronous code waits for the voice player to fully load before resolving promises, leading to more reliable test results. This improves the overall stability of the voice messaging feature.
Original PR description
Before this commit, voice message tests don't wait until the voice player is drawn before resolving the corresponding promise. This may lead to race conditions. This commit fixes the issue by properly `await`ing the completion of the asynchronous code before resolving the promise. Related runbot error: https://runbot.odoo.com/odoo/error/242411 Community: https://github.com/odoo/odoo/pull/261910 Forward-Port-Of: odoo/enterprise#115587