The map does not focus on the chosen city

astfgl

This is after the latest update.
I’m using the app on iphone 12, ios 17.1

Opening the app shows the initial city correctly, but any search results in the map focusing far south and I have to zoom out a lot, to get back to where I am

  {
  "errorID": "cant-create-ecmwf-calendar-from-meta-tag-missing-minifest-s",
  "timestamp": 1698076329347,
  "runningMs": 13,
  "type": "user",
  "module": "products",
  "msg": "Cant create ecmwf calendar from meta tag: Missing minifest string",
  "line": null,
  "col": null,
  "url": "capacitor://localhost",
  "script": null,
  "ver": "40.0.4",
  "target": "mobile",
  "stack": "i@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:97365
		b@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:102234
		global code@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:339675",
  "platform": "ios",
  "error": " {
		    \"message\": \"Missing minifest string\",
		    \"line\": 1,
		    \"column\": 97365,
		    \"sourceURL\": \"capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js\",
		    \"stack\": \"i@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:97365\
		b@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:102234\
		global code@capacitor://localhost/v/40.0.4.mob.7c8f/mobile.js:1:339675\"
		}",
  "isOnline": true,
  "size": "428x926",
  "latestBcast": "store: sessionCounter (13ms ago at 1698076329334)"
}

Suty

@astfgl Hi, what exactly happens when you insert the Teteven into the search field? Can you make a screenrecording?

astfgl

Hi, @Ondřej-Šutera
can't upload it here, so here's a link to the screen recording: https://we.tl/t-sOqn3Ef86U

Suty

@astfgl Okay, thank you for that. Can you share your iOS and Windy version?

astfgl

@Ondřej-Šutera ios is 17.1 and windy was 40.0.4, now it's 40.0.6 ( that's the version it shows in the app, in the app store it's 40.419), just got the latest update ... the error in gone, but the issue still persists.

Suty

@astfgl If you try to search for any other locations, does this issue persist?

xnewf

Same thing happens to me. Latest Windy app version on latest iOS. Home city correct but when I select it to get the detailed forecast, the map defaults to the Bermuda Triangle, literally.

Suty

@xnewf Do you have production version of iOS or Beta 17.1?

xnewf

@Ondřej-Šutera
Using iOS 17.0.3

Suty

@xnewf May I ask what language do you use in Windy? Also do you meet this issue only for certain locations or everywhere?

I would like to replicate the issue so I would like to have as much info as it is possible.

inAjet

Same thing happens to me. Clicking on ‘home’ icon, map goes to correct location. As soon as you tap on the 4-day weather at the top, the map centres on another location to the south. Same if you go to a favourite location or search for a location. Happens for all cities.

Suty

@inAjet What language do you use in Windy? Can you please check your settings?

xnewf

@Ondřej-Šutera Using English. All favorites and every search defaults to same area. Just updated to latest iOS yesterday which did not affect the app

Suty

@xnewf Could you please try to completely reinstall Windy?

Suty

@astfgl @inAjet @xnewf Hi, we probably found the cause of this issue and our colleagues started to work on the fix, so it will hopefully be solved soon. However, it happens when you have turned this button off. Could you please check that and let me know if the behavior gets better if you turn this feature on?

inAjet

@Ondřej-Šutera yes, turning that option back on fixes the issue; however, I prefer to have it selected off, so I’m glad to hear a fix is being worked on.

I use English language as well.

As the other users have reported, this wasn’t an issue until the latest update.

xnewf

@Ondřej-Šutera That did fix the problem but I also prefer not to have that always on. I will do a full reinstall and check that as you advised.

xnewf

@Ondřej-Šutera Full reinstall does not fix the issue. Have to keep that toggled map location on to have it function as it did before.

Suty

@inAjet @xnewf No worries, fix will be hopefully as soon as possible.

inAjet

@Ondřej-Šutera not sure whether today’s release was intended to include the fix, but just fyi this behaviour is still occurring.