Windy Community
    • Unread
    • Categories
    • Groups
    • Go to windy.com
    • Register
    • Login

    Solved Tapping on favourites not functioning as expected since last update.

    Fixed BUGs
    4
    13
    2.1k
    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.
    • CrofterC
      Crofter | Premium
      last edited by Crofter

      Tapping on the home icon then tapping on the home location forecast in the upper left corner does not take you to that forecast but rather to the location on the map where you tapped. Same when accessing favorites from the profile slide-over. I have logged out, logged in and rebooted iPad. No change. Happening on iPad mini, iPad 5th gen and iPhone SE.
      same on in-app browser version. (Edit: working now on iPhone SE)
      error log:
      "runningMs": 760,
      "type": "user",
      "module": "geolocation",
      "msg": "Unable to load||parse /node/geoip: undefined is not an object (evaluating 't.ll[0]')",
      "line": 52,
      "col": 1101,
      "url": "http://localhost:8080/#/?2019-02-09-21,49.230,-124.277,9",
      "script": "mobile.js",
      "ver": "18.2.1",
      "target": "mobile",
      "stack": "http://localhost:8080/v/18.2.1.mob.2bdc/mobile.js:52:1101
      promiseReactionJob@[native code]",
      "scriptLine": "mobilejs-52",
      "latestBcast": "bcast: paramsChanged (159ms. ago)
      store: visibleProducts (149ms. ago)
      store: lastModified (139ms. ago)
      render: toggleSeaMask (2ms. ago)
      render: rendered tileLayer (2ms. ago)
      ",
      "sessionName": "ca-127",
      "sessionCounter": 127,
      "lang": "en",
      "retina": true,
      "size": "768x1024",
      "glParticles": false,
      "platform": "ios",
      "errorID": "unable-to-loadparse-nodegeoip-undefined-is-not-an-objec"
      }
      Error no: 2
      {
      "runningMs": 409000,
      "type": "error",
      "msg": "TypeError: undefined is not an object (evaluating 't.image'): undefined is not an object (evaluating 't.image')",
      "line": 2,
      "col": 463,
      "url": "http://localhost:8080/#/44.778/-134.341?2019-02-09-21,45.921,-123.047,5,m:e1jacJ3",
      "script": "nearest.js",
      "ver": "18.2.1",
      "target": "mobile",
      "stack": "getThumb@http://localhost:8080/v/18.2.1.mob.2bdc/plugins/nearest.js:2:463
      http://localhost:8080/v/18.2.1.mob.2bdc/plugins/nearest.js:2:1066",
      "scriptLine": "nearestjs-2",
      "latestBcast": "bcast: rqstClose wind (1896ms. ago)
      bcast: detailRendered (1896ms. ago)
      bcast: log detail2/model/ecmwf (1884ms. ago)
      bcast: log detail2/display/table (1884ms. ago)
      bcast: log detail2/source/favs-page (1453ms. ago)
      ",
      "sessionName": "ca-127",
      "sessionCounter": 127,
      "lang": "en",
      "retina": true,
      "size": "768x1024",
      "glParticles": false,
      "platform": "ios",
      "errorID": "typeerror-undefined-is-not-an-object-evaluating-timage"
      }
      Error no: 3
      {
      "runningMs": 411001,
      "type": "error",
      "msg": "TypeError: undefined is not an object (evaluating 't.image'): undefined is not an object (evaluating 't.image')",
      "line": 2,
      "col": 463,
      "url": "http://localhost:8080/#/44.778/-134.341?2019-02-09-21,45.921,-123.047,5,m:e1jacJ3",
      "script": "nearest.js",
      "ver": "18.2.1",
      "target": "mobile",
      "stack": "getThumb@http://localhost:8080/v/18.2.1.mob.2bdc/plugins/nearest.js:2:463
      http://localhost:8080/v/18.2.1.mob.2bdc/plugins/nearest.js:2:1066",
      "scriptLine": "nearestjs-2",
      "latestBcast": "bcast: rqstClose wind (3897ms. ago)
      bcast: detailRendered (3897ms. ago)
      bcast: log detail2/model/ecmwf (3885ms. ago)
      bcast: log detail2/display/table (3885ms. ago)
      bcast: log detail2/source/favs-page (3454ms. ago)
      ",
      "sessionName": "ca-127",
      "sessionCounter": 127,
      "lang": "en",
      "retina": true,
      "size": "768x1024",
      "glParticles": false,
      "platform": "ios",
      "errorID": "typeerror-undefined-is-not-an-object-evaluating-timage"
      }

      idefix37I 1 Reply Last reply Reply Quote 0
      • idefix37I
        idefix37 Sailor Moderator @Crofter
        last edited by idefix37

        @Crofter
        Yes, you are right.
        On iPad it’s now impossible to select a location via the Search box.
        Typing a place name in this box gives one or several proposed locations. But then it’s impossible to select one of them.

        734733DE-D0AE-4B96-AA4D-B126F27E4BAE.jpeg

        This issue is encountered in both versions:
        index.html - Version 18.20
        mobile.html - Version 17.20

        ivoI 1 Reply Last reply Reply Quote 0
        • ivoI
          ivo Administrator
          last edited by

          It seems that you are reporting two different bugs. Can you describe step by step how it worked before and how it is broken now?

          idefix37I 1 Reply Last reply Reply Quote 0
          • idefix37I
            idefix37 Sailor Moderator @ivo
            last edited by

            @ivo
            I have just added some additional details in my previous post

            1 Reply Last reply Reply Quote 0
            • ivoI
              ivo Administrator @idefix37
              last edited by

              @idefix37 It is imposibble to click on it? On iPad?

              idefix37I 2 Replies Last reply Reply Quote 0
              • idefix37I
                idefix37 Sailor Moderator @ivo
                last edited by idefix37

                @ivo
                Yes on iPad if I click on a name place the list disappears and no location is shown.
                EDIT: I have just checked again. Now it works on the mobile app on IPad again, but not on the web version index.html - version 18.20

                1 Reply Last reply Reply Quote 0
                • idefix37I
                  idefix37 Sailor Moderator @ivo
                  last edited by idefix37

                  @ivo
                  By the way, there is a small bug on iPad too, when searching a weather station. The « Windy » logo is hiding the name below.

                  74CB55A1-C9EC-4478-BE7E-DC8A8184FF94.jpeg

                  1 Reply Last reply Reply Quote 0
                  • CrofterC
                    Crofter | Premium
                    last edited by Crofter

                    @ivo
                    Indeed, still not working on iPad. I second the observation re: location search box as well. Working on iPhone SE.
                    Also confirm the Windy logo is over the search box and prevents search function. Layers are messed up.
                    No errors reported when launched today.
                    Untitled.jpeg
                    This is what I see after I tap on the mini forecast which appears when I tap on the home icon. You can see that it selects the location on the map which would be under the mini forecast. So: launch app, tap on home icon, tap on forecast, result is as you see.

                    1 Reply Last reply Reply Quote 0
                    • ivoI
                      ivo Administrator
                      last edited by

                      Fixed on website soon in App Store

                      CrofterC idefix37I Michael WindyM 3 Replies Last reply Reply Quote 1
                      • CrofterC
                        Crofter @ivo | Premium
                        last edited by

                        @ivo
                        👍🏻😊

                        1 Reply Last reply Reply Quote 0
                        • idefix37I
                          idefix37 Sailor Moderator @ivo
                          last edited by

                          @ivo
                          Thanks for fixing !

                          1 Reply Last reply Reply Quote 0
                          • Michael WindyM
                            Michael Windy @ivo | Premium
                            last edited by

                            @ivo
                            Thank you for fixing up. It's the same problem I reported three hours ago. So I wait here for a Solution. Thanks a lot...
                            Michael

                            1 Reply Last reply Reply Quote 0
                            • CrofterC
                              Crofter | Premium
                              last edited by

                              Thank you for the fix. :)

                              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 of Use     Privacy Policy