Opened 15 years ago
Closed 15 years ago
#3005 closed defect (fixed)
Upload to OSM API failed
| Reported by: | Owned by: | dmuecke | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | NullPointerException api | Cc: |
Description
Trying to upload 2 roads using JOSM but I get the following error:
Upload to OSM API failed
java.loang.NullPointerException
Please advise on how to proceed.
Thanks,
Nina
Attachments (1)
Change History (8)
by , 15 years ago
| Attachment: | Upload_to_OSM_API_failed.JPG added |
|---|
comment:1 by , 15 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 15 years ago
comment:3 by , 15 years ago
| Keywords: | api added |
|---|
comment:5 by , 15 years ago
I am against closing this. The user cannot provide a stacktrace because it's not printed anywhere, where it would be accessible. The easiest solution would be to just not handle the error and display the usual "this is always a coding error" dialog. The code checks for a bunch of other exceptions first anyway, so the error would only really pop up under strange circumstances… and if there is an issue that shouldn't result in the "coding error"-dialog, we can still write a patch that catches it.
comment:6 by , 15 years ago
Missing exception handling has been added with revision 1885 on August 2. I would recommend to close the issue.
Could you provide a stack dump or a way to reproduce the issue?