[Update] It's the RCP query that causing the crash, not WeatherCatRCP. To test this I entered a RCP query for the External Temperature Basic Graph in the Safari browser. It caused WeatherCat 3.1.3 to crash. If I enter a RCP query for System Information, WeatherCat 3.1.3 doesn't crash. Here are the two queries (192.168.0.215 is the local IP address of the M1 Mini running WeatherCat 3.1.3):
http://192.168.0.215:49255/image/getBasicGraph/1 (crashes WeatherCat 3.1.3)
http://192.168.0.215:49255/discovery/systemData (retrieves WeatherCat 3.1.3 System Data)
How to replicate it on an iPhone:
1. Open WeatherCatRCP (the iOS app)
2. Select the More tab.
3. Select Basic Graphs
4. Select External Temperature
WeatherCat (the macOS app) crashes.
WeatherCatRCP is version 1.2 (190618) running on iOS 15.5 and was connected over the "Local" network to WeatherCat version 3.1.3 on a M1 Mini with Monterey 12.4.
[Update] The WeatherCat crash leaves WeatherCatRCP in "where did my server response go" limbo. Leave WeatherCatRCP alone until after WeatherCat restarts. WeatherCatRCP will find the restarted server and continue as normal.
This is very strange since WeatherCatRCP is making a Rich Client Protocol (RCP) request and waiting for WeatherCat to respond. When this occurs, WeatherCat crashes and WeatherCatRCP is abruptly disconnected.
Only a Basic Graph, Custom Graph, or CTW request causes the WeatherCat crash.Has this happened to anyone else using WeatherCat 3.1.3 or WeatherCat 3.2?