Hello,

This is a common situation on Odoo.sh when introducing a new dependency.

When you add a new module (B) as a dependency of an existing module (A), Odoo.sh may not detect it immediately because the app list is not refreshed during deployment.

Recommended approach:

• Ensure Module B is present in the repository and correctly referenced in the manifest of Module A.
• Trigger an app list update before installation (e.g., using -u all or explicitly updating the app list in your deployment script).

• Alternatively, deploy in two steps:

  1. First deploy Module B alone (so it becomes visible)
  2. Then deploy Module A with the dependency

This ensures Odoo recognizes the new module before trying to install dependent modules.

Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com

So the only viable ways are:

1. Deleting A, refresh-app list and reinstall A
2. Introduce B when not an dependency
3. Write migration scripts which inlude refresh method before the dependencies are checked (not tested)
4. Trigger an app list update before installation (e.g., using -u all or explicitly updating the app list in your deployment script).
   How to do this in odoo.sh?? Given that the code is already swapped to the new state (B as dep from A) which is the working Code.
5. ???