Bug Reports

One bug report per post. Off-topic posts will be closed. Only submit bug reports for builds currently marked as "public". For isolated issues or customer support visit help.vrchat.com.
POST /calendar/{groupId}/event intermittently returns 500 "Application error"
Creating a group calendar event fails with a 500 on 10 of 19 calls since 2026-10-11. The request bodies differ only in title, description and times, so the same request succeeds or fails at random. We hit this in the test suite for the community API specification . Three workflows create an event in a group they created a second earlier, and nothing else touches the group in between: group-calendar-lifecycle calendar-event-lifecycle update-instance-calendar-link-lifecycle CI runs with failures: 10-11 15:19 , 10-12 14:07 , 10-12 15:51 , 10-12 16:37 , 10-12 16:46 Request POST /api/1/calendar/{groupId}/event {"accessType":"group","category":"other","description":"Created by the test suite","title":"Test","sendCreationNotification":false,"startsAt":"2026-10-12T17:47:40.171Z","endsAt":"2026-10-12T18:47:40.249Z"} Response ( 500 ) {"error":{"message":"Application error","status_code":500}} Every call, failed or successful, reached build master-build-2026-10-09-pill-j-spearpide in the blue group. Failed (UTC, x-vrc-request-id) 2026-10-11 15:20:58 mv3z089tgsuw9nzz 2026-10-12 14:08:57 mv5bvgc4nuawh5dm 2026-10-12 14:10:17 mv5bx5v6d0z76z52 2026-10-12 15:51:53 mv5fjtszv0x2g0th 2026-10-12 15:53:00 mv5fl9h6ngz2zmri 2026-10-12 16:47:36 mv5hjgyovnpclfeo 2026-10-12 16:47:42 mv5hjll1pcaioy4c 2026-10-12 17:08:18 mv5ia3v5lfpuol7i 2026-10-12 17:08:25 mv5ia99065rllitv 2026-10-12 17:09:33 mv5ibpsv2bdb9mmw Succeeded (UTC, x-vrc-request-id) 2026-10-11 15:19:54 mv3yyugez7oprqpu 2026-10-11 15:20:03 mv3yz131x21o6lk5 2026-10-11 15:20:58 mv3z07nhrbz7n8up 2026-10-12 14:08:41 mv5bv4pavr7esmdy 2026-10-12 14:10:14 mv5bx48cht0bpi59 2026-10-12 14:10:15 mv5bx4rqf8bnxqc4 2026-10-12 15:51:59 mv5fjyt87luswyi7 2026-10-12 15:52:58 mv5fl7o3qzjcrdi7 2026-10-12 15:52:58 mv5fl8d9budkxp4g
1
·
tracked
OSCQuery: “Could not make new OscClient: Object reference not set” when an OSC app is already running at VRChat startup (no HUD notification)
Summary If an OSCQuery-enabled app on the same PC is already advertising when VRChat starts, VRChat discovers it during startup, before login, and fails with a NullReferenceException while creating the OscClient. No “VRChat is going to send data to …” HUD notification is shown. OSC data is still delivered to the app (avatar parameters and /avatar/change arrive), so only the client setup or notification step seems to fail. If the app is started after VRChat has finished starting, it is discovered without errors and the HUD notification appears. Environment VRChat 2026.4.1-1931-68b4616cf3-Release (Steam), Windows 11 OSCQuery app on the same PC, advertising _oscjson._tcp and _osc._udp on 127.0.0.1 (python-zeroconf / tinyoscquery) Steps to reproduce Start an OSCQuery app that advertises an /avatar endpoint (e.g. /avatar/parameters/MuteSelf). Start VRChat with OSC enabled. Watch the HUD after logging in, and check the output log. Expected The app is registered and the HUD notification is shown, the same as when the app is started after VRChat. Actual No HUD notification. The output log shows this during startup (while the login UI is being created, before authentication): ```log Debug - Advertising Service VRChat-Client-XXXXXX of type OSCQuery on 53316 Debug - Advertising Service VRChat-Client-XXXXXX of type OSC on 9000 Debug - [Behaviour] creating login UI Debug - Found new OSC Service: <app>:<id> at 127.0.0.1:63269 Debug - Found new OSC Service: <app>:<id> at 127.0.0.1:63269 Debug - [Behaviour] authenticating Debug - Found OSC Client of type 0 Debug - Found OSC Client of type 2 Error - Could not make new OscClient: Object reference not set to an instance of an object. Debug - Found OSC Client of type 0 Debug - Found OSC Client of type 2 Error - Could not make new OscClient: Object reference not set to an instance of an object. ``` Frequency 7 out of 7 launches with the app started first. 0 errors when VRChat was started first. In that case the app was discovered about 2 minutes after startup, and the notification appeared. Notes Discovery happens about 1 second after VRChat starts its own OSCQuery service, while the login UI is still being built. Something used when creating the OscClient (possibly the HUD or notification system) seems not to be initialized yet. Similar log line, different cause (remote PC / request failure): “Osc being discovered on non-local pc” and vrchat-community/osc#169( https://github.com/vrchat-community/osc/issues/169 ).
1
·
tracked
Load More
→