Dev assertion failure message

Options
RobWilk
RobWilk Superuser ✭✭✭✭✭
edited November 2023 in Report a Bug

Been getting this screen from time to time (not sure if it is always the same message):

At minimum, someone should know about it. I'm not sure what I did to cause it. I imagine the error message identifies where in the code it's happening.


Rob Wilkens

Tagged:

Comments

  • MrGood
    MrGood Member ✭✭✭✭
    Options

    I’ve been getting that too. Not sure if it’s been cleared since 3.89 but I suspect not since it wasn’t mentioned in the release log. I’ve gotten it with Safari on MacOS Sonoma.

  • Coach Natalie
    Coach Natalie Administrator, Moderator admin
    Options

    Hey @RobWilk & @MrGood — thanks for reporting this!

    It looks like our product team is aware of this issue and they're working to resolve it. These types of messages should never be shown to our users in production. The issue should be fixed with the next web release (3.90.0), but please let me know if you continue to see it after that time. 🙂

    -Coach Natalie

  • Jeff C
    Options

    I am getting two error popups when I sign in to my account. Screenshots below.

    The browser developers console shows the following:

    main.8b3199e1c9fcbb205087.js:2 Assert: maximum message length 33554432 exceeded
    at https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2255410
    at d.value (https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2116584)
    at console.debug (https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2116034)
    at Object.debug (https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:684395)
    at https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2094138
    at https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:702684
    at https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:702637
    at Object.dispatch (https://app.simplifimoney.com/npm.redux-saga.2203e8c5e3aa821c7ed6.js:1:15957)
    at Object.f [as rehydrate] (https://app.simplifimoney.com/8714.fe95c34a6debe3f6535b.js:2:306374)
    at D (https://app.simplifimoney.com/8714.fe95c34a6debe3f6535b.js:2:304051)

    OriginalError
    :
    Assert: maximum message length 33554432 exceeded at https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2255410 at d.value (https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2116584) at console.debug (https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2116034) at Object.debug (https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:684395) at https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js:2:2094138 at https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:702684 at https://app.simplifimoney.com/npm.app-components.a7c4c90def1ca386436d.js:1:702637 at Object.dispatch (https://app.simplifimoney.com/npm.redux-saga.2203e8c5e3aa821c7ed6.js:1:15957) at Object.f [as rehydrate] (https://app.simplifimoney.com/8714.fe95c34a6debe3f6535b.js:2:306374) at D (https://app.simplifimoney.com/8714.fe95c34a6debe3f6535b.js:2:304051)
    name
    :
    "Assert"
    message
    :
    "maximum message length 33554432 exceeded"

    explicit props:{href: 'https://app.simplifimoney.com/', path: '/', exception_type: 'browserjs', exception_class: 'Assert', exception_name: 'maximum message length 33554432 exceeded', …}
    exception_class
    :
    "Assert"
    exception_name
    :
    "maximum message length 33554432 exceeded"
    exception_reason
    :
    "{"file":"https://app.simplifimoney.com/main.8b3199e1c9fcbb205087.js","lineNumber":2,"columnNumber":2255410}"
    exception_type
    :
    "browserjs"
    href
    :
    "https://app.simplifimoney.com/"
    path
    :
    "/"

    Pressing OK dismisses the dialogs and I haven't noticed anything wrong while using the app afterwards, but it's annoying that I have to do that when signing in.

  • Coach Natalie
    Coach Natalie Administrator, Moderator admin
    Options

    @Jeff C, thanks for letting us know!

    As you can see from the above discussion, this issue is expected to be fixed with the next web release of 3.90.0. 😀

    -Coach Natalie

This discussion has been closed.