Navigation

    Windy Community

    • Register
    • Login
    • Search
    • Unread
    • Categories
    • Groups
    • Go to windy.com

    Errors from Lib.js - Started 1st August 2022

    Developers
    4
    5
    49
    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.
    • C
      CompassDSNM last edited by

      Hi Windy,

      We first noticed we were getting errors from lib.js this morning, errors shown in Chome Dev Console:

      Screenshot 2022-08-01 104605.png Screenshot 2022-08-01 105634.png Screenshot 2022-08-01 105657.png

      Can you please investigate this?

      Let me know if you need any more information. We were not getting these errors last week.

      Euan

      Tomáš Nesrovnal 5 1 Reply Last reply Reply Quote 0
      • Tomáš Nesrovnal 5
        Tomáš Nesrovnal 5 @CompassDSNM | Premium last edited by

        Hi @CompassDSNM ,
        sorry for the issue, we will look into this.

        Can you please specify, how and what parameters are you setting up? It looks like the problem is with product and overlay.

        If you don't want to enclose details here, write us an email to support@windy.com

        Thanks,
        Tomas

        petegreg 1 Reply Last reply Reply Quote 0
        • petegreg
          petegreg @Tomáš Nesrovnal 5 last edited by

          @tomáš-nesrovnal-5

          Hi I'm also getting errors starting from the new libBoot version 36.0.0.

          Uncaught (in promise) TypeError: Cannot set properties of undefined (setting 'maxZoom')
          at windy.js:182:24
          at libBoot.js:1:259144

          windy.js 182

          W.map.options.maxZoom = 18;
          

          Thanks
          Pete

          marekd 1 Reply Last reply Reply Quote 0
          • marekd
            marekd Administrator @petegreg last edited by marekd

            @petegreg Sorry for the trouble. Please, use map object returned into API init callback (example: https://api.windy.com/map-forecast/examples/hello-world). As it stands in the documentation https://api.windy.com/map-forecast/docs

            Do not use features not listed here as we cannot guarantee that they will be available in other versions of Map Forecast API.

            For hotfix use W.map.map instead of W.map, but it does not solve the issue for next possible releases. The only safe solution is to use only a documented methods and objects from callback.

            petegreg 1 Reply Last reply Reply Quote 1
            • petegreg
              petegreg @marekd last edited by

              @marekd Thanks for the help. All good now!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Windyty, S.E. - all rights reserved. Powered by excellent NodeBB
              NodeBB & contributors, OSM & contributors, HERE maps
              Terms and Conditions     Privacy Policy