I’m not sure if the bug I encountered is the same I tried to reproduce on play.
If you provide a geometry on the event payload, the api returns a 500 html page.
It seems a problem when the event is updated with that payload (creating is ok, it’s when you run for a second time the call that it fails)
On my server it’s a much older version (where there’s seem to have a compatibility layer for event.coordinate vs event.geometry) , but the problem is a NullPointerException on EventGeometryCheck
java.lang.NullPointerException
at org.hisp.dhis.dxf2.events.importer.shared.validation.EventGeometryCheck.check(EventGeometryCheck.java:58)
at org.hisp.dhis.dxf2.events.importer.EventChecking$ValidationRunner.run(EventChecking.java:87)
at org.hisp.dhis.dxf2.events.importer.update.validation.UpdateValidationFactory.check(UpdateValidationFactory.java:67)
at org.hisp.dhis.dxf2.events.importer.EventManager.updateEvents(EventManager.java:189)
at org.hisp.dhis.dxf2.events.importer.EventImporter.importAll(EventImporter.java:104)
at org.hisp.dhis.dxf2.events.importer.EventServiceFacade.addEventsJson(EventServiceFacade.java:101)
at org.hisp.dhis.dxf2.events.event.JacksonEventService.addEventsJson(JacksonEventService.java:205)
I don’t have access to the logs of the play so can’t confirm the problem.
Yeah, I understand the issue you could be facing, but the /api/events is a deprecated endpoint so even if there’s a bug in that older version it will not be of a major and prioritized importance; however, if we’re facing the same issue using the latest version and the new endpoint then it will most definitely be fixed.
For the record, I understand the game at play but upgrading dhis2 instance is generally a long process, and that old version doesn’t have the tracker api.
For the sake of a future upgrade, I tried to replicate that
on 2.39 : I have an error about an invalid date “Month not valid [1,4,7,10], was given 9” while trying to specify the featureType on the program