Overslaan naar inhoud
Je moet geregistreerd zijn om te kunnen communiceren met de community.
Alle posts Personen Badges
Labels (Bekijk alle)
odoo accounting v14 pos v15
Over dit forum
Deze vraag is gerapporteerd
3 Antwoorden
7495 Weergaven
Avatar
Austin

Hello - 

Today we updated our Odoo Community Edition (using method APT-GET) from 16.0.20221029 to 16.0.20230222. After the update, we receive the following error upon logging in. Uninstalling our custom modules did not resolve the issue. Could anyone who performed a similar update provide some insight into this issue?

UncaughtPromiseError > TypeError
Uncaught Promise > this.env.services.bus_service.start is not a function
TypeError: this.env.services.bus_service.start is not a function
    at model.start (https://example.com/web/assets/481-bd97ad6/web.assets_backend.min.js:11804:852)
    at model.start (https://example.com/web/assets/481-bd97ad6/web.assets_backend.min.js:11773:55)
    at async ModelManager.start (https://example.com/web/assets/481-bd97ad6/web.assets_backend.min.js:10313:151)


Additionally, after clicking OK on the error page, we receive a different error when switching between modules on the site:

 UncaughtPromiseError > OwlError
Uncaught Promise > An error occured in the owl lifecycle (see this Error's "cause" property)
OwlError: An error occured in the owl lifecycle (see this Error's "cause" property)
at handleError (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:1105:101)
at owl.App.handleError (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:1932:29)
at ComponentNode.initiateRender (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:1413:19)

Caused by: Error: a rpc promise should always have a reject function
at Class._rpc (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:5784:62)
at Class._rpc (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:7767:13)
at prototype. [as _rpc] (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:5588:488)
at Class._rpc (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:8082:183)
at prototype. [as _rpc] (https://example.com/web/assets/368-db0267e/web.assets_common.min.js:5588:488)
at Class._performOnChange (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:8042:159)
at Class._makeDefaultRecord (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:8037:258)
at async Class.load (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:7762:244)
at async Record.load (https://example.com/web/assets/483-344403c/web.assets_backend.min.js:2300:77)

Avatar
Annuleer
Niyas Raphy (Walnut Software Solutions)

Did you try upgrading the base/web module ?

Austin
Auteur

Hi Niyas -
How do I upgrade the base/web module?

Austin
Auteur

Okay, I see where both the web and base modules are. I will try the upgrade. Thank you.

Austin
Auteur

I upgraded web and base modules, then attempted the Odoo update again. We're still getting the same error (the first one above) when initially signing in. We get the second error when selecting Settings from the top-left menu.

Austin
Auteur

Hi Niyas,

I upgraded the base and web modules, and did the Odoo update again, but we are receiving the same errors. Do you have any more suggestions?

Thank you.



On Wed, Feb 22, 2023 at 12:18 PM Niyas Raphy <notifications@mail.odoo.com> wrote:
Did you try upgrading the base/web module ? ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

Did you try upgrading the base/web module ?

--
Niyas Raphy

Odoo S.A.

+32 81 81 37 00 | info@odoo.com | https://www.odoo.com

Powered by Odoo

Avatar
Isaias Valle
Beste antwoord

Add the ?debug=1 to the URL /web?debug=1​ and click regenerate assets bundle, this worked for me, hope it works for you or anyone else


Avatar
Annuleer
Avatar
Gregorutti SA
Beste antwoord

Hi,

I have an onPremise and do update to 16.0+e-20230330. I got same issue after update and login.

UncaughtPromiseError > TypeError

Promesse non interceptée > this.env.services.bus_service.start is not a function

TypeError: this.env.services.bus_service.start is not a function
    at model.start (https://odoo.mydomain.ch/web/assets/108593-0bb4bca/web.assets_backend.min.js:11841:852)
    at model.start (https://odoo.mydomain.ch/web/assets/108593-0bb4bca/web.assets_backend.min.js:11810:55)
    at async ModelManager.start (https://odoo.mydomain.ch/web/assets/108593-0bb4bca/web.assets_backend.min.js:10345:151)

Workaround with assets works, but my database is on production. I cannt ask my users to change url.

Is there another things to do??

Avatar
Annuleer
Avatar
Mantas
Beste antwoord

I also got this issue after updating odoo 16 with apt from 16.0.20221221 to 16.0.20230220 - get the same error in browser:
Uncaught Promise > this.env.services.bus_service.start is not a function
TypeError: this.env.services.bus_service.start is not a function
    at model.start (https://example.com/web/assets/481-bd97ad6/web.assets_backend.min.js ...

I've found only one workaround - in Setting turn on Debug with assets mode or simply go to your odoo server with ?debug=assets added:

odoo.server.url/web?debug=assets

Avatar
Annuleer