hearse error when starting nethack

[GoogleCodeExporter]

What steps will reproduce the problem?
1. remove and reinstall inethack beta
2. start a nethack game
3. quit the game (ie, press iphone home button)
4. go to the inethack settings 
5. enable hearse
6. enter my email address in the email address field. leave the other two
fields blank
7. quit settings and restart inethack

after a few seconds I get the error: HEARSE: FATAL: Bones file could not be
downloaded: an unhandled error occured, for more support with these errors,
please contact me at nethackhearse@gXXXXXX.com

this is while I am connected to the wifi.

I am installing and using inethack version 1.3beta2 on an iphone os version
3.1.2 (7D11). Installing from windows XP using itunes 9.0.2.25

Original issue reported on code.google.com by jasonble...@gmail.com on 25 Nov 2009 at 11:13

[GoogleCodeExporter]

This the expected behavior when there are no valid bones (yet) for a version to
download, but at this stage it's getting weird since there do seem to be valid 
bones
available for download. I have notified Alexis about this.

Original comment by din...@gmail.com on 26 Nov 2009 at 11:34

• Changed state: Accepted

[GoogleCodeExporter]

why not simply supress that message? i mean, the user can't do anything about 
it and
it's not a critical error. I would simply now show it, because all it does is to
confuse the player.

Original comment by fryx.asr...@gmail.com on 26 Nov 2009 at 4:51

[GoogleCodeExporter]

When we are near release and the server still keeps sending that message, and 
there
won't be enough bones, this will probably the way to go. Atm I'm quite glad it's
shown b/c it tells me that there is probably something wrong. In case the 
message
boxes disappear completely (issue 145) it will stay in the logs anyway.

Original comment by din...@gmail.com on 26 Nov 2009 at 5:45

[GoogleCodeExporter]

Yes, this error message is very confusing and why is a normal process (attempt 
to
download a bones file but none available) causing an un-handled error? 
shouldn't a
common problem like that be handled more gracefully?

Jason

Original comment by jasonble...@gmail.com on 26 Nov 2009 at 11:09

[GoogleCodeExporter]

After some clarification from Alexis this message will be ignored in future 
builds.
The bones are all valid btw. Will resort to forced downloads in those (and 
related)
circumstances (issue 152).

Original comment by din...@gmail.com on 27 Nov 2009 at 10:32

[GoogleCodeExporter]

All hearse messages are now logged in trimmed form to a file which is viewable 
from
the main menu, plus some additional status messages. r359 / 1.3-b4

Original comment by din...@gmail.com on 30 Nov 2009 at 5:33

• Changed state: Fixed