Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    Maximum call stack size exceeded error on iOS

    SNAPSHOT_v13.1d_2024-08-15/Enterprise Deployment

    iOS on iPhone 8 and iOS simulator on MacOS

    Hello, this wasn't happening with SNAPSHOT_v13.1d_2024-08-13/Enterprise Deployment:

    Code:
    *08:43:30.877:TUP5:WARN:Log:RangeError: Maximum call stack size exceeded.
    Stack from error.stack:
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108293:44
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108319:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108319:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    getRuleScope@https://localhost:8443/Jat/isomorphic/system/modules-debug/ISC_Core.js:108316:46
    .....

    #2
    There has been a change to identify a component's ruleScope from its auto-child creator if it has no parent (yet). Is your failure occurring in code you can share or a sample?

    Comment


      #3
      Hello, the error is triggered by a click on the RibbonButton which should open the application Menu. The RibbonButton isn't in a RibbonGroup, it's the child of a Layout.

      If I add these two logs in ISC_Core.js (lines 108315 and 108319):

      Click image for larger version

Name:	2024-08-16 21.51.26.jpg
Views:	51
Size:	92.5 KB
ID:	273298

      I get this log in loop:

      Code:
      [Warning] *20:57:50.346:TUP9:WARN:Log:"appMenu" (ISC_Core.js, line 33197)
      [Warning] *20:57:50.346:TUP9:WARN:Log:"appMenu_navStack_navStackPagedPanel_pagesContainer" (ISC_Core.js, line 33197)
      [Warning] *20:57:50.346:TUP9:WARN:Log:"appMenu_navStack_navStackPagedPanel" (ISC_Core.js, line 33197)
      [Warning] *20:57:50.347:TUP9:WARN:Log:"appMenu_navStack" (ISC_Core.js, line 33197)
      [Warning] *20:57:50.347:TUP9:WARN:Log:"appMenu_navStackContainer" (ISC_Core.js, line 33197)
      [Warning] *20:57:50.347:TUP9:WARN:Log:"appMenu" (ISC_Core.js, line 33197)
      where appMenu is the Menu which should appear after clicking the RibbonButton.

      Does this helps?

      Comment


        #4
        Originally posted by claudiobosticco View Post
        The RibbonButton isn't in a RibbonGroup, it's the child of a Layout.
        and this seems to be the problem: when I use a MenuButton instead of a RibbonButton, everything works fine.

        Is it not supported to use a standalone RibbonButton? What is the purpose of using a RibbonBar and RibbonGroup if I only have one RibbonButton? My use case is the classic "hamburger" icon that opens the application menu.


        Comment


          #5
          Thanks for that log output. We are able to reproduce the issue locally as well. When we have a fix ready, we'll update this thread.

          As for using a RibbonButton standalone, that is fine. This issue is a regression and not a sign of misuse.

          Comment


            #6
            A fix has been committed for builds starting 2024-08-16. Please check it out and let us know if that fixes your failure.

            Comment


              #7
              Thanks, no new 13.1 build as of now...

              Comment


                #8
                SNAPSHOT_v13.1d_2024-08-18/Enterprise Deployment

                I can confirm it's fixed, thank you very much

                Comment

                Working...
                X