That's a No then? So... you replace the competition with your own product, remove one of the (IMHO) better features, and then tell your developers it's for their benefit. I, and my users, appreciated the general purpose summary. And sure, I can devote some time (at my skill level, a long time) to take the forecast and design a function that will compare the various conditions and somehow output a general summary. But it's insulting to call it a "freedom", especially when it was once provided.

OK, that’s a No then? So … you replace the competition with your own product, remove one of the (IMHO) better features, and then tell your developers it’s to their benefit. I, and my users, appreciated the General Purpose Summary. Sure, I can spend some time (at my skill level, a lot) to creating a function that will take the forecast and somehow cobble together a general summary. But it’s insulting to tell me it’s a “freedom”, especially when it was once so conveniently offered.

OK, that’s a No then? So … you replace the competition with your own product, remove one of the (IMHO) better features, and then tell your developers it’s to their benefit. I, and my users, appreciated the General Purpose Summary. Sure, I can spend some time (at my skill level, a lot) to creating a function that will take the forecast and somehow cobble together a general summary. But it’s insulting to tell me it’s a “freedom”, especially when it was once so conveniently offered.

OK, that’s a No then? So … you replace the competition with your own product, remove one of the (IMHO) better features, and then tell your developers it’s to their benefit. I, and my users, appreciated the General Purpose Summary. Sure, I can spend some time (at my skill level, a lot) to creating a function that will take the forecast and somehow cobble together a general summary. But it’s insulting to tell me it’s a “freedom”, especially when it was once so conveniently offered.

OK, that’s a No then? So … you replace the competition with your own product, remove one of the (IMHO) better features, and then tell your developers it’s to their benefit. I, and my users, appreciated the General Purpose Summary. Sure, I can spend some time (at my skill level, a lot) to creating a function that will take the forecast and somehow cobble together a general summary. But it’s insulting to tell me it’s a “freedom”, especially when it was once so conveniently offered.

Same! Started about an hour ago. I had made a few changes but after seeing your comment, I went back to my last working commit and still getting the error. Not feeling very secure about WeatherKit.

nope!