APP IS BROKEN DO NOT BUY THIS
Response from developer
Hi - sorry to hear about your experience! What device are you using? Would love to solve this for you!
FIXED!!!! - CRASH After iOS 26
Thanks for the work. Tried to email developer, but no working email. Commented the last time it broke and it got fixed then.
App was fully functional under iOS 18 and below. Also worked with iOS 26 when in beta… once iOS 26 launched officially, App ceases to function. Opening then immediately closing. Widget also fails to load.
Response from developer
We recently had an issue due to NOAA changing their back-end for supplying weather data. It was now fixed in version 1.2.2 and is fully working! We are also adding safeguards in place to ensure this won't happen again with future versions!
New update fixed the crashing on ios26
Response from developer
Hi koolkarim94 - there was an outage with the API (NOAA) we use for gathering up to date TAF and METAD data which caused this outage. We have fixed it by migrating to a newer version - a we the new version of the app now available (1.3.0) should solve it. Please update - and apologies for the outage!
App no longer works
CRASH After iOS 26
Response from developer
We recently had an issue due to NOAA changing their back-end for supplying weather data. It was now fixed in version 1.2.2 and is fully working! We are also adding safeguards in place to ensure this won't happen again with future versions!
App is crashing
Response from developer
Hi Skysurferdude - there was an outage with the API (NOAA) we use for gathering up to date TAF and METAD data which caused this outage. We have fixed it by migrating to a newer version - a we the new version of the app now available (1.3.0) should solve it. Please update - and apologies for the outage!
Doesn’t work with iOS 26
Response from developer
Hi koolkarim94 - there was an outage with the API (NOAA) we use for gathering up to date TAF and METAD data which caused this outage. We have fixed it by migrating to a newer version - a we the new version of the app now available (1.3.0) should solve it. Please update - and apologies for the outage!
Not working
Response from developer
Hi - there was an outage with the API (NOAA) we use for gathering up to date TAF and METAD data which caused this outage. We have fixed it by migrating to a newer version - a we the new version of the app now available (1.3.0) should solve it. Please update - and apologies for the outage!
Doesn’t work with iOS 26
Cloud ceiling is wrong!!!!
A great substitute!
Needs improvement
Great App But…
I was really hoping I was able to put it on my Lock Screen so I can see the METAR at a glance however I’m unable to put the widget on the Lock Screen.
Please add the ability to put Widgets on the Lock Screen instead of just the home.
Response from developer
Great idea to add support for lock screen widgets. Might be coming in the next update!
Cloud ceiling
Absolutely love it
Current revision improperly parses visibility data
Response from developer
Hi, thanks for flagging this issue. This was caused by a change in the data format returned from the NWS. We have released a new version (1.2.4) which solves this. Please update to that version. Sorry for the inconvenience and hope you enjoy the app!
Crashes and reports wrong visibility
Response from developer
Hi, thanks for flagging this issue. This was caused by a change in the data format returned from the NWS. We have released a new version (1.2.4) which solves this. Please update to that version. Sorry for the inconvenience and hope you enjoy the app!
Does Not Work Anymore
meh … could be better
Secondly, the app is a little “crashy” when attempting to add stations. I found a work-around, but it shouldn’t be that way.
UPDATED!!! Fantastic app.
Below is original post, with newest update after notifying app developer all was fixed. Took only 3 days.
App and widget fail to load. Just crash. App needs updating to be compatible with IOS 17
Response from developer
We recently had an issue due to NOAA changing their back-end for supplying weather data. It was now fixed in version 1.2.2 and is fully working! We are also adding safeguards in place to ensure this won't happen again with future versions!
