• Recent
    • Tags
    • Popular
    • Register
    • Login

    Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

    Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website Mango 5 Documentation Website

    iOS 12.2 Problem

    User help
    3
    11
    2.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • CraigWebC
      CraigWeb
      last edited by

      @ralf said in iOS 12.2 Problem:

      with any browser on

      Hi Ralf

      If things are not working there will definitely be errors in your browser's console and/or in your ma.log file that can point us to what is going wrong. Please review this document: https://help.infiniteautomation.com/reporting-bugs

      Without screenshots, logs and errors, no one can really help...

      1 Reply Last reply Reply Quote 0
      • R
        Ralf
        last edited by

        Hi CraigWeb,

        that's right, sorry...

        ma.log:

        WARN 2019-04-29T11:33:49,073 (com.infiniteautomation.mango.rest.v2.ServerRestV2Controller.postClientError:223) - Client error
        [user=admin, cause=<marker inkscape:isstock="true" style="overflow:visible" id="marker4475" refX="0" refY="0" orient="auto" inkscape:stockid="TriangleInM">, location=https://www.8.8.8.8:8443/ui/zt/ezr/ezr/5og, userAgent=Mozilla/5.0 (iPad; CPU OS 12_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1 Mobile/15E148 Safari/604.1, language=de-DE, date=2019-04-29T11:33:45.136+02:00, timezone=Europe/Berlin]
        ReferenceError: Can't find variable: google
        at i (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango.js?v=1dfa5170b7822c28b0be:84:722281)
        at Re (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:56645)
        at ie (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:51452)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:44322)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:44339)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:44339)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:43535)
        at link (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:151795)
        at Re (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:56645)
        at ie (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:51452)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:44322)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:43535)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:151266)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:94738)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:94875)
        at $digest (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:100290)
        at $apply (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:102474)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:124802)
        at completeTask (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:122758)
        at null (https://www.8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=0f03d20f7b30b4a597f9:78:34337)

        Safari:

        [Error] WebSocket network error: The operation couldn’t be completed. (OSStatus error -9807.) (x2)

        [Error] WebSocket network error: The operation couldn’t be completed. (OSStatus error -9807.) (x6)

        [Error] Can't find variable: google

        https://8.8.8.8:8443/modules/mangoUI/web/mangoUi~ngMango.js?v=1dfa5170b7822c28b0be:84
        c (mangoUi~ngMango~ngMangoServices.js:72:165698)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:72:166652)
        Re (mangoUi~ngMango~ngMangoServices.js:78:56668)
        ie (mangoUi~ngMango~ngMangoServices.js:78:51453)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:44323)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:44340)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:44340)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:43536)
        link (mangoUi~ngMango~ngMangoServices.js:78:151796)
        Re (mangoUi~ngMango~ngMangoServices.js:78:56646)
        ie (mangoUi~ngMango~ngMangoServices.js:78:51453)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:44323)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:43536)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:151267)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:94739)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:94876)
        $digest (mangoUi~ngMango~ngMangoServices.js:78:100291)
        (anonyme Funktion) (mangoUi~ngMango.js:77:15733)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:124724)
        completeTask (mangoUi~ngMango~ngMangoServices.js:78:122759)
        (anonyme Funktion) (mangoUi~ngMango~ngMangoServices.js:78:34338)

        1 Reply Last reply Reply Quote 0
        • CraigWebC
          CraigWeb
          last edited by

          Is your server by any chance behind a reverse proxy or firewall? Something is blocking web socket connections which is what the <ma-point-value> and other components use to show the live value.

          1 Reply Last reply Reply Quote 0
          • R
            Ralf
            last edited by

            No, everything necessary open.
            The strange thing is, that with windows or mac or android OS there is all ok, the svg and the ma-point-values are showing the live values.
            With iOS 12.2 only the charts are working...

            1 Reply Last reply Reply Quote 0
            • CraigWebC
              CraigWeb
              last edited by

              Will have to wait and see what Jared says, if you could give any more information it would only help.

              Screen-shots from your iPad?
              Did this stop working after an upgrade?
              Did it ever work?
              Is it only on custom dashboards?
              Do the standard dashboards such as watchlists work properly?

              1 Reply Last reply Reply Quote 0
              • R
                Ralf
                last edited by Ralf

                Hi CraigWeb,

                thank you, my answers:

                • Did this stop working after an upgrade? -> No upgrade.
                • Did it ever work? -> this is the first time I check Mango with an iPad.
                • Do the standard dashboards such as watchlists work properly? -> No, no values and timestamps, only Device Name and Name are visible.

                Here are the screen-shots:

                Mango Dashboard PC:

                0_1556629314443_59f88c55-9c6a-4832-a3a1-9fae764e3422-image.png

                Mango Dashboard iPad Pro iOS 12.2:

                0_1556629464674_0c3563b1-0e06-4013-afd4-6607d2644c60-image.png

                Own Dashboard PC:

                0_1556629686574_4752455a-7d06-48f3-affe-06b6ad96e1ea-image.png

                Own Dashboard iPad:

                0_1556629767521_47d28853-2921-45c4-a299-063af0080189-image.png

                Watchlist PC:

                0_1556630358657_4ac1f9b5-5445-4f94-a47e-202a94e5c968-image.png

                Watchlist iPad:

                0_1556630439389_6d407fe7-bcd8-4fbe-8d06-ce5b4f527c58-image.png

                1 Reply Last reply Reply Quote 0
                • Jared WiltshireJ
                  Jared Wiltshire
                  last edited by

                  Are you connecting to Mango over the internet? Do you have HTTPS enabled? We see this most commonly when there is an ISP transparent proxy which doesn't handle WebSockets correctly.

                  Developer at Radix IoT

                  1 Reply Last reply Reply Quote 0
                  • R
                    Ralf
                    last edited by

                    Hi Jared,

                    yes, I connect to Mango over the internet and https is enabled.
                    I don't understand why this bug only exist with iOS. If the reason is Websocket or ISP, why it works with Android, WIN and Mac?

                    Jared WiltshireJ 1 Reply Last reply Reply Quote 0
                    • CraigWebC
                      CraigWeb
                      last edited by CraigWeb

                      I have not had this problem before on an Ipad, don't really have one to test ATM but you could maybe do some troubleshooting like putting your pad on a WiFi with a different ISP or hotspot from a different mobile provider.
                      BTW this probably won't be your last frustration when it comes to IOS and browsers.

                      1 Reply Last reply Reply Quote 0
                      • Jared WiltshireJ
                        Jared Wiltshire @Ralf
                        last edited by

                        @ralf said in iOS 12.2 Problem:

                        I don't understand why this bug only exist with iOS.

                        iOS / Safari don't exactly have a great track record when it comes to web standards.

                        Unfortunately this does seem to be a bug in Safari, see here - https://stackoverflow.com/questions/37898048/websocket-network-error-osstatus-error-9807-invalid-certificate-chain

                        Since the message there says "Invalid certificate chain" it might be worth checking your certificate using a site like https://www.ssllabs.com/ssltest/

                        PS I would recommend you to try a different browser but I don't think it will make any difference as Apple in its infinite wisdom prohibits using anything than its own Safari browser engine on iOS, so Chrome on on iOS is a basically a skinned version of Safari.

                        Developer at Radix IoT

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post